Opt-Out Management for SMS, Text & WhatsApp in Salesforce
Your customer replies STOP to your marketing SMS. Two weeks later your WhatsApp bulk fires to the same customer. That’s a compliance failure with fines attached. Centralised opt-out in Salesforce closes the gap across every channel, every automation and every AI agent.
Why opt-out is the #1 compliance failure point
Your regulators in every jurisdiction, TCPA in the US, PECR in the UK, CASL in Canada, focus heavily on opt-out handling because it’s the easiest failure to prove. A customer says STOP. You send again. There’s no grey area. The violation is evident, and the penalty per message adds up fast.
Your technical failure is usually not a single bad send. It’s a disconnected system where one channel’s opt-out doesn’t propagate to the others. Email opt-outs live in the email platform. SMS opt-outs live in the SMS tool. WhatsApp opt-outs live somewhere else. Customers move channels, compliance stays siloed, and the fine finds you.
One consent record per Contact, four channels enforced
Your Salesforce Contact or Lead has separate consent fields per channel, SMS consent, text consent, WhatsApp consent, and optionally email. Each field carries the opt-in timestamp, the opt-in source and the current status. When a customer opts out, the relevant field updates. Every future send to that channel is blocked.
Your opt-outs can be channel-specific or blanket. “STOP” on SMS typically opts out of SMS marketing only, the customer might still want transactional texts or WhatsApp updates. “Unsubscribe from all marketing” blankets across channels. Your consent model supports both shapes.
Keyword recognition across languages
Your opt-out keywords your customers may use vary:
- English: STOP, UNSUBSCRIBE, END, CANCEL, QUIT, OPT OUT, NO MORE
- Spanish: PARAR, CANCELAR, BAJA
- French: STOP, ARRÊT
- German: STOPP, ABMELDEN
Your messenger recognises each variant in the language appropriate to the recipient’s region or profile, updates the Salesforce consent field, and confirms back to the sender that their opt-out is processed. The confirmation itself is compliant, “You’ve been unsubscribed” is not marketing.
Where the opt-out enforcement actually runs
Your opt-out enforcement sits at the Salesforce record level, not at the messenger UI. That means every send pathway you run respects it:
- User-initiated sends, the Send Message button blocks if consent is withdrawn
- Bulk sends, the send list skips recipients with withdrawn consent automatically
- Salesforce Flow, the Send Message action respects consent before firing
- Agentforce AI agent replies, AI responses respect consent before sending outbound marketing
- Scheduled sends, scheduled messages check consent at send time, not at schedule time
Your consent withdrawal on Monday morning propagates to your scheduled bulk send Tuesday afternoon without anyone on your team manually reconciling lists. Your Salesforce record is the source of truth; every pathway reads from it.
Audit evidence when a complaint lands
Your customer complains they received a message after opting out. Your audit trail produces the timeline in seconds: the opt-out timestamp, every send after that date, whether each send honoured the opt-out, the sender of any non-compliant send, and the Salesforce user who configured any override.
Your complaints you’ll field turn out to be customer confusion, they opted out of one channel but still get the others, or they forgot they’d opted back in. A clean audit trail resolves those in minutes. The few genuine compliance issues get surfaced with the evidence needed to act on them.