Guide · Opt-in and opt-out

WhatsApp opt-in for property leads

Collect and honor opt-out on every channel that will send templates. A portal click is not automatically a marketing opt-in in your policy. A buyer who says STOP on WhatsApp must leave the Growth list. CoPulse will not invent a full consent-ledger product name beyond list exclusion and inbox handling you configure — operators still do the honouring.

Portal lead ≠ blanket marketing consent
STOP must mean stop
Three nurture systems must all honour it

Start free Opt-out compliance playbook

Definition

Opt-in and opt-out operations means recording that a person agreed to marketing or transactional sends on a given channel, excluding them from Growth/autonomous audiences when they revoke, and keeping inbox available for transactional visit confirms only if your written policy allows — on Organization-owned numbers, not personal phones.

Why one inbox mute is not enough

RM stops chatting. Drip still fires at 11:00. Autonomous win-back still picks the CRM query. Buyer reports spam. Wallet still spends. That is three systems (G18) without a shared stop contract — you must exclude the number everywhere.

Opt-out-compliance playbook is the job. RERA guide is claims. This is consent mechanics.

HowTo: collect and honour

Write a Project policy. Implement with lists and inbox, not hope.

Define marketing vs transactional Launch teasers vs visit reminders. Counsel if needed. Not legal advice.
Capture opt-in where you blast Web checkbox, campaign reply, or documented inbound. Do not assume portal TOS is enough without review.
Keyword STOP Train RM and agent to exclude from lists immediately.
Exclude from Growth and autonomous queries Both. Inbox mute is not enough.
Document exceptions If you still send a utility visit confirm after STOP, that is a policy you own.

How it runs on the platform

List hygiene + inbox. There is no shared stop-when-booked and no shared stop-when-STOP unless you configure all runtimes. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: launch reply then STOP

Buyer replies to teaser (window opens). Qualifier chats. Buyer says STOP to marketing. Operator removes from launch drip and from dormant CRM query used by autonomous. Sunday visit reminder: policy says transactional utility still OK — RM sends one utility, notes the file. Next week’s listing campaign query excludes them. Wallet saved from continued marketing.

Web chat to WhatsApp: capture consent when you collect the number if you plan templates. See that guide.

Runtime × what to stop

STOP must hit every sender.

Runtime	If they STOP marketing	Transactional visit?	Owner
Inbox agent	Do not upsell	Per policy	RM / router
Growth drip/campaign	Exclude list	Separate utility campaign only if policy	Growth operator
Autonomous task	Exclude CRM query	Do not ‘win-back’ them	Task owner
Email SES	Suppress	Same policy	Campaigns
Phone	Do not autodial marketing	RM confirm call maybe	Ops

Honest limitations

No first-class consent ledger beyond what you configure. G18 three systems. G4 no auto handoff of replies into nurture — still do not add STOP’d people manually. Not legal advice. Honour opt-out on SMS too.

Keep this Opt-in and opt-out article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Growth audiences / lists. Autonomous CRM query filters. Inbox. Library templates with opt-out language. Opt-out-compliance playbook. Canonical playbook: Opt-out compliance playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

RERA posture. Campaigns. 24h window.

Frequently asked questions

Lists that still include people who said STOP last launch.

Is a portal enquiry opt-in for marketing templates?

Do not assume. Policy + counsel. Operationally, prefer explicit opt-in for blasts.

Does CoPulse auto-stop all three systems on STOP?

You must exclude lists and queries. We are honest that they do not share one switch today.

Visit reminder after STOP?

Your policy. Many desks allow transactional utility. Document it.

Marketplace leads?

Separate path. Do not dump into CRM marketing lists casually (G17).

Email unsubscribe vs WhatsApp STOP?

Honour each channel. One does not always mean the other — say so in policy.

Pricing?

Suppression saves wallet. See pricing for send markups.

Hub, sibling guides, canonical playbook, product, pricing.

STOP has to hit Growth and autonomous, not only inbox

Exclude the number everywhere — opt-out-compliance playbook.

Get started free