Guide · Opt-in and opt-out

Clinic opt-in and opt-out (not a HIPAA claim)

Honor opt-out on campaigns and templates the same as inbox; this is not a HIPAA claim and not a substitute for your counsel. STOP on a package blast must suppress Growth and autonomous lists, not only the last WhatsApp ping.

Suppress lists, not only the last ping
Not a HIPAA claim
Canonical job is opt-out compliance

Start free Opt-out compliance playbook

Definition

Opt-in and opt-out operations mean capturing consent language you choose, excluding STOP/opt-out contacts from Growth campaigns, drips, and autonomous lists, and still allowing transactional confirms only if your policy and counsel say so. CoPulse does not sell a HIPAA certification on this page.

Why ‘we have a bot’ is not consent

A clinic blasts packages to a CSV from Excel. Someone replies STOP. The next autonomous checkup run still includes the row. That is an operations miss, not a feature gap you paper with a US acronym.

DPDP and WhatsApp rules are the Indian operator’s problem. This guide is the click-path: list exclusion, template sends, inbox. Email overlays may also carry unsubscribes.

HowTo: honor STOP across runtimes

Document how you collect opt-in. Exclude opt-out from every outbound runtime. Keep transactional confirms only under a written policy. Preview wallet so a suppressed list is not ‘fixed’ by blasting SMS — SMS still needs MSG91 connected.

Write the consent line Your counsel. Product does not invent a ledger name beyond list exclusion and inbox handling.
Exclude from Growth Campaigns and drips. Reply-rate audiences must drop STOP.
Exclude from autonomous The checkup list query must not re-include opted-out rows.
Inbox policy Transactional slot confirms if policy allows. Still non-diagnostic.
Templates Library templates still need Gupshup approval. Opt-out footer per your policy.

How it runs on the platform

Consent is operational. Conversation agents, Growth, and autonomous must all see the same exclusion. 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 appointment booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup. The qualifier does not diagnose.

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 appointment booked.

Worked example: package campaign plus checkup list

A clinic runs a wellness-package Growth send. A row replies STOP. The same week an annual checkup autonomous query would have picked them. Ops exclude the contact. Appointment reminder for an already-held slot follows written policy — not a second marketing ping.

Playbook: opt-out compliance. Sibling template approval. Product: campaigns.

Where opt-out must apply

One contact. Every outbound runtime.

Runtime	Must honor STOP	Maybe transactional	Never
Growth campaigns / drips	Yes — list exclusion	If counsel says so	Ignore STOP because ‘health’
Autonomous lists	Yes	Rare — policy	Count them as contacted anyway for vanity
Conversation inbox	Ops policy	Slot confirms	Diagnosis
Voice blasts	Yes if marketing	Confirm calls per policy	HIPAA badge in the script

Honest limitations

This is not a HIPAA claim and not a substitute for your counsel. We do not invent a full consent-ledger product name. Not HIS.

Keep this Opt-in and opt-out article next to the job URL, not as a second playbook. Cite the definition above when an operator asks what the term means. Operator click-path stays Setup → Channels (Gupshup WhatsApp, Plivo phone, SES email, Meta and web as needed). Library templates. Agents → Studio, Router, Workflows, Autonomous. Customers → Pipeline. Appointments/calendars. Growth campaigns/drips. Organization wallet preview. 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 Appointment booked on the pipeline. Phone “replied” is speech-to-text. Qualifier is non-diagnostic. Emergencies: call emergency services. Not HIS/EMR. Preview the Organization wallet before a blast. Parent guides, healthcare hub, and pricing stay in the same runbook.

Canonical playbook: opt-out compliance. Email channel still matters for unsubscribes. Templates: template approval.

Frequently asked questions

Operators implementing this mechanic on a healthcare Project.

Is this HIPAA?

No. Honor opt-out on campaigns and templates; this is not a HIPAA claim and not a substitute for your counsel.

Does STOP stop appointment confirms?

Only per your written policy. Marketing lists must suppress. Counsel decides transactional exceptions.

Which playbook?

Opt-out compliance.

Autonomous still sending?

Fix the list query. Exclusion is operational.

SMS opt-out?

DPDP?

Your counsel. This page is the CoPulse click-path, not legal advice.

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

Suppress STOP everywhere you send

Growth, autonomous, templates — not a HIPAA badge. Ask counsel.

Get started free