“Please don’t call me again”: how a sales team should handle do-not-call requests

Every team that sells by phone hears it: “Please don’t call me again.” Sometimes it is polite, sometimes it is not. What happens in the next ten seconds decides whether that person is ever called again by someone on your team, and a surprising number of teams leave it to memory, a sticky note or a message in a group chat.

This is a working routine for those requests: what a do-not-call list is, why it matters more than the lead, how to record a request at the moment it is made, who should be allowed to lift it, and how to check that it holds.

What a do-not-call list is

There are two kinds of list, and teams often mix them up.

• Your own do-not-call list: the people who told your business, on a call, by email or in a message, that they do not want to be called. It belongs to you, and you are the only one who can keep it.
• National registries: lists that people join to refuse sales calls from businesses in general. Examples include India’s DND (the National Customer Preference Register run under TRAI’s rules), the US National Do Not Call Registry and the UK’s Telephone Preference Service (TPS). Australia, Canada and other countries have their own.

Screening against a national registry happens before you call a list, and it is covered in TPS screening and Do Not Call checks and, for India, in DND, consent and call recording. This article is about the first kind: the requests your own team receives. In many places the rules expect a business to keep its own list as well as screening against the national one, and to honour a request whether or not the number is on a registry. Check what applies where you call.

Why one ignored request costs more than the lead

A person who asked not to be called is not going to buy on the next call. Calling again cannot win the deal; it can only cost you.

• Complaints. A second call after a clear refusal is the call people report. Depending on the country, a complaint can reach your telecom operator, a regulator or a court, and several countries can fine a business for each unwanted call.
• Your numbers. People who feel harassed mark the number as spam in caller-ID apps, and every agent sharing that number pays for it in answered calls. Why business numbers get flagged as spam explains how labels build up.
• Your name. “They kept calling after I said no” is what ends up in reviews and in conversations with the person’s friends and colleagues.
• Your team’s time. Every call to someone who will never buy is a call not made to someone who might.

Most repeat calls are not deliberate. The request was heard by one agent and never reached the next one, or the lead was reassigned, re-imported or picked up from an old list. The fix is a process, not a warning.

Record the request at the moment it happens

The safest place to record a request is the screen the agent is already looking at, before the next call starts. A note written up at the end of the day is a note that sometimes does not get written.

1. Acknowledge it on the call. A short, calm line is enough: “Understood, I’ll make sure nobody from our team calls you again.” Do not argue or try one more pitch.
2. Mark the lead before you do anything else. Use a dedicated mark or outcome, not a free-text note that nobody filters on.
3. Write the reason in the person’s words, with the channel: “Said on the call: do not call again”, or “Replied STOP to our SMS”. Keep it factual and short.
4. Record who took the request and when. The system should do this for you, so it cannot be skipped.
5. Clear any follow-up on the lead, so no reminder tells someone to call.
6. Treat requests that arrive elsewhere the same way: an email reply, a message on WhatsApp, a word with a colleague at a trade fair. Whoever receives it marks the lead.

Make the request stick for the whole team

A request is only honoured if it holds for every person and every route by which the number could be called again.

• One list for everyone. The mark should travel with the lead, so a reassigned lead keeps it and a new agent sees it.
• Blocked at the dial, not just flagged. A coloured tag can be missed; a Call button that does not work cannot.
• Out of every queue. A marked lead should never come up as the next call, in any list or calling session.
• Kept, not deleted. If you delete the lead, the number can come back as a fresh lead in the next import or enquiry, with no record that the person refused. Keep the lead and keep the mark.
• Screened at import. Before you upload a list, remove the numbers on your own do-not-call list as well as any national registry that applies.

Who may lift a do-not-call mark

Sometimes the mark should come off: a person who refused last year now enquires about your product, or a request was recorded against the wrong lead. That decision should not sit with the agent who wants to make the next call.

• Let anyone who takes calls mark a lead, but let only a manager remove the mark.
• Remove it only when the person has clearly agreed to be contacted again, and record how and when they agreed. A new enquiry form they submitted, or an email asking you to call, is the kind of record to keep.
• Never remove marks in bulk to “clean up” a list for a campaign.
• Keep a history of every mark and removal: who, when and why.

Check that it works

A do-not-call process is only as good as its last check. A short monthly routine is enough for most teams.

1. Count the marks added and removed last month, and read the reasons on the removals.
2. Pick a few marked leads and confirm none of them was called after the mark.
3. Compare complaints with your list: any complaint from a marked number means something leaked.
4. Check recent imports were screened against your own list and any registry that applies, and keep the screening record.
5. Remind the team of the one-line script and where the mark is.

If someone complains, the history is your answer: when they asked, who recorded it, and that no call followed.

National registries to check

Your own list does not replace a national registry, and a registry does not replace your own list. Rules on who must screen, how often and for which calls differ widely, so check the official guidance for every country you call. A few starting points:

How LumaKol handles it

In the LumaKol web app, a do-not-call request is a mark on the lead. The guide Mark a lead as Do not call (DND) shows each step.

• Anyone who logs calls can choose Mark as DND on the lead page, with an optional reason, or mark many leads at once from the leads list.
• A red Do not call badge shows who marked the lead, when, and the reason. The lead’s follow-up is cleared.
• On the web, the Call button is disabled for a marked lead, click-to-call from the web app and the browser extension refuses it, and it never comes up as the next lead.
• Logging the outcome “Requested no contact” marks the lead automatically while the matching setting in Settings → Calling policy is on, which it is by default. The Android and iPhone apps already refuse to dial a lead with that outcome.
• Only owners, admins and team leads can remove the mark, after a confirmation. Every mark and removal is in the lead’s activity and, for owners and admins, in the security log.
• A filter on the leads list shows only marked leads, or hides them.

LumaKol does not check numbers against national registries such as India’s DND, the US National Do Not Call Registry or the UK’s TPS, so screen bought or cold lists before you import them.