Growth campaigns
Listings & launches. Multi-channel.
Marketing listings and launches is an omnichannel campaign job, WhatsApp plus email plus Meta, with library templates and wallet preview before send. This is not whatsapp-property-campaigns. property-launch is the teaser event; this page is always-on listings marketing. Growth nav label is Listings & launches.
Property campaigns is the ongoing job of promoting listings across WhatsApp, email, and Meta using Growth campaigns, approved library templates, CRM segments, and Organization wallet preview — then handing replies to qualification and visit booking.
Teams want a WATI clone URL. CoPulse jobs stay omnichannel. Meta is capture/ads; WhatsApp/email are sends. Autonomous optional on lists. Conversion in campaigns is still reply rate.
Segment → WhatsApp/email send → Meta may have driven the original lead → replies qualify → voice for visits.
Growth is primary. Conversation agent on replies. Autonomous list follow-up 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.
Listings & launches. Multi-channel.
Gupshup approval for WhatsApp.
Ads/DMs via Meta overlay, not a second playbook URL.
Optional. Sends/reads. Operator picks template.
Channels connected, templates, segments, wallet.
Setup → Channels WhatsApp/email/Meta → Library → Growth campaigns → Studio qualifier → wallet preview.
Ops builds a segment. Wallet preview kills the 50k idea. 800 WhatsApp + email. Replies go to qualifier. Click-path: Growth, wallet, inbox.
Launch teaser is a sibling event. Illustrative launch funnel % if you reuse that template family. Pricing: /pricing/ wallet-only.
Operators assemble this job on the Project. Click-path remains Setup → Channels WhatsApp/email/Meta → Library → Growth campaigns → Studio qualifier → wallet preview. Keep the quotable definition in the brief for the team: Property campaigns is the ongoing job of promoting listings across WhatsApp, email, and Meta using Growth campaigns, approved library templates, CRM segments, and Organization wallet preview — then handing replies to qualification and visit booking. 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 campaigns 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.
Always-on hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | Meta / web (optional) | Original capture | CRM |
| 2 | WhatsApp + email | Listing send | Delivered |
| 3 | Qualify reply | Fields | |
| 4 | Voice | Visit | Calendar |
Use launch-template estimates when the creative is a teaser family. 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.
Why this is not a WhatsApp nested path.
Here. Omnichannel. No nested URL.
Campaign attach is separate; autonomous cannot nurture marketplace allocations.
Snapshot/dynamic deferred. Prefer static lists today.
Coming soon.
No. You pick the clock. Email warmup is not engagement-ordered.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
How-to companion. The job URL stays this playbook.
Guide →One URL per omnichannel job.
Directory →The event teaser.
Open →Weekly cadence.
Open →Launch desks.
ICP →Replies land here.
Stage →Teaser hop.
Channel overlay →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →WhatsApp + email sends debit the Organization wallet — preview first.
See pricing →Segment, template, wallet preview, WhatsApp plus email plus Meta capture — one playbook URL.
Get started free