The stack between a dial tone and a settled payout
Four layers — capture, qualify, route, settle. Each one produces evidence the next one depends on, which is why disputes on this network are rare enough to be interesting.
Platform
What happens in the four seconds before a call connects
Most of the work is done before anyone says hello. By the time a buyer's phone rings, the call has been attributed, screened, scrubbed, and auctioned.
Capture
Dynamic number insertion assigns a tracked number per visitor session. Click identifiers, UTMs, and the originating URL are persisted with it, so a call arriving ten minutes later still resolves to the keyword that produced it.
- Session-level number pools
- GCLID / MSCLKID / FBCLID capture
- First-party session stitching
Qualify
An IVR gate screens for geography, intent, and offer criteria before anyone is connected. Duplicate suppression and DNC scrubbing run in the same pass.
- Custom criteria trees per offer
- Federal and state DNC scrubbing
- Configurable duplicate lookback
Route
A ping-post auction runs inside the greeting while the caller is still on the line. Routing reads live buyer capacity, licensing, and business hours, then connects the best match on the first ring.
- Sub-200ms p99 decision time
- Concurrency caps per buyer
- Automatic failover within one attempt
Settle
Billability is decided against the published rules and reconciled to carrier call detail records. Recording, transcript, and CDR attach to the record that both sides read.
- Carrier CDR reconciliation
- Evidence-attached disputes
- Weekly publisher payment runs
Every number decomposes
Aggregate dashboards hide the thing you need. Every metric on the platform drills to the individual calls behind it, including the ones that were rejected and why.
- Per-call rejection reasons — short duration, wrong geo, failed gate, duplicate
- Attribution down to keyword, ad, creative, and landing page
- Billable rate segmented by source, state, day-part, and hour
- Recording and transcript on every call, one click from the row
Data where you already work
Attribution that lives only in our dashboard is attribution nobody acts on.
Webhooks & REST API
Per-call payloads with recording URLs, delivered on completion or polled on demand.
Warehouse delivery
Scheduled CDR exports to S3 or GCS in Parquet or CSV, partitioned by date.
Ad platform conversions
Offline conversion imports to Google Ads and Microsoft Ads with original click identifiers and values.
CRM logging
Salesforce and HubSpot call logging with the full qualification response set attached.
How the platform actually behaves
See it against your own numbers
Bring a month of your current call data and we will show you what the same volume looks like with rejection reasons attached.