Growth campaigns
Milestone sends. Wallet preview. Exclude launch tags.
Construction updates are a cadence, not a second launch
After booking, buyers need milestone updates through possession, not another launch teaser. GrowthLoop’s demo follow-up after booking confirmed is weekly construction on email. That is SES, clock-based, not smart send-time, not adaptive nurture. This stage is not the construction-updates playbook (the job) and not the email overlay (the hop). It is the Bookings column for people who already paid and are waiting on a building.
- Email milestones
- Short WhatsApp pings
- Not launch creative
Launch templates to booked buyers feel like spam and risk template quality
Marketing teams reuse the launch teaser because it is already approved. Booked buyers wanted slab photos and possession dates. Wrong audience, wrong job, possible WhatsApp quality hits. Property managers should not use this column for maintenance tickets. Autonomous “keep them warm until possession” still only counts sends/reads and will not know handover happened. SMS construction alerts are not live.
Cadence until keys
Email is the long hop. WhatsApp is the alert. Voice is rare (possession scheduling).
- Audience is Booked+ Do not mix with New enquiry launch lists.
- Milestone mail SES. Operator picks the clock. Warmup is not engagement-ordered.
- Optional WhatsApp Utility template if the session is closed. Wallet preview on large towers.
- Handover week Appointment skill for possession slot. Then a done label you define.
How it runs in CoPulse
Growth campaigns/drips are the runtime. Workflow on enter adds them to the construction audience. Conversation agent answers “when is my floor?” from knowledge you update. Humans own delay explanations.
SES digest. See /industries/realestate/channels/email.
Workflows
On enter: subscribe to construction drip. On possession booked: reminder like a visit.
Knowledge bases
Current slab status. Stale knowledge is worse than no bot.
Operator setup
Project-level knowledge per tower. Organization wallet for tower-wide sends.
Setup → Customers → Pipeline → Growth construction drip (email + optional WhatsApp) → Library templates → knowledge update ritual → wallet preview.
Tower B slab 12, 280 booked buyers
All Bookings in Construction / handover get a SES photo mail Tuesday 11:00 because ops chose 11:00 — not a smart algorithm. A WhatsApp utility pings “photos in email.” Someone asks possession; conversation agent reads knowledge; delay questions hand off. Possession week uses appointment skill plus a Visit-Caller-like voice if you copy that pattern — still sends/reads if you used autonomous by mistake.
Click-path: Growth campaigns; Setup → Channels email; Library; kanban filter this stage. Playbook construction-updates is the job URL. Do not create nested construction-updates email paths. Pricing: 280 mails and pings hit the wallet; preview first. Update the knowledge base when slab status changes or the conversation agent will lie. Workflows on enter only subscribe the Booking; they do not write the photo. Humans explain delays. Appointments/calendars appear again at possession week, with T-24h reminders like a site visit, still not an autonomous stop-on-booked rule. Exclude shoppers in Dormant / re-engage from this drip.
After-sales cadence
Exit is informed possession, not “opened the launch teaser.”
| Stage | Automation | Human | Channel hops | Exit criteria |
|---|---|---|---|---|
| Construction / handover | Milestone drip | Delay comms, possession | Email + WhatsApp | Keys / done label |
| Booked | Welcome | KYC | WhatsApp + email | After-sales fork |
| Loan disbursal | File nudges | Bank | Email + voice | Often before this |
| Launch campaign | Teaser | Creative | WhatsApp + email | Wrong audience |
Jobs for people who already bought
Construction cadence is one job. Listings digest is another — do not mix lists.
Frequently asked questions
Launch vs construction, and email clocks.
Can I reuse the launch WhatsApp template?
Do not. Wrong job, quality risk. Use a utility construction template.
Smart send-time?
No. You pick the clock. Email warmup is not engagement-ordered.
Workflow on enter?
Add the Booking to the construction audience / drip.
Autonomous until handover?
Sends/reads only. Update knowledge and stop the drip when you hand keys.
Meta Cloud WhatsApp for alerts?
Live catalog is Gupshup.
Wallet?
Tower-wide sends add up. Preview under Growth. Pricing.
Related
Parent hub, sibling stages, CRM product, and jobs that move this column.
Real estate hub
Buyers & Tenants, Bookings, channels, and playbooks.
Back to hub →Loan disbursal
Often still running in parallel.
Open →Booked
Where after-sales started.
Open →Pipeline & CRM
Campaigns from pipeline stages; knowledge for bot answers.
Product CRM →Wallet-only pricing
Milestone SES and WhatsApp debit the Organization wallet — preview large towers.
See pricing →Put slab photos on a drip, not a launch list
Stage-enter subscription to construction email, short WhatsApp pings, humans on delays — until possession. Preview the Organization wallet before a full-tower send, and keep launch teasers off this list.
Get started free