Players cannot reach support: what to check in the voice setup

A player says the support line did not answer. To an agent it looks like a missed call; to the technical team there are several possible failure points. Find where the call stopped before changing a queue or blaming a carrier.

Start with one traceable example

Collect the time and time zone, support number, caller’s country and network, approximate ring time and what the caller heard. Share the player's number only through an approved internal channel. Look for the call in the number provider's records and in your PBX log. If the provider never saw it, investigate reachability of the number and originating network. If it reached the PBX but no agent, check queue rules, schedules and available staff.

Look at very short answered calls too: a caller may have reached a menu and hung up before speaking to anyone. “Accepted by the system” is not the same as a conversation.

Check whether there is a pattern

Group examples by DID, country, network and time. A single unreachable number is different from a busy-hour queue issue. Arrange controlled calls from networks you can access; a successful test from the office phone does not necessarily reproduce a player's call from abroad.

Close the investigation properly

Record the failing leg, tests that confirmed it and the person responsible for the fix. Repeat the same calls afterwards and review unanswered-call records. Proton can provide DID numbers and a cloud PBX with queues, but the outcome also depends on your handling rules and agent availability.