Weekly matched 3BHKs — email and WhatsApp, not this Saturday’s panic

Definition

Listings digest is the weekly job of sending matched inventory to shoppers who are not this-weekend-visit-ready, primarily on email with an optional WhatsApp ping, then qualifying replies into the visit path.

Daily WhatsApp marketing to lukewarm buyers trains opt-out

Ops nags daily. Digest is the long hop. Opt-out-compliance still applies. Exclude Booked/construction. Autonomous weekly sends still only count reads.

Omnichannel sequence

Email digest, optional WhatsApp, replies on either, voice if they book.

How it runs in CoPulse

Growth drip/campaign. Conversation on replies. Autonomous 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

SES, optional WhatsApp template, segment, drip.

2,800 digest, 412 hot WhatsApp slice stays on launch

Library split: digest email 2800, teaser WhatsApp 412. Digest readers book later. Click-path: Growth, SES, inbox.

Construction-updates uses email too — different audience. Illustrative opened 71% on launch template. Pricing: SES + WhatsApp wallet.

Operators assemble this job on the Project. Click-path remains Channels email + WhatsApp → Library → Growth weekly drip → qualifier → wallet. Keep the quotable definition in the brief for the team: Listings digest is the weekly job of sending matched inventory to shoppers who are not this-weekend-visit-ready, primarily on email with an optional WhatsApp ping, then qualifying replies into the visit path. 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, Qualified, 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 Listings digest 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)

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

Illustrative funnel (library template estimates)

Opened 71% is the launch-template email-ish bar — still an estimate. 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.