Opt-out is every channel — including the next launch template

Definition

Opt-out compliance is the job of taking a STOP or unsubscribe on any connected channel, excluding that contact from Growth listing and launch sends, and applying your written policy to transactional visit or ticket messages — not pretending a blast is fine because it used a different hop.

Unsubscribed on WhatsApp, emailed the teaser anyway

Channel silos. Honor across WhatsApp, email, Meta. SMS must not be the consent loophole. Marketplace allocations vs CRM numbers have no suppression bridge — do not mix those audiences casually. No adaptive “maybe they still want launches.”

Omnichannel sequence

Signal on WhatsApp/email/Meta → CRM flag → exclude lists → optional human inbox note.

How it runs in CoPulse

Inbox + list hygiene + router. Workflows can set properties on keyword. Autonomous must not pick opted-out CRM queries. Conversation agent should not keep pitching. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. 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

Property, workflow, list process, legal copy in knowledge.

STOP on WhatsApp, launch email killed the same day

Workflow flags opted_out. Ops removes from Friday launch list (static list). Saturday visit reminder still sends because they hold a slot — written policy. Click-path: inbox, property, Growth recipients.

RERA guide is posture, not legal advice. Duplicate-leads must copy the flag. Pricing: compliance sends still wallet if you message; suppression saves wallet. Marketplace vs CRM gap: do not assume one STOP covers unrevealed marketplace rows.

Operators assemble this job on the Project. Click-path remains Customers property opted_out → Workflows on inbound keyword → Growth list discipline → Studio knowledge policy → never add SMS as a bypass. Keep the quotable definition in the brief for the team: Opt-out compliance is the job of taking a STOP or unsubscribe on any connected channel, excluding that contact from Growth listing and launch sends, and applying your written policy to transactional visit or ticket messages — not pretending a blast is fine because it used a different hop. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, Pipeline hub, 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 Opt-out compliance 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)

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