Using Call

Blocking Unwanted Numbers in Call: Rules, Ranges and Messages

How to stop nuisance callers reaching your lines in Call: block a number or range, choose what they hear and review turned-away calls to protect real customers.

Call editorial team · Published · 6 min read

Every busy phone line attracts calls nobody wants: sales robots, a former customer who rings repeatedly, a person who abuses the agents who answer. Left alone, they steal time from the queue, wear down morale and can push genuine callers further back in line. Blocking is the blunt but effective answer, provided you use it with care.

A person at a desk looking at a list of blocked callers on a screen
Illustrative image

This guide explains when to block, how to build a rule in Call, how to decide what a blocked caller hears, and how to check that your rules catch the right people. For the wider picture of nuisance calls, see Spam Call Blocking for Business Lines.

When blocking is the right tool

Not every difficult call deserves a block. A customer who is angry once is a coaching topic; a caller who is abusive on every call is a different matter. Before you add a rule, ask whether the problem is the number, the behaviour or the process.

Choosing the right response

Block the numberHandle another way
Typical caseRepeated abuse, robocalls, harassment, wrong-number floodsA frustrated customer, a one-off complaint, a confusing menu
What you changeWhether the call reaches your lines at allHow agents handle it, or what the menu offers
RiskBlocking a real person by accidentAgents spend time on an avoidable call
GuidesThis articleHandling Harassment on Customer Calls and De-escalating Difficult Calls

A good rule of thumb: block on evidence. A pattern in the call history, such as the same number calling many times in an hour, or a note from agents, is better grounds than a single bad experience.

Building a blocking rule in Call

Open Settings, then Do-not-call and rules, and scroll to Call blocking. The form has three parts.

Adding a block

  1. Number or rangeType a full number, or a prefix ending in an asterisk to block everything that starts that way.
  2. WhyWrite a short reason, such as repeated abuse. Future you and your colleagues will be glad of it.
  3. They hearChoose what the caller experiences when blocked (see the next section).
  4. Press BlockThe rule applies to incoming calls straight away.
  5. Review laterPress Unblock on any row to let a number through again.

Blocking requires the admin or manager role. If you see a message that you do not have permission, ask someone with that role to add the rule or to change your role; see Roles and Permissions in Call.

Using ranges with care

A range is powerful because one rule can stop a whole batch of numbers that a nuisance caller rotates through. It is also the easiest way to block real customers. A short prefix can cover thousands of numbers, including a neighbouring business or a mobile carrier's whole block. Start with the longest prefix that still covers the pattern you see, and widen it only when the call history proves it is needed.

Deciding what a blocked caller hears

Call lets you choose the experience for each rule. The default tells the caller that the number is not in service, which is a polite way to end the contact without argument. The other choices suit other situations.

OptionWhat happensWhen it fits
Not in service messageThe caller hears that the number is not in serviceRobocalls and sales calls; the default
Straight to voicemailThe caller can leave a message instead of reaching an agentA person you want to hear from, but not live
SilentlyThe call is turned away without a messagePersistent abusers; avoids giving them anything to react to
Ask them to say who they areThe caller is asked to identify themselves firstNumbers you suspect but cannot be sure about
Let it through, but mark itThe call connects and is flaggedA trial rule, to see what it would catch before you stop calls

The last option is a safe way to test. Mark calls for a week, look at who the rule would have stopped, and only then change it to a real block. It is particularly useful for ranges.

Reviewing what your rules catch

A rule that is never reviewed becomes a liability. Call gives you two places to look. The Caught column shows how often each entry has stopped a call, so you can see which rules are active and which are dead weight. Below the list, a section of calls that were turned away shows the most recent blocked calls.

What to look for

  • Rules that catch nothingProbably a number that stopped calling. Consider removing it so the list stays readable.
  • Rules that catch a lotCheck that the callers are really unwanted; a heavily used rule is also a heavy risk.
  • Unknown numbers in the turned-away listA real customer calling from a new phone may be caught by a range. Look at the pattern.
  • Repeat attemptsSomeone calling again and again may be using several numbers; a range or a different approach may be needed.

A monthly blocking review

  • Open the turned-away list and scan for numbers that look like real customers
  • Check the Caught column and remove rules that no longer catch anything
  • Confirm each remaining rule has a clear Why
  • Ask agents whether new nuisance numbers have appeared
  • Test one blocked number to confirm the message is what you expect

Agreeing a blocking policy with your team

A rule list is easier to trust when everyone knows how it is made. Decide in advance who may add a block, what evidence is needed and how long a block stays. A small team might agree that a manager adds a rule after two reports from agents; a larger one might ask a supervisor to propose and a manager to approve.

Agents also need to know what to say when a genuine customer says they were cut off. A rule can occasionally catch someone it should not. The fix is quick when the agent can raise it straight away and a manager can press Unblock, so make that path obvious.

What blocking does not do

Blocking in Call applies to incoming calls. It does not stop your own team from calling a number. If you want to stop outbound calls to a person, add the number to the suppression and do-not-call list instead; The Do-Not-Call List in Call explains how.

It also does not stop a determined caller who changes number. Phone numbers can be spoofed or rotated, so blocking is a way to reduce noise, not to end it. Combine it with good menu design, so that robots fail to find an option, and with a clear process for agents who face abuse. The legal side of unsolicited calls varies a lot between countries; see Robocall Rules: An Overview for general background.

Doing it in Call

Go to Settings, then Do-not-call and rules, and use the Call blocking section. Enter the number or range, the reason and what they hear, and press Block. Keep an eye on the Caught column and the list of calls turned away, and press Unblock when a rule has done its job. Pair it with sensible agent support; the guide on Live Listening for Supervisors shows how a supervisor can step in on a hard call.

Frequently asked questions

Who can block numbers in Call?

Blocking needs the admin or manager role. Other users who try will see a message that they do not have permission.

Can I block a whole group of numbers at once?

Yes. End a prefix with an asterisk to block every number that starts that way. Use the longest prefix that covers the pattern, because short prefixes can block real customers.

What does the caller hear when blocked?

You choose per rule: a not-in-service message (the default), straight to voicemail, silence, a request to say who they are, or the call let through but marked.

Does blocking stop my team from calling that number?

No. Blocking is for incoming calls. To stop outgoing calls to a number, add it to the do-not-call list.

How do I know whether a rule works?

Look at the Caught column, which shows how often each entry stopped a call, and at the list of calls that were turned away.

Can a blocked number be allowed again?

Yes. Press Unblock on its row and the number can reach your lines again.

Add a call-blocking rule in Call

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

Related guides