Why Is My Call Tracking Number Not Forwarding Calls?

A call tracking number usually stops forwarding for one of five reasons: a misconfigured forwarding destination inside the tracking platform, an outage or routing error at the carrier or SIP trunk level, a number whose local provisioning or porting has lapsed, a spam or DNC filter blocking the connection before it reaches your phone, or conflicting call flow logic between your CRM and the tracking system that overrides the intended route. Each of these produces a slightly different symptom, which is the fastest way to narrow down the fix. A number that rings busy on every call usually points to carrier capacity or a full ring group, while a number that goes straight to voicemail with no ring at all usually points to a forwarding destination that’s wrong, disconnected, or set to “always forward.”

Match the Symptom to the Likely Cause

• Immediate busy signal: destination line is on another call with no call waiting, a SIP trunk has hit its concurrent channel limit, or the carrier is rejecting the route.
• Straight to voicemail, no ring: the forwarding number in the dashboard is wrong, has a typo, is missing an extension digit, or call forwarding is enabled on the destination handset itself and intercepting the call before it rings.
• Dead air or a fast busy tone (reorder tone): the tracking number’s provisioning has expired, been released, or was never fully activated with the carrier.
• Call connects but drops within a few seconds: a spam-likelihood score or STIR/SHAKEN attestation issue is causing the receiving carrier to flag and terminate the call.
• Calls route to the wrong location or agent: the CRM’s call flow logic and the tracking platform’s call flow logic are both trying to control routing, and one is silently overriding the other.

Check the Forwarding Configuration First

Before assuming a carrier problem, confirm the basics inside your call tracking dashboard. Open the number’s call flow and verify the destination number is formatted correctly (full E.164 format with country code), that any extension or IVR menu digits are entered in the correct field, and that the number hasn’t been accidentally reassigned to a different campaign, location, or ad group during a recent edit. A surprising share of “broken” tracking numbers are simply pointed at an old destination after a team member updated a campaign and forgot to re-save the forwarding rule underneath it.

Rule Out Carrier and SIP Trunk Problems

If the destination number is correct, the next layer to check is the connection between the tracking platform and your phone system. SIP trunk registrations can drop silently, concurrent call limits can be hit during a traffic spike (common during a new ad campaign launch), and upstream carriers occasionally have regional outages that affect call completion without affecting SMS or dashboard access. If you use a hosted PBX or a VoIP provider like Twilio underneath your call tracking setup, check that provider’s own status feed for active incidents before troubleshooting further on your end.

Confirm the Number’s Provisioning Hasn’t Expired

Local and toll-free numbers are leased, not owned outright, and they require periodic verification with the carrier and regulatory bodies (including 10DLC or toll-free verification requirements in the US). A number that was provisioned months ago but never re-verified, or one that was ported from another platform and left in a pending state, can appear active in your dashboard while silently failing to complete calls. This is more common with numbers that haven’t received traffic in a while, since idle numbers are more likely to get flagged for re-verification or reclaimed by the carrier pool.

Check for Spam Filtering and DNC Blocks

Carriers increasingly score outbound-looking traffic for spam likelihood, and a tracking number that generates a high call volume in a short window (a common pattern during a paid ad surge) can get mislabeled as “Spam Likely” or “Scam Likely” on the receiving end. This typically shows up as calls connecting briefly and then disconnecting, or as unusually low answer rates compared to historical performance. Separately, if the number or destination is tied to a Do Not Call registry conflict, calls may be blocked or truncated entirely depending on your carrier’s compliance filtering. Checking your STIR/SHAKEN attestation level through your carrier is a useful diagnostic here if answer rates have dropped suddenly rather than gradually.

Look for Conflicting Call Flow Logic

When a CRM and a call tracking platform are both configured to manage routing, such as dynamic number insertion swapping numbers on a landing page while the CRM simultaneously tries to apply its own forwarding rule based on lead source, the two systems can fight over the call. Symptoms include calls that route correctly most of the time but intermittently land in the wrong queue, or calls that forward fine for one campaign but not another using the same underlying logic. Reviewing webhook delivery logs on both platforms for timeout errors or duplicate trigger events is usually the fastest way to spot this.

Run This Checklist Before Contacting Support

1. Call the tracking number from at least two different carriers (for example, your personal cell and a landline or a coworker’s phone) to rule out a carrier-specific block.
2. Confirm the forwarding destination number in the dashboard matches the intended phone exactly, including extension and country code.
3. Check whether call forwarding, Do Not Disturb, or a third-party call screening app is active on the destination device itself.
4. Verify the number’s provisioning and verification status hasn’t lapsed or flagged for review.
5. Check your carrier’s or SIP provider’s status page for active incidents in your region.
6. Review recent edits to the call flow, campaign, or routing rule for an accidental change.
7. Pull webhook or API logs between your CRM and tracking platform for timeout or error codes around the time calls failed.
8. Test during both low-traffic and high-traffic hours to see if the failure correlates with call volume.

How Real-Time Monitoring Catches This Before It Costs a Lead

Most of the causes above don’t announce themselves until a customer complains that they called and got nothing, by which point the lead has usually already called a competitor. Live call status tracking closes that gap by showing whether a call rang, connected, went to voicemail, or failed in real time rather than surfacing the problem only in a weekly report. Outbound webhook alerts take this a step further by notifying an admin or triggering an alert in a connected system the moment a call fails to complete as expected, rather than waiting for someone to notice a dip in answered-call numbers. For agencies managing call routing across multiple clients and campaigns, this kind of alerting matters even more, since a silent forwarding failure on one client’s number can go unnoticed for days without a dedicated monitoring layer. You can see current system uptime and any active incidents on the status page at any time.

FAQ: Call Tracking Forwarding Problems

Can a tracking number stop forwarding without any changes being made to it?

Yes. Carrier-side issues such as spam flagging, provisioning expiration, or an upstream outage can all break forwarding even if nothing was changed in your dashboard, which is why checking carrier status and verification state matters as much as checking your own settings.

Why does the number work for some callers but not others?

This pattern almost always points to carrier-level spam filtering or regional routing issues rather than a dashboard misconfiguration, since a true configuration error would affect every caller equally.

How often should I test my tracking numbers?

Testing after any campaign change, routing update, or CRM integration edit is the minimum; businesses running high call volume from paid ads benefit from a recurring weekly test call to each active number to catch silent carrier flags before they affect a real lead.

If forwarding failures keep slipping through unnoticed, it’s worth evaluating whether your current setup gives you visibility into call status the moment something breaks, rather than after a prospect has already given up. Get Started Today to see how Power Answer’s real-time call status and webhook alerts are built to catch exactly these failures before they cost you a lead.