Matched launch teasers on WhatsApp and email — then triage

Definition

Property launch is the job of segmenting buyers by stated BHK and locality, sending a launch teaser on WhatsApp and email with approved library templates, previewing the Organization wallet, and routing hot replies to a conversation agent or RM — one omnichannel URL.

Whole-database teasers burn template quality and Saturday slots

Marketing blasts everyone. Unqualified traffic saturates visits. Match first (inventory-match fields). Construction buyers must be excluded. Autonomous launch follow-up may send after plan approve but will not stop on site visit booked and will not create templates.

Omnichannel sequence

List is CRM. WhatsApp + email go out. Replies on WhatsApp. Voice when a visit books. Meta is optional ads, not this send.

How it runs in CoPulse

Growth campaigns are the runtime. Reply Triage is a conversation agent. Workflows on reply optional. 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

Templates approved, audience, wallet, qualifier ready for replies.

Prestige Lakeside teaser, 412 WhatsApp, 2800 email digest slice

Library copy: 412 WhatsApp teaser, 2800 weekly digest on email. Replies hit qualifier. GrowthLoop demo funnel is Reached 2400 → Replied 612 → Qualified 184 → Site visits 47 → Bookings 9 — demo analytics, labeled separately from template % below.

Click-path: Growth, Library, wallet, inbox. property-campaigns is the generic listings job. Pricing on /pricing/. Illustrative launch template: Sent 100, Opened 71, Replied 14, Site visit 6, Closed 2.

Operators assemble this job on the Project. Click-path remains Library launch templates → Growth audience from CRM → wallet preview → Studio Reply Triage → pipeline → exclude construction. Keep the quotable definition in the brief for the team: Property launch is the job of segmenting buyers by stated BHK and locality, sending a launch teaser on WhatsApp and email with approved library templates, previewing the Organization wallet, and routing hot replies to a conversation agent or RM — one omnichannel URL. 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, New enquiry, WhatsApp 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 Property launch 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)

Launch hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

From playbook-templates.ts re-launch-promo. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.