Short answer
If the app does not ring, first check whether the call reached the history. If it did, review the session, availability, notifications and device restrictions; otherwise investigate the number and route before reinstalling.
Key verification: Test the open app and locked device, recording arrival, notification and sound separately.
Sources and limitationsIf the phone system registers a call but the application does not ring, start with the session, status and notifications. If the call does not even appear in the call history, check the inbound number and route before reinstalling the app. Separating the two lets you locate the fault with fewer changes and without wiping the clues you need.
Locate the point where the alert is lost
An inbound call passes through four layers before it rings: it reaches the service, the flow offers it to an agent, the device receives the alert and the operating system turns it into sound. Each layer fails for different reasons, so the first task is to find out where it gets lost.
| Observation | First check |
|---|---|
| There is no call in the general history | Line, carrier, active number and arrival at the service |
| It exists, but no agent receives an alert | Flow, group members, business hours and availability |
| The desktop rings, the mobile does not | Mobile session, notifications and background execution |
| It only rings with the app open | System permissions and background restrictions |
| The notification appears, but without sound | Focus mode, Do Not Disturb and channel volume |
| It rings briefly and someone else answers | Group strategy and final outcome of the call |
A brief alert at one agent does not always mean the business missed the call. Find the final outcome before counting it as abandoned.
Checks in the application
CloudTalk links mobile reception failures to an expired session, the product's own notification pause, system permissions, Focus modes, battery and background restrictions, some manufacturers' tweaks and conflicts between several devices. Its inbound call diagnosis also covers empty groups, business hours and incorrect routes. Mobile reception diagnostics and inbound route diagnostics, consulted on 27 October 2026.
- Open the application and confirm the account, an active session and an available status. An update, a reinstall or a device clean-up may have ended the session.
- Check whether notifications are paused inside the product.
- Check notification and sound permissions in the system.
- During the test, turn off any Focus or Do Not Disturb mode that could silence it.
- On mobile, check battery and background activity restrictions following the system's and the manufacturer's guidance.
- Make one test call with the application open and another with the device locked.
Change one condition at a time and note the result. Do not clear the app's data as a first step: you could delete information useful for the diagnosis and end a session you still need for comparison.
Android and iOS: settings that change the behaviour
On Android 13 and later, a newly installed app's notifications are off until the user grants permission. Android's documentation exempts apps that manage their own calls and register as a calling account with the system. Along the same lines, CloudTalk asks Android users to check that its calling account is enabled: if it is not, the app may not ring when closed or when the screen is locked. Android notification permission.
From Android 14, the full-screen incoming call view depends on a permission reserved for calling and alarm apps, which the user can turn on or off. If, with the phone locked, you only see a notification in the status bar rather than the call screen, check that permission. Android 14 behaviour changes.
On iOS, CloudTalk advises checking lock-screen notifications, sounds, Focus modes and Background App Refresh. Also check scheduled Focus settings: a sleep schedule that switches on automatically reproduces the fault only at certain times.
Check the workstation and call route
From an authorised account, verify that the agent belongs to the correct group and that the line uses that group. Review business hours, holidays and fallback routes, without modifying a calendar that works for other numbers. Compare with an agent who does receive calls on the same route. CloudTalk also recommends that the step ringing an agent lasts at least 20 seconds and that the menu waits at least 10 before moving on; a shorter time ends the call before the mobile has finished ringing.
If the same user has several devices, document which ones are connected and where the alert appears. A desktop session may answer the call before the mobile rings, and a duplicate browser tab can confuse the test. If the agent is new, go through the verification for the first workstation on the phone system (in Spanish).
Worked example
An agent with an Android phone says calls "sometimes" do not ring. Instead of reinstalling, a matrix of 6 test calls is made from a number the team owns: 2 with the app open, 2 in the background and 2 with the screen locked.
| Condition | Calls | In history | Notification | Sound |
|---|---|---|---|---|
| App open | 2 | 2 | 2 | 2 |
| Background | 2 | 2 | 2 | 0 |
| Screen locked | 2 | 2 | 0 | 0 |
| Total | 6 | 6 | 4 | 2 |
Reading: all 6 calls reach the history, so the route works. The notification appears in 4 of 6 (66.7%) and sound in 2 of 6 (33.3%). The fault starts in the background and gets worse with the screen locked: it points to battery, the calling account or full-screen permission, not to the phone system. One condition is changed, battery usage set to "unrestricted", and the matrix is repeated. If the result becomes 6 of 6 in all three columns, the cause is narrowed down; if not, the next condition is checked.
Edge case: if the history showed 6 calls answered by the same agent on the desktop, the mobile would have no fault at all. The call would simply be delivered to another session.
Common mistakes and how to spot them
| Mistake | Symptom | Check |
|---|---|---|
| Reinstalling before looking at the history | The fault returns and there is no data to compare | Find the test call in the history before touching the device |
| Testing only with the app open | "It rings in the test", yet the agent keeps missing calls | Repeat with the app in the background and the screen locked |
| Ignoring the desktop session | The call shows as answered although the mobile did not ring | Check which device answered each call |
| Scheduled Focus | It only fails at certain times or on certain days | Review the mode's automatic schedules and note the time of each test |
| Group or ring time misconfigured | No agent receives the call or it rings very briefly | Compare with an agent who receives calls on the same route |
Sheet for a reproducible incident
Record the date with time zone, call identifier, inbound line, agent, system, version and device status. Add "reached history", "notification appeared" and "there was sound" as three separate observations. A screenshot of the phone's volume does not prove that the application received the event. CloudTalk asks support requests to include the OS version, model, notification screenshots and approximate times.
If the problem only occurs on one network, record that difference: a VPN or a corporate firewall can also interfere. If it affects the entire operation, use the continuity plan. If the app rings and connects but the sound is poor, it belongs in the audio diagnosis (in Spanish).
Closing criteria
Close the incident when the full matrix passes under normal working conditions, not merely because the app rang once after a restart. Repeat it at a different time of day to rule out a scheduled mode. If you are evaluating CloudTalk, include this test in the mobile and desktop pilot. Real notification behaviour must be accepted before you rely on it to serve customers.
From the author's experience
After 11 years implementing and supporting contact-centre phone systems (at Vocalcom), my first move with an app that does not ring is always the same: check whether the call actually reaches the agent and whether they are in the right group. If the call event shows up in the system but never appears on the workstation, I check notifications and the audio device before even considering a reinstall; in my experience, reinstalling without first looking at the history is the shortcut that wastes the most time.
On mobile, what I check first are battery restrictions, notification permissions and background execution, because any of them can stop an incoming call from being presented without producing any visible error.
When onboarding a new agent, the first thing I check is the link between agent, service and distribution group, and that the agent is in an available state; too short a ring time or too quick a jump to the next destination can also give the false impression that the agent is not receiving calls. To close an intermittent incident, one successful call is never enough for me: I run consecutive test calls, calls after changing status and calls after a period of inactivity, and I always need the exact time, call identifier, affected user and observed behaviour to correlate the workstation logs with the server's.
Sources and limitations
Documentary review: . Content type: Documentation-based guide.
- Mobile reception diagnosticshelp.cloudtalk.io
- inbound route diagnosticshelp.cloudtalk.io
- Android notification permissiondeveloper.android.com
- Android 14 behaviour changesdeveloper.android.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
CloudTalkOfficial plans and termsEstos enlaces llevan a las páginas oficiales de cada proveedor. CallsIQ no usa enlaces de afiliación. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.