If your outbound calls are failing, not connecting, or reaching the wrong recipient, this article explains how to identify the root cause and resolve the most common issues.
User level: Admin
Symptoms
You may notice one or more of the following:
The call fails immediately or never starts
The call rings but does not connect
The call reaches the wrong recipient
Only some agents or numbers experience the issue
Calls to certain countries fail while others work
Calls fail only at specific times of day
You see no clear error message in the app
Root Cause
Outbound call failures usually happen due to one or more of the following:
Insufficient credit
Company outbound calling disabled (non-payment or restrictions)
International calling disabled at account level
Country or prefix blocked in number-level settings
Incorrect number format
Carrier routing issues
Local device or browser problems
Destination country restrictions
Step-by-Step Solution
1. Check CloudTalk system status
Before you start troubleshooting, verify if CloudTalk is experiencing a known outage.
Use: status.cloudtalk.io
If there are any incidents or degraded performance alerts, wait for them to be resolved.
If the status page is clear, continue with the next step.
2. Verify Your Calling Credit
Outbound calls require a positive credit balance, even if your plan includes minutes.
Go to Dashboard > Billing > Credit
If your balance is positive, move on to the next step.
If your balance is close to zero or negative, outbound calls may be blocked. Add credit and try again.
Most customers begin to experience issues when the balance becomes very low (for example, just a few euros or dollars), but the exact threshold can vary depending on how often you make outbound calls and the destinations you call.
To avoid interruptions, we recommend turning on Auto Top-Up in your Billing settings.
If you’re unsure whether your balance is sufficient, contact CloudTalk Support and our team can check it for you.
3. Confirm That Calls to the Destination Country Are Allowed
International calls can be blocked globally at the account level.
Go to Dashboard > Account > Settings > International Calls
If the country is enabled, continue troubleshooting.
If the country is disabled (grayed out), outbound calls will fail.
If you cannot enable calling to that destination yourself, contact Support to assist you.
4. Check the Number-Level International Calling Settings
Even if international calling is allowed at the account level, individual CloudTalk numbers may have stricter outbound rules.
A number may be blocked from calling specific countries even when the account allows them.
To see whether a specific CloudTalk number is allowed to make international calls, go to Dashboard > Numbers > Select a number > Allowed international calling > Manage.
Review the list of countries and make sure the destination you are trying to call is available for that number.
Note on Number Types & Outbound Reachability
Some number types (especially toll-free) in some countries have limited or no outbound calling capability. See our full coverage table in the article Phone Number Coverage, Requirements & Functionality for details by country.
5. Confirm the Dialed Number Format
Incorrect format is one of the most common causes of call failure.
Check:
Full international format (starting with
+and country code)No missing digits
No spaces or special characters causing rejection
Dialing the correct carrier-supported prefix
If you're unsure, try calling another international number to see if the issue is destination-specific.
Correct format examples
US:
+14155552671UK:
+447912345678France:
+33123456789Germany:
+49301234567Australia:
+61412345678
How many digits does a phone number need?
Every country has a fixed total length for its phone numbers in international format. The number must include the + sign, the country code, and the local subscriber number with no digits missing or added.
The table below shows the total digit count (excluding the +) for some of the most commonly dialled destinations:
Country | Country code | Local number length | Total digits (after | Example |
United States / Canada | +1 | 10 | 11 | +14155552671 |
United Kingdom | +44 | 10 | 12 | +447912345678 |
Egypt | +20 | 10 | 12 | +201012345678 (mobile) / +20212345678 (Cairo landline -- 10 total) |
Norway | +47 | 8 | 10 | +4712345678 |
Germany | +49 | 3–11 (varies) | 6–13 | +49301234567 |
France | +33 | 9 | 11 | +33612345678 |
Australia | +61 | 9 | 11 | +61412345678 |
Netherlands | +31 | 9 | 11 | +31612345678 |
UAE | +971 | 9 | 12 | +971501234567 |
India | +91 | 10 | 12 | +919876543210 |
If the number you are dialling does not match the expected length for its country, the call will fail immediately, often with no audio and no clear error message in the app. Correct the number and retry.
6. Optionally Test from Another Device
To rule out issues on the recipient’s side:
Try calling the same number from your mobile phone
Try another CloudTalk number
Ask another agent to place the same call
If the number fails from multiple sources, the issue may be with the recipient or recipient carrier.
When to Contact CloudTalk Support
Reach out to Support if:
You verified your credit is positive
International calling is enabled
The number format is correct
The issue affects multiple agents or multiple numbers
Calls consistently fail to a specific country or prefix
The number works on mobile but not through CloudTalk
You need help activating a blocked destination country
To speed up the investigation, include:
1–2 recent failed call attempts
Call ID (if available)
Date/time and number dialed
The agent who attempted the call
Whether the call rang, failed instantly, or reached the wrong recipient
Carrier routing issues on specific destinations
CloudTalk routes outbound calls through a network of carrier partners, and each destination country (sometimes each mobile network within a country) is served by a specific carrier route. Occasionally a carrier on one of these routes starts rejecting calls, due to congestion, an outage, a change in routing agreements, or regulatory restrictions in the destination country.
When this happens, calls to that destination fail before they connect, while calls to other countries work normally. This is not caused by your CloudTalk settings. A strong sign of a carrier-side issue is that the same number connects when called from your personal mobile but fails through CloudTalk.
When you report a persistent failure to a specific country, our team confirms the failure pattern in your call history, checks the carrier route for that destination, and escalates confirmed carrier-side issues to our Voice engineering team, who work with the carrier to restore service or switch the destination to an alternative route.
While the investigation is in progress, calls to the affected destination may connect intermittently, so retrying at a different time can sometimes work. Support will keep you updated on progress in your ticket.
Outbound calls failing due to a payment issue
If your subscription payment fails, CloudTalk's connections to one or more of its carrier partners may be suspended. When this happens, outbound calls routed through those carriers will fail immediately, often showing a "line busy or declined" or "call rejected" message in the app, even though your CloudTalk settings look correct and calls to other destinations (or via other routes) may still work.
This is different from a low credit balance. It is caused by an unpaid subscription charge, not by the amount of calling credit in your account.
Signs this may be your situation:
Outbound calls fail immediately with a "line busy or declined" or "call rejected" message
The issue affects multiple agents and multiple numbers at the same time
Some calls (to certain destinations or via certain numbers) still succeed while others fail
You recently received a payment failure notification or a suspension warning from CloudTalk
What to do:
Go to Dashboard > Billing and check whether there is an outstanding payment or a failed charge on your account.
If a payment has failed, update your payment method or settle the outstanding balance. Instructions are in the article Why was my payment declined?.
Once the payment is resolved, carrier access is typically restored automatically. If calls are still failing after the payment clears, contact CloudTalk Support and include 2–3 recent failed call examples with the date and time.
Note: If you need to keep making calls while the payment issue is being resolved, contact CloudTalk Support. Our team can advise on whether an alternative routing option is available for your account in the interim.
Need help or have a question? Just reach out through our Support portal — we’re here for you.