Block known unwanted callers
Add phone numbers your team has decided to suppress. Use a deliberate rule rather than asking each receiving team to remember the same unwanted caller.
Unwanted caller blocking
Keep your call rules in your hands.
Manage suppression rules by phone number, ZIP code, or tag and check whether a caller is allowed.
Conversation intelligence · Built for US call workflowsUnwanted caller blocking
- Rule typeBlocked phone number
- Caller checkMatches suppression rule
- ResultNot eligible for this workflow
Identify the reason
Decide why the caller or traffic group should be excluded.
Unwanted caller blocking
- Rule typeBlocked phone number
- Caller checkMatches suppression rule
- ResultNot eligible for this workflow
Save the rule
Apply the appropriate phone, ZIP, or tag condition.
Unwanted caller blocking
- Rule typeBlocked phone number
- Caller checkMatches suppression rule
- ResultNot eligible for this workflow
Review the effect
Check the rule's result and adjust it if the intended scope changes.
Explore the steps above. Sample details show the workflow, not a live account.
Conversation intelligence
What changes in your day.
When your team identifies a caller or traffic pattern that should not enter a workflow, the rule needs to be clear and repeatable. Suppression controls keep those decisions close to the call operations they affect.
Apply broader rules carefully
Use ZIP codes or tags where the workflow calls for them. Review the scope so a broad rule does not accidentally exclude people you intended to serve.
Check the reason behind a result
Review whether a caller is allowed and investigate unexpected exclusions. Keep manual suppression separate from an automated spam assessment.
From setup to review
Put it to work.
- 01
Identify the reason
Decide why the caller or traffic group should be excluded.
- 02
Save the rule
Apply the appropriate phone, ZIP, or tag condition.
- 03
Review the effect
Check the rule's result and adjust it if the intended scope changes.
A closer look
Useful answers before you start.
Explore the workflow above, then bring your own requirements to an early-access conversation.
Does this use the same controls as spam screening?
No. Suppression rules are the conditions your team maintains. Spam screening uses caller checks to assess incoming calls before routing.
Can a ZIP rule affect more than one caller?
Yes. A rule based on location or a tag may affect a group of calls. Review its scope before applying it to an active workflow.
Meet your next growth tool
Let’s connect the dots on your calls.
Get an early look at Lead Source, built for the way your business handles calls.