Slab photos to booked buyers — not another launch teaser

Definition

Construction updates is the job of sending milestone email digests and optional WhatsApp utility pings to buyers who already booked, using knowledge for current slab status and humans for delay explanations, through possession.

Launch templates to booked buyers feel like spam

Marketing reuses the teaser because it is approved. Wrong job, quality risk. Property managers should not use this for maintenance. No SMS slab alerts.

Omnichannel sequence

Email primary, WhatsApp ping, voice rare at possession (appointment skill).

How it runs in CoPulse

Growth campaigns/drips. Workflow on enter subscribes. Conversation answers “when is my floor?” from knowledge. Autonomous optional with honest metrics. Autonomous agents may follow a launch list on WhatsApp, email, or phone after plan approve. They do not create templates, do not adapt from prior outcomes, and do not stop when a site visit is booked. Campaign reply rate is not an Interested CRM state. WhatsApp live catalog is Gupshup, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.

Operator setup

Per-tower knowledge, SES, utility template, wallet preview.

Tower B slab 12, 280 booked buyers

Tuesday 11 SES because ops chose 11. WhatsApp utility ping. Delay questions hand off. Possession uses calendars like a visit. Click-path: Growth, knowledge, kanban filter.

Do not create nested construction-updates/email URLs. Listings digest is shoppers. Pricing: 280 mails hit the wallet. Autonomous would only count reads.

Operators assemble this job on the Project. Click-path remains Pipeline construction stage → Growth drip email + WhatsApp → Library → knowledge ritual → wallet preview. Keep the quotable definition in the brief for the team: Construction updates is the job of sending milestone email digests and optional WhatsApp utility pings to buyers who already booked, using knowledge for current slab status and humans for delay explanations, through possession. Autonomous agents may follow a launch list on WhatsApp, email, or phone after plan approve. They do not create templates, do not adapt from prior outcomes, and do not stop when a site visit is booked. Campaign reply rate is not an Interested CRM state. While you implement, keep the parent playbooks directory, Construction / handover, Email overlay, Developers, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the visit truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The Construction updates playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.

Channel sequence (one job, not extra URLs)

After-sales hops. There is no nested playbook-by-channel path.