Triage before you dial
CallTrackingMetrics Customer Service: Triage Before You Dial
We are not CallTrackingMetrics and cannot field their support calls. What we can offer is triage: customer service desks fix some problems and shrug at others, and knowing which layer your problem lives in saves the call entirely.
- Not their support desk
- Three problem layers
- Safe channels only
Support questions
Can you help with my CallTrackingMetrics account?
No — we are a separate Australian company with no access to their accounts. Their own support channels handle their customers; the safe route to those channels is their official domain, never a number from a search advertisement.
What problems does a vendor support desk actually fix?
Platform-layer problems: dashboard access, report configuration, billing queries, feature questions. Phone-layer problems — calls not arriving, numbers dead, routing wrong — belong to the number carrier, and hardware problems belong to your office.
Our calls stopped arriving — is that a support-desk call?
Usually not. Check whether the platform shows calls failing or just reports lagging; if calls themselves are dead, the trail runs to routing, answer points or the carrier — the diagnostic is in our outage guide.
A customer-service search happens when something is already wrong — and the worst moment to discover a fake support number. We are an Australian number provider, not CallTrackingMetrics, and their account holders are their business, not ours. What this page adds: the triage that tells you whether a vendor support desk can even fix your problem, and the channel discipline that keeps support searches safe.
The three layers, and who fixes each
Platform layer. Dashboard access, report configuration, plan and billing questions, feature behaviour. This is vendor support territory — their desk, their credentials, their help centre.
Phone layer. Calls not arriving, ringing out, misrouting, numbers behaving oddly. Vendor support can look at this only indirectly; the trail runs through routing configuration, answer-point hardware and the carrier that hosts the numbers. Carrier-side questions belong to the carrier — if your numbers are Australian and hosted with us, that desk is ours: contact us.
Local layer. Browser caches, office internet, handsets, headsets. Fixed by you in minutes, and worth checking before any call to anyone.
The safe-channel routine
Before dialling any support number found in a search: type the vendor'"'"'s domain yourself, use their logged-in console'"'"'s help section, and cross-check that both name the same channels. Never call a number from a search advertisement, and never hand codes or credentials to a caller you did not initiate. The routine in full — and the impersonation red flags — is in our support-number guide.
If the problem is your numbers, not their platform
The quickest self-test: ring one of your tracking numbers from a phone you trust. Calls arriving? Your problem is reporting, not telephony. Dead? Work the phone layer — routing first, answer points second, carrier last. That diagnostic, and the outage playbook built on it, is in our outage guide. And if the durable fix is numbers, routing and records under one Australian roof, that is what we run — number-based tracking from $5 a month per number, rates on the pricing page.
The layer we do answer for
Australian numbers, answered here
Number-based tracking from $5 a month per number — carrier-side support for routing, numbers and records.