Follow-Up Email Templates

Customise and send post-open-home follow-up emails using three buyer scenario templates.

4 min readUpdated 2026-05-11Agent Portal

The Follow-Up Email system allows you to send personalised post-open-home emails to attendees using three buyer scenario templates. Emails are sent in batch after an open home is completed.

The Three Scenario Templates

TemplateWhen to UseTone
Hot LeadAttendee flagged as 'interested in purchasing' and engaged during the open homeWarm and action-oriented — emphasises next steps (e.g., second viewing, offer deadline)
Cold LeadAttendee who signed in but showed no purchasing interestLight-touch — keeps the property top of mind without pressure
Single AttendeeVery small open home (1–2 attendees) where a personalised note is appropriatePersonal and conversational

Customising Your Templates

  1. 1Navigate to Agent Portal → Profile.
  2. 2Scroll to the Follow-Up Email Templates section.
  3. 3Edit the Hot, Cold, or Single template in the text area provided.
  4. 4Use the placeholder variables: `{{buyer_name}}`, `{{property_address}}`, `{{agent_name}}`, `{{agent_phone}}`.
  5. 5Click Save Templates.
  6. 6Use the Preview panel to see how the email will look before saving.

Template Persistence

Your templates are saved to your agent profile and persist across all listings. You only need to set them up once. Different templates can be used for different open homes by editing the template before sending.

Sending Follow-Up Emails

  1. 1Open a completed open home card in your listing.
  2. 2Click Send Follow-Up Emails.
  3. 3The system groups attendees into Hot / Cold / Single scenarios based on their sign-in data.
  4. 4Review the groupings and adjust if needed.
  5. 5Click Send All. Emails are sent via Resend with an idempotency guard — each attendee can only receive one follow-up per open home.

Idempotency Guard

The system prevents duplicate follow-up emails. If you click Send twice by accident, the second attempt is silently ignored — attendees will not receive duplicate messages.

Found an error? Open an issue on GitHub