The service, scoped
Call Tracking Services: What the Service Includes
A call tracking service has four moving parts — the numbers, the network logging, the routing and the reporting — and knowing which part does the work is what keeps the price honest. Here is each part, and the boundaries we will not blur.
- Four parts, mapped
- Tracking from $5/month per number
- Boundaries stated, not blurred
Service questions
What does a call tracking service include?
The numbers themselves (a distinct one per campaign), network-side logging of every call, routing that delivers calls to your answer points, and reporting that aggregates calls per number over time — with recordings where enabled.
What is the service priced on?
Per number and per call: tracking numbers from $5 a month each, with call data billed per second against published per-minute rates. No bundles hiding the unit economics — the rate table is published.
What is not included, honestly?
Keyword-level attribution (that needs session-level platforms), conversation analytics and AI transcription (we do not sell them), and built-in CRM connectors (the CDR data layer is the honest alternative).
"Call tracking services" gets marketed as one amorphous thing — a platform, a dashboard, a promise. In practice a service is four moving parts, and understanding which part does which job is what separates a fit from an overspend. This page names the parts as we run them, with the boundaries stated.
Part one: the numbers
The sensor layer. A distinct tracking number — 1300, 1800 or local-pattern — is allocated to each campaign or medium you want to compare. The number is the entire attribution mechanism: no scripts, no sessions, no install. Numbers run from $5 a month each, searchable in the live pool on available numbers.
Part two: the logging
Network-side call capture: every call received on a number is recorded — arrival time, duration, answered or missed — before it routes anywhere. Because logging happens on the network, the measurement survives office outages, staffing changes and hardware swaps. The raw layer is exposed through the CDR area of our API, with records appearing within roughly one to two minutes of each call.
Part three: the routing
Delivery: the rules that land each call on a human — overflow behind busy lines, after-hours paths, round-robin across teams. Routing is configuration, not engineering, and it is where a well-set service stops losing callers. The patterns are in how 1300 numbers work.
Part four: the reporting
Aggregation: calls per number over time, durations, answered rates — the views that feed budget and staffing decisions. Console reporting covers the everyday questions; the API covers the custom ones.
The boundaries, stated
Three honest exclusions: no keyword-level attribution (session-level platforms'"'"' territory — the split is in what call tracking software is); no conversation analytics or AI features (we do not sell them); no built-in CRM connectors (the data layer is the alternative). Each exclusion keeps the service simple, and the price reflects it — the full table on the pricing page.
The takeaway
Four parts, each doing one job, priced per number and per second. If that scope covers your question — which medium earns its spend — the setup is an afternoon: our call tracking, live from the first call.
The four parts, working
Start the service
Search the pool free, take a number per campaign, read the first report within a week.