Saved-search match, instant
New listing matches your search, {{first_name}}
A {{bhk}} in {{locality}} just went live at ₹{{price}}. View photos and book a visit before it's gone.
Industry
ReachBell for real estate.
Alert buyers when a saved search matches, remind them about site visits, nurture leads to a booking, and re-engage cold enquiries — push, email, WhatsApp, and SMS from one place.
The problem
The real-estate engagement tax.
Portal alerts in one tool, CRM follow-ups in another, WhatsApp reminders in a third — and the hot lead went cold while the message sat in a queue.
Most property businesses end up with listing-alert emails from one vendor, a CRM that pings agents from a second, and a WhatsApp broadcast tool bolted on as a third. Each has its own idea of who a lead is, its own webhook contract, and its own definition of an “active subscriber”. A sales team can spend more time copying numbers between systems than actually calling buyers — and when a new project launches, nobody is quite sure which list got which announcement.
The site visit is the canonical example. The portal knows a buyer saved a property. The CRM knows the same person enquired last week. The WhatsApp tool sends a reminder that has no idea the visit was already rescheduled. None of them talk to each other, so the buyer gets three near-duplicate nudges — or worse, a reminder for a slot they cancelled an hour ago.
New-listing and price-drop alerts have the same shape: an event in your inventory needs to fan out to whoever cared about that locality or saved search, on whatever channel they accepted. When the alert lives in a separate system from your lead segments, fan-out becomes an export-and-import chore instead of an automation step.
Templates
Notifications you can ship today.
Drop these into the composer and adjust the merge tags — every template works across web push, mobile push, and email.
Price drop on saved property
Price drop in {{locality}}
{{project_name}} just dropped to ₹{{new_price}} — down from ₹{{old_price}}. The unit you saved is still available.
Site-visit reminder, 2-hour delay
Your site visit is at {{visit_time}} today
Meeting {{agent_name}} at {{project_name}}, {{locality}}. Tap for directions and the on-site contact number.
Project launch announcement
Now launching: {{project_name}} in {{locality}}
Pre-launch pricing from ₹{{starting_price}}. Limited inventory for early registrations — book a preview slot.
Post-visit follow-up, next day
How was your visit to {{project_name}}?
Have questions on pricing, floor plans, or possession date? Reply here and {{agent_name}} will get back to you.
Cold-lead re-engagement
Still looking in {{locality}}, {{first_name}}?
Three new {{bhk}} options came up this week in your budget. Want us to shortlist them for you?
Automation flows
Three flows worth their weight in bookings.
Built from the visual flow builder — each node is a send, a wait, or a condition. No code.
Lead-nurture drip for new enquiries
Multi-touch sequence across push, email, and WhatsApp to move a fresh enquiry toward a booked site visit without overwhelming the lead.
- 01Trigger: `lead.created` webhook from your portal, landing page, or CRM.
- 02Send "Thanks for your interest" email immediately with the project brochure and a link to book a visit.
- 03Wait 1 day, then send web/mobile push: "Ready to see {{project_name}} in person?" with a deep link to the slot picker.
- 04If no visit booked after 3 days, send WhatsApp template (opt-in only) offering to shortlist matching units.
- 05Exit the flow as soon as a visit is booked — webhook listens for `visit.scheduled`.
Site-visit booking and reminders
Confirm the booking, cut no-shows with timely reminders, and follow up the moment the visit is done.
- 01Trigger: `visit.scheduled` for a lead.
- 02Send "Visit confirmed" email immediately (transactional, bypasses marketing throttle) with date, time, and directions.
- 03Send WhatsApp reminder 1 day before with the agent's name and on-site contact number.
- 04Send push 2 hours before: "Your site visit is today" with a maps deep link.
- 05After the `visit.completed` webhook, wait 1 day and send a post-visit follow-up email.
Re-engagement for cold leads
Bring back enquiries that went quiet with fresh, budget-matched inventory instead of letting them lapse.
- 01Segment: last activity > 30 days ago, opted in to marketing, has a saved search or stated budget.
- 02Send email: "New homes in {{locality}} you haven't seen yet" with three matching listings.
- 03Wait 4 days, then push: "Want us to shortlist {{bhk}} options for you?"
- 04If the lead clicks or replies, exit and tag them as `reengaged` for the sales team to follow up.
- 05If not, drop the lead to a low-frequency monthly market-update segment instead of unsubscribing.
In the wild
Who's using it.
We dogfood ReachBell on our own products before recommending it to yours.
ReachBell powers push, email, and automation for our internal portfolio — including VedHoroscope (a daily-horoscope app where personalisation needs to read like it came from your astrologer, not a CRM), StumpScore (a cricket-scores site that has to push score updates within seconds of a wicket without hammering subscribers off the list), and OmegleCo. (a chat product whose re-engagement loops live entirely on push and email).
The real-estate playbook above isn’t a hypothetical — it’s the same event-trigger-template-segment loop those products use, with listing and site-visit events swapped in for scores or horoscopes. If a cricket site can push score updates inside 5 seconds of a boundary without burning its list, your “new listing matches your search” alert can land in time too.
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Can ReachBell connect to my property portal or CRM?
Yes — any portal, landing page, or CRM that can fire a webhook can push ReachBell events for enquiries, saved searches, site visits, and listing changes. Send a flat JSON payload to a single webhook URL and we route it into the matching automation; no per-integration glue code required.
How do I keep listing alerts from feeling spammy?
Use frequency caps per channel (e.g. max 2 marketing pushes per day) and combine them with quiet hours per project. ReachBell skips capped messages instead of failing them, so the audit log still shows what would have sent — useful when a buyer's saved search suddenly matches a dozen new listings at once.
Can I personalize messages with listing, project, or lead data?
Yes. Every send accepts a flat JSON payload, and templates use {{merge_tags}} like {{first_name}}, {{locality}}, {{project_name}}, or {{visit_time}}. The same data is available across push, email, and WhatsApp templates so a single automation can branch by channel without rewriting copy.
How do saved-search and price-drop alerts work across many listings?
Leads attach to a saved-search or `locality` tag rather than a separate list per property. When a new listing matches or a price changes, your portal POSTs to ReachBell with the listing details and we fan out to everyone whose saved search matches — no pre-creating a campaign per property.
Is ReachBell a fit for India-first real estate with WhatsApp follow-up?
Yes. Pricing is in INR, the platform is built DPDP-aware with consent capture and a preference center, and WhatsApp and SMS sit alongside web and mobile push and email — so site-visit reminders and lead follow-up go out on the channel each lead actually opted into, with STOP honoured automatically.