Messaging and channels

Managing Opt-Outs and STOP Requests: A Practical Guide

How to receive, record and honour opt-out requests across phone, SMS, email and chat, so a person who says stop is never contacted again by mistake.

Call editorial team · Published · 6 min read

Marketing emails, text messages, chat messages and outbound calls all create the same risk: sooner or later somebody says "please stop contacting me". What happens next shows whether your contact process is under control. If the request is heard by one person, noted in a private file and forgotten, the customer will be contacted again, and the second contact is the one they complain about.

A support team member reviewing a shared list of contact preferences on a laptop
Illustrative image

This guide covers why opt-outs deserve priority, the routes they arrive by, how to automate the easy cases, what to record, and how to prevent a repeat contact. It pairs well with Following Up After Calls by SMS or Message and Managing a Do-Not-Call List in Call.

Why opt-outs come first

An opt-out is a customer's decision about the relationship. Handling it late or not at all produces complaints, blocked senders and lost trust, and in many places it can also create legal exposure. The practical rule is simple: a stop request outranks every other task in the same inbox, queue or call.

What counts as contact

Agree internally what "stop" covers, because customers rarely distinguish between kinds of messages. A useful split is:

Whether a stop request also ends service messages depends on your contract and the local rules, so write down your policy and phrase your confirmation accordingly. If you are unsure, ask the person which kinds of message they want to stop.

Where opt-out handling usually breaks

  • Verbal onlyA request is heard on a call and never written down, so the list never changes.
  • One channel onlyEmail is stopped but texts and calls continue, and the customer feels ignored.
  • Private notesThe request lives in one employee's notebook and disappears on leave or a role change.
  • No confirmationThe customer is never told it worked, so they ask again or complain.
  • Buried in a queueA stop request sits in a general backlog next to routine questions.

The routes a request arrives by

People do not read your policy. They reply to whatever message reached them, or they say it out loud. Plan for every route and make each one end in the same process.

RouteTypical wordingWho notices first
Email body"unsubscribe", "remove me"Whoever reads the shared mailbox
Unsubscribe linkOne clickThe sending system
SMS reply"STOP", "end", "no more"The messaging platform or its monitor
Chat or social message"stop messaging me", muting, blockingThe chat operator
Phone call"don't call me again"The agent on the call
Form or account pageA preference changeThe system
In person or by letterA comment at the counterFront-desk or office staff

Taking a request on the phone

A verbal request is the easiest to lose. Train agents to do the same few things every time, on the call and before wrapping up:

  1. Say that you will stop, without arguing or offering a discount.
  2. Confirm which channels to stop: calls, texts, email, chat, or all of them.
  3. Confirm the number or address the request applies to.
  4. Note the date and time and your name, then create the record before the next call.

In Call, an agent can add the number to the suppression list during the call, and the number is then refused before any dial is attempted. Customers should never need to ask twice.

Short keywords such as STOP

Keyword replies need rules. A reply that is exactly "STOP" is clear and should be processed automatically. A longer message that happens to include the word, such as a question about stopping a delivery, needs a person to read it. While a message is waiting for review, send nothing further to that person.

What to automate and what to check by hand

Automation is for speed, not for judgement. Stop quickly where the request is clear, and route the unclear cases to a person.

Automate or review

ExamplesHow to handle
Clear and mechanicalUnsubscribe links, exact STOP keywords, duplicate suppressionHandle instantly in the system and confirm
AmbiguousA verbal "leave me alone" with no scope, a message that mixes a complaint and a stop requestA named person reads it and replies the same day
SensitiveRepeated contact after an opt-out, a strong complaint, a legal threatEscalate to a supervisor or the person responsible for compliance

Notice that the second column is not "ignore". Whatever the category, stop contacting the person while you clarify.

A reliable processing flow

  1. ReceiveCreate a stop request record from whichever route it came in on.
  2. NormaliseClean the number or address: remove spaces and dashes, use one international format, lower-case email.
  3. SuppressAdd the identifier to the suppression list for the channels requested.
  4. PropagateMake sure every sending tool, dialler and campaign reads the same list.
  5. ConfirmTell the person it is done, using a short, neutral message where appropriate.
  6. AuditSample recent requests weekly and check that none still receive contact.

Normalising matters more than it looks. The same person can appear as a number with a country code in one system and without it in another, or as an old address left behind after a change. Match on the cleaned form, and suppress every record you find.

Records that stand up to a check

If a customer or an authority asks "did you stop contacting this person?", you need to answer quickly and with evidence. For every request keep:

Keep this record for as long as the suppression is in force. Deleting a person's details can be appropriate under privacy rules, but deleting their suppression entry means you may contact them again. The usual approach is to keep a minimal entry that only prevents contact. See Call Data Retention and Backups for how to think about retention more generally.

Preventing a repeat contact

Repeat contact after an opt-out almost always has one of a few causes.

Before every campaign or dial list

  • The suppression list is checked automatically, not by memory.
  • Imported lists are matched against the list before they are used.
  • Every tool (email, messaging, dialler, chat) uses the same list or syncs to it.
  • Partners and agencies who contact customers for you receive the list, or use your tools.
  • Old lists and exports are deleted or refreshed, not reused from a folder.
  • A manager signs off a campaign only after the list check is shown.

If it happens anyway

Mistakes will happen. Respond in a set order: stop the sending, add the identifier, apologise briefly and confirm that the request is now applied, then find the cause. Record the incident and the fix. A short, honest correction is better than silence.

Re-opting in

Contact can resume only when the person clearly asks to hear from you again, on a channel they choose. Record how and when they said so. Do not treat a purchase, a support call or a new form as permission to restart marketing.

Doing it in Call

Call keeps these controls in a few places so a request does not depend on a person remembering it:

Pair this with a shared mailbox where stop requests are tagged and handled first; see Shared Team Inboxes Explained and Customer Support on LINE Official Accounts.

Frequently asked questions

Should opt-outs be handled separately from normal enquiries?

Yes. Give them their own tag or queue so they are not buried under routine work. If a message contains both a question and a stop request, process the stop first and then answer the question.

What should an agent do when a caller says "stop calling me"?

Agree, confirm which channels it covers, and record the number and time before the next call. If your tool lets you, add the number to the suppression list during the call. Do not try to change their mind.

Can I keep an opted-out person's data?

Often you keep a minimal entry so you do not contact them again, even if other details are deleted. Rules differ by country, so check the official guidance or ask a qualified adviser.

Do I have to confirm an opt-out?

A short confirmation is good practice and reduces repeat requests, but requirements vary by channel and place. Keep it neutral, and do not use it to promote anything.

When can I contact someone again after they opt out?

Only when they clearly ask to hear from you, on the channel they choose. Record how and when they asked, and treat other interactions such as a purchase as insufficient on their own.

Review unsubscribed contacts and keep your do-not-call list current in Call

In the demo console you can try incoming calls in a simulation.

Related guides