Product Feedback: Allow Zendesk Talk number blocks to be scoped to specific phone lines | The place for Zendesk users to come together and share
Skip to main content
Newcomer
June 30, 2026
Accepted

Product Feedback: Allow Zendesk Talk number blocks to be scoped to specific phone lines

Related products:Voice
  • June 30, 2026
  • 4 replies
  • 96 views

1. Overview & who is affected

We're requesting the ability to scope a number block in Zendesk Talk to specific phone lines, rather than applying it across the entire instance. This would allow restrictions to be applied to certain lines (e.g., dedicated or premium support channels) without removing the customer's access to all other support pathways in the same instance. The lack of this capability affects admins (who configure the blocks), agents on restricted lines (who continue to receive calls that should be blocked), and customers (who cannot be selectively restricted in a way that matches operational needs).

 

 

2. What problem do you see this solving?

It would solve the binary nature of the current blocked numbers feature — today, admins must either block a customer from all Talk channels or allow full access, with no way to restrict access to specific lines while preserving access to others. This enables line-level access control aligned with how support tiers are typically structured within a single Zendesk instance.

 

 

3. Last impact, frequency, and business impact

This was raised most recently this week, when a request came in to block a single customer from accessing restricted support lines while keeping that customer assisted normally on the standard support channel — a configuration the native blocking cannot deliver, as any block applies instance-wide to all Talk numbers. Similar requests come up regularly when customer behaviour on a specific line needs to be managed (misuse, opt-out enforcement, dedicated-channel protection) without removing legitimate access elsewhere. The current limitation forces an all-or-nothing choice and, in practice, means these requests cannot be fulfilled at the platform level. The business impact is the inability to deliver tier-aware access control, which is a recurring need in support setups that operate multiple phone lines under the same Zendesk instance.

 

 

4. Are you currently using a workaround?

There is no automated workaround currently in place. Operational handling — agents identifying the caller and routing the case accordingly — is possible but unreliable, doesn't prevent the call from reaching the restricted line in the first place, and doesn't scale.

 

 

5. What would be your ideal solution?

In the existing blocked numbers configuration, allow the admin to select which Talk phone lines the block applies to, rather than the block being instance-wide by default. Blocks would then be honoured only on the selected lines, while non-selected lines would continue to receive calls from that number as normal.

 

 

    4 replies

    Rohan Gupta
    Product Manager
    July 1, 2026

    Hi ​@Eric134 ,

    thanks for the feedback. Though we do not have this directly at phone numbers level,

     

    There can be a couple of workarounds, to segregate customers and route them based on certain criteria :

    1. Using omnichannel routing - there can be trigger conditions that run on comment text contains - “+1111-caller phone” and route it to a specific group of agents/ or queue of agents. Omnichannel routing
    2. Using Voice AI agents in the EAP → Call gets connected to the voice AI agent which takes caller information and routes accordingly

     

    In both the above scenarios call comes on one phone number (rather than on multiple phone numbers) which routes it appropriately to desired group or queue.

    Can it work?

    thanks

    Rohan

     

    Ferran Barneda
    Product Manager
    July 1, 2026
    Updated idea statusFeedback submitted→Accepted
    Eric134Author
    Newcomer
    July 31, 2026

    Hello, ​@Rohan Gupta , thanks for your inputs! Unfortunately, it would bring more complexity to my scenario, and the workarounds would not fully solve my initial problem, given the nature of my products and the situation I described. Also, for item 2, Usage during the EAP is billed at standard rates, Zendesk also confirmed that there’s no option to provision additional credits to my Product.

    Martin Holmes
    Product Manager
    August 12, 2026

    Hi, 

    Thanks for the feedback. We will add this feature request to our backlog for future consideration. 

    If you would like to reconsider option 1 as a workaround (Using omnichannel routing), please get in contact with Zendesk Customer Support team and they will be happy to help you set it up.

    Thanks