Support, triaged
CallTrackingMetrics Support: The Triage Before the Ticket
We are not CallTrackingMetrics and their support desk is theirs — reached from their domain, never from a search advertisement. What this page adds is the triage: three self-tests that tell you which helper your problem needs before you wait in any queue.
- Their desk, their domain
- Three self-tests first
- The carrier bucket, ours
Support questions
How do I contact CallTrackingMetrics support?
Through their official domain — the contact page or the help section inside your logged-in console. We cannot field their support, and we will not print their channels secondhand; official domains are the only safe source.
What should I test before contacting support?
Three quick tests: ring a tracking number from a trusted phone (is the phone layer alive?), reload the dashboard in another browser (is it local?), and check recency (CDR-style data can lag minutes). The answers route you to the right helper.
Who fixes routing and number problems?
The carrier that hosts the numbers — a different desk from the software vendor. If your numbers are Australian and hosted with us, routing, reachability and call records are answered here, directly.
Support searches happen mid-problem, and mid-problem is exactly when the triage matters. We are an Australian number provider, not CallTrackingMetrics — their support desk is theirs, reached from their domain. What this page adds is the triage that runs before any ticket: three self-tests, three buckets, and the reason the bucket you land in decides who can actually help.
The three self-tests, in order
- The call test. Ring one of your tracking numbers from a phone you trust. Calls arriving? Your telephony works, whatever looks broken. Dead? You are in the phone bucket — routing, answer points, carrier.
- The browser test. Open the dashboard in another browser or device. Fixed? The problem was local — cache, network, extension — and the ticket dies here.
- The recency test. Call detail data can lag by minutes. Data "missing" for five minutes is not an outage; check the clock before checking the vendors.
The three buckets, and their helpers
- Platform problems — access, reports, billing, features: the vendor'"'"'s desk, reached via their official domain. Their docs and help centre answer most of it without a queue.
- Phone problems — calls not arriving or routing wrong: the carrier'"'"'s desk. Software vendors cannot fix a phone network path; the carrier owns it. If your numbers are Australian and hosted with us, this desk is ours — contact us.
- Local problems — yours, in minutes, with the tests above.
The layer reasoning behind the split is in our help triage page, and the full diagnostic sequence in our "down" guide.
The channel discipline
Support searches are a favourite hunting ground for fake support numbers: type the vendor'"'"'s domain yourself, cross-check channels inside the logged-in console, never call a number from a sponsored result, and never hand codes or credentials to an inbound caller. The routine in full is in our support-number guide.
The takeaway
Three tests, three buckets, three helpers — and most problems die at the self-tests. When the bucket is the phone layer and your numbers are Australian, that helper is us: number-based tracking from $5 a month per number, with the rates on the pricing page.
The desk for the phone layer
Numbers and routing, answered directly
Number-based tracking from $5 a month per number — one provider for numbers, routing and records.