Skip to main content

​
Real estate showing, listing, and closing notifications end to end

You run messaging for a brokerage. A buyer’s timeline holds four conversations at once: which listings to see, when the showing is, which documents the agent still needs, and what the closing requires. This guide composes the pieces Devotel Orbit ships for that timeline into one reference, in the order you should build them. The examples follow one fictional brokerage, Harborline Realty: 14 agents, about 300 active buyers, one MLS feed. Each part has its own deep guide. This page is the vertical order of work; the industries overview places real estate in the wider vertical map, and the real-estate notifications buyer explainer is the piece to hand a prospect who is deciding whether the workflow fits. Every control on this page is tenant-owned. You decide which messages are marketing and which are transactional, which segments receive listing alerts, which windows apply to each lane, and how an opt-out propagates. Orbit provides the channels and the controls; it does not attest to any state licensing rule or MLS policy on your behalf. If your program answers to one, your team maps these controls to it.

​
1. Split the transactional lane from the marketing lane

A showing confirmation tells a buyer about an appointment they asked for; a listing alert pitches them something they did not. Treating the two as one stream is the most common real-estate messaging mistake, because listing-alert volume then burns the reputation and the consent standing of the messages that close transactions. Classify every send before you build anything: Three controls hold the split in place:
  • Consent by class and channel. Record consent per class, per channel, with consent management. A buyer who booked a showing consented to showing coordination; that is not consent to listing alerts, and SMS consent is not WhatsApp consent. Capture listing-alert consent separately at intake, and verify a sample of your buyer list with the consent inspector before the first alert run.
  • Separate email streams. Send closing documents and showing notices from a different email stream than listing alerts, the same isolation any team applies between transactional and marketing email: Isolate transactional and marketing email streams. Listing-alert engagement then never affects the deliverability of the stream that carries contracts.
  • Buyer-local quiet hours on the marketing lane. Set recipient-local quiet hours and apply them to listing alerts and open-house invitations. Which classes quiet hours cover is your decision; most teams exclude showing-day reminders and closing deadlines so a signing reminder is never held until evening.
One platform guard applies to voice regardless of tenant settings: outbound calls outside the US federal calling window are blocked and the window cannot be disabled. Schedule offer callbacks and showing-reminder calls inside it.

​
2. Listing alerts to propensity and linked segments

Do not send every alert to every buyer. Score buyers on the engagement you already observe, and send each alert to the segment that will act on it:
  • Build propensity segments from engagement traits: alerts opened, listings saved, showings attended, replies sent. A buyer who opened the last three alerts is a different segment from one who has not opened any in sixty days.
  • Keep the segments fed from your MLS data with linked audiences, so a listing that enters your feed tonight is in front of the right segment tomorrow without a manual sync.
  • Send over two channels with different jobs: SMS for the time-sensitive slice (price drop on a saved listing, listing going pending), email for the full brief with photos and the map link. A buyer who opts in to one has not opted in to the other; the consent split from section 1 applies per channel.
  • Cap the marketing lane with your tenant frequency caps. A workable default for an active market is three listing alerts per buyer per week; tighten it per segment rather than globally.

​
3. Showing confirmation as an RCS card with SMS fallback

The showing confirmation is the moment RCS earns its place in this stack: a branded card carrying the listing photo, the address, and the showing window, with two actions under it. Build it with the RCS rich card builder:
  • Card content: listing photo, street address, date and time window, agent name.
  • Book action: opens your scheduling link for buyers who have not picked a slot yet.
  • Reschedule action: opens the same link in reschedule mode, or starts the WhatsApp conversation from section 4 for buyers who prefer to talk it through.
Not every device receives RCS. Put the card in a fallback chain so a device without RCS gets the SMS version: same showing window, same two actions as a link and a keyword. Two rules keep the chain honest:
  • The fallback send is a new send: it passes the same consent, quiet-hours, and suppression checks as the card.
  • Key both sends on the same showing_id so a buyer who confirmed on SMS never also gets the RCS card an hour later.

​
4. WhatsApp buyer–agent coordination and document requests

Showing logistics are one-way; the work between offer and closing is a conversation. Run it on WhatsApp:
  • Set up the workspace and approved templates with Getting started with WhatsApp. Keep the template set small: showing reminder, document request, and closing update cover the lane.
  • Use WhatsApp for the back-and-forth and email for the paper. When the buyer’s lender needs the signed disclosure, the document itself travels as an attachment on the transactional email stream (email attachments); the WhatsApp thread carries the “it’s in your inbox, page 4 needs a signature” nudge. The attachment and the nudge reference the same file_id, so your record shows one document request answered once.
  • Map reschedule intents with keyword rules and recipes: RESCHEDULE reopens the scheduling link, CONFIRM writes the confirmed event and ends the reminder run, STOP flows into the opt-out handling in section 7. Keep the set to those words; every extra keyword is a misspelling you will support.

​
5. Listing IVR for time-sensitive offers

A buyer calling about a listing at 7 p.m. is the highest-intent moment you will ever route. Give it a built IVR flow instead of a voicemail box:
  1. Play the listing address and offer deadline.
  2. Press 1 to reach the listing agent’s on-call line.
  3. Press 2 to schedule a callback inside the next calling window.
  4. Press 3 to hear showing times and press 4 to receive them by SMS.
Add IVR routing with NLU for the callers who speak instead of pressing digits: “I want to see the house on Saturday” routes to the showing branch, “is the seller motivated” to the agent branch. Two rules keep the IVR defensible: the callback branch schedules inside the federal calling window, because the callback is outbound voice, and the SMS branch sends only to callers who pressed it, which is the consent record for that one message.

​
6. Closing package over scheduled email

The closing package is the one send in this guide where timing discipline matters more than speed: disclosures arrive when the buyer can actually read them, on the transactional stream, with the paper attached.
  • Attach the documents with email attachments: the signed disclosures, the closing disclosure, and the wiring instructions, each uploaded once and referenced by file_id on every send that mentions it.
  • Schedule the send with message scheduling at a reasonable hour in the buyer’s timezone. A closing package that lands at 2 a.m. is read at 9, after the wire deadline; schedule it for 8 a.m. buyer-local instead.
  • Wire your escrow or transaction-management system to emit one event per milestone (docs_requested, docs_signed, clear_to_close) with a stable transaction_id, and key every condition on that id so an older transaction can never trigger a reminder on a newer one.
Treat an undelivered closing document as an incident, not a statistic: the monitoring in section 7 tells you which sends never arrived, and a closing document in that queue gets a same-day phone call.

​
7. Opt-out propagation, monitoring, and rollout

A buyer who texts STOP to a listing alert has told you about the marketing lane, on one channel. Propagate that decision the way the buyer expects: everywhere.
  • Keyword handling writes the opt-out to your opt-out lists; the entry is per destination, not per campaign.
  • Message suppression then applies the list across channels, so the same buyer never receives the open-house invitation by email the next morning. Which classes an opt-out suppresses is a tenant decision: most brokerages suppress the whole marketing lane and keep transactional showing and closing messages flowing, because those complete requests the buyer made; if your counsel separates them differently, configure the classes accordingly.
  • Reconcile every send through the delivery log. A weekly pass over undelivered and suppressed sends is the operational heartbeat of this program: undelivered closing documents become phone calls, and a marketing send that hit a suppressed destination is a consent-bookkeeping bug to fix at the source.

​
Rollout checklist

The canonical sequence is the production go-live checklist; this is the real-estate annotation of it:

​
Troubleshooting

​
See also