My Phone Number Doesn't Ring
Callers get silence, a busy tone or a message instead of your agent? Work through these checks, from number setup to campaigns, webhooks and line limits.
Written By voiceaiwrapper
Last updated 26 days ago
You call your number and the agent never picks up. The caller might hear ringing that goes nowhere, a busy tone, a recorded message or silence. This article helps you find out which part of the chain stopped the call: the number, the agent, a campaign, your webhook, your phone account or your line limits.
The checks are in order, from the most common cause to the least. Most problems are found in the first three.
Before you start
- Check the call log first. On a VAW Native Pod (an engine or provider connection), open Call Logs. Every call that reaches your number gets a row, even a refused one, and the End reason tells you why it was refused. Use the table below to jump to the right check.
- Know which engine the number is on. VAW Native numbers are set up in VoiceAIWrapper. Numbers on Vapi, Retell AI and ElevenLabs Pods are set up in your provider account. If that's you, skip to the last section, Numbers on Vapi, Retell AI and ElevenLabs.
Calls that end with Concurrency limit reached are hidden from Call Logs by default. To see them, add the Missed calls filter and choose Include missed calls.
VAW Native numbers
Check 1: The number is ready
- In the sidebar, open Phone Numbers.
- Find the number and look at its Status:
What callers hear on an unassigned number comes from the Pod setting When a number has no assistant yet: Play a message (with the text in What the caller hears) or Busy tone. Edit the Pod from the Pod selector to change it.
Check 2: An agent answers the number
A number rings one agent. An agent can answer several numbers.
- On Phone Numbers, click the number.
- Click the agent row. It reads Answers as followed by the agent's name, or No agent connected with Connect agent.
- Under Who answers (followed by the number), pick the agent.
You can also do this from the agent: open it, go to Deploy β Inbound and click Connect number. If the panel warns that a number "is not reaching" the agent, click Retry, or Check connection to open the number. See Choose Who Answers a Number.
Check 3: An inbound campaign is holding the number
If the number belongs to an inbound campaign, the number sheet shows In campaign: followed by the campaign's name. The campaign decides what happens to every call:
- The number's own agent and inbound webhook aren't used.
- This applies while the campaign is Scheduled, Active or Paused. A paused campaign still holds the number.
- When the campaign can't take a call, the caller hears a busy tone and the call ends with Campaign not taking calls. It doesn't fall back to the number's own agent.
The campaign refuses calls when it's paused, hasn't started yet, is switched off with the Campaign Switch, is outside its calling window, or its agent no longer exists. Open the campaign and fix whichever applies:
- Click Resume Campaign if it's paused.
- Turn on its Campaign Switch on the Campaigns list. Turning the switch off pauses an Active campaign, and turning it back on doesn't resume it, so click Resume Campaign afterwards.
- Check Start Date, Days of the Week, Daily Calling Window and Time Zone in the campaign's Settings β Schedule.
To let the number's own agent answer again, the campaign has to let go of the number. A Scheduled campaign does this when you click Move to Draft. An Active or Paused campaign keeps the number until the campaign ends or is deleted. See Run an Inbound Phone Campaign and Campaign Statuses and the Campaign Switch.
Check 4: The inbound webhook rejected or delayed the call
If the number has an Inbound webhook (number sheet β Inbound webhook tab), VoiceAIWrapper asks your server about each caller before the agent answers.
- If your server replies with
"agent_id": null, the call is rejected on purpose. The caller hears a busy tone, and the call ends with Rejected by inbound webhook. - If your server doesn't reply within 5 seconds, returns an error, or doesn't return JSON, the number's default agent answers instead. These calls aren't lost, but the agent may answer without the details your webhook would have added.
Click Send test request to check what your server sends back. For a campaign number, the campaign's Pre-call context webhook is used instead and can reject the caller the same way. See Route Inbound Calls with the Phone Number Webhook.
Check 5: Credits and client billing
- Out of AI credits. When your balance runs out, inbound callers hear a busy tone and the call ends with Insufficient credits. Buy credits in Settings β Billing. See What Happens When You Run Out of Credits.
- Client billing paused. If the agent belongs to a client whose billing is paused, calls outside a campaign get a busy tone and end with Client billing paused. See What Clients See When Payment Is Due.
Check 6: Your Twilio account
VAW Native numbers run on your own Twilio account. If Twilio can't reach VoiceAIWrapper, or the call can't be checked against your Twilio credentials, the call never shows up in Call Logs.
If a connection failed its last check, Phone Numbers shows a red banner ("Calls to numbers on this connection are rejected until the credentials are fixed.") with Update credentials. Otherwise:
- On Phone Numbers, click Connected telephony accounts.
- Click Re-check next to the account.
- If you see "Inbound calls on this connection are being rejected.", click Update credentials and enter the current Account SID and Auth Token. This usually happens after the Auth Token was changed in Twilio.
Also check in your Twilio Console that the account is active and funded, and that the number is still in the account. Twilio's own restrictions, such as trial-account limits or voice geographic permissions for calling other countries, are managed in Twilio. See Connect Your Twilio Account to VAW Native.
Check 7: All inbound lines are busy
Each Pod has a set number of inbound lines. When they're all in use, the next caller hears a busy tone and the call ends with Concurrency limit reached.
Give inbound calls more lines in the Pod's Set Concurrency step: edit the Pod from the Pod selector, click Next to reach Set Concurrency, raise Inbound and click Update Concurrency. On VAW Native, the total is managed by the platform, so raising inbound lowers outbound. See Split Concurrency Between Inbound and Outbound Calls.
Numbers on Vapi, Retell AI and ElevenLabs
On these Pods the number lives in your provider account, so some checks happen there.
Vapi or Retell AI: the number shows "Sync required"
Vapi or Retell AI: the number shows "Sync required"
Open Phone Numbers. A number marked Sync required shows "Sync our webhook and remove default destination to use this phone number." when you hover it. Click Sync now.
After syncing, the number has no agent of its own. Each call asks VoiceAIWrapper which agent should answer, and the answer comes from an inbound campaign that uses the number. If someone re-attaches an agent to the number in your provider's dashboard, it goes back to Sync required. See Sync Webhooks So VoiceAIWrapper Can Track Calls.
Vapi or Retell AI: the number is synced but calls don't reach an agent
Vapi or Retell AI: the number is synced but calls don't reach an agent
A synced number only answers through an inbound campaign. The call isn't handed to an agent when:
- No inbound campaign uses the number, directly or through a phone number pool.
- The campaign isn't Active. Scheduled, Draft and Paused campaigns don't take calls.
- The Campaign Switch is off.
- The call arrives before the start date, after the end date, on a day not in Days of the Week, or outside the Daily Calling Window in the campaign's Time Zone.
- All inbound lines on the Pod are in use.
- The campaign's Pre-call context webhook rejected the caller.
Fix the one that applies, then call again. See Run an Inbound Phone Campaign.
ElevenLabs: the number doesn't reach the agent
ElevenLabs: the number doesn't reach the agent
ElevenLabs numbers don't need a sync. When you save an inbound campaign, VoiceAIWrapper assigns the campaign's agent to the number in ElevenLabs. Check in ElevenLabs that the number still has that agent assigned, and that the campaign uses the right number. Inbound campaigns on ElevenLabs have no status button, so the campaign's schedule doesn't decide when the number answers.
The provider account itself
The provider account itself
Check your provider's dashboard: the account must be in good standing with enough balance, and the number must still exist there. If the number is imported from Twilio or another carrier, also check that carrier account. See Phone Numbers on Vapi, Retell, ElevenLabs and Bolna.
Still not ringing?
Open Need help? β Help Chat and include the phone number, the time you called, your Tenant ID from Settings β General, and what the caller heard.
Related articles
Was this helpful?
More in Troubleshooting and FAQs
Calls Are Missing from Call LogsMy Custom Domain Won't VerifyCSV Import Errors and Invalid LeadsMy Webhook Isn't Receiving DataStill need help? Share an idea