Live routing
Every call, the route it took, the carrier that answered and the latency it cost. Filter by market, by command, by outcome.
Sixty operators, thirty-five countries, one contract and one budget line, and a reviewer waiting to be told who holds the data. This is the page that says what moves to our side of the line.
What you integrate
Your engineers integrate once, against one contract and one credential. You can reach a mobile operator without us. What you cannot assemble on your own is governance over sixty of them at once, in more than thirty-five countries, under one contract, with one bill and one record of what happened. Adding a market, an operator or a version is a change on our side of the line, not a ticket on your roadmap.
Who reads this page
Wants the lawful basis, the data flow and the retention. All three are documented before the kickoff, early enough to enable the launch.
Wants to know the dependency cannot become an incident. The failure modes are named below, including what happens when nobody can answer at all.
Wants the price comparable and the contract exitable. The questions and the no-spread rule sit on the pricing page, with our own answers beside them.
What you operate
Every call, the route it took, the carrier that answered and the latency it cost. Filter by market, by command, by outcome.
Answer rate, declared gaps, p95 latency and cost per resolved decision, per market and per command. Exportable, and the same numbers we hold.
Turn a command on or off per market, cap spend, rotate a credential, add a user. No ticket, no waiting on us.
Any call retrieved by correlation id with the carrier, the version and the timestamp, in a form an auditor accepts.
Billing
Different cycles, different units, different definitions of a billable event, and a reconciliation job nobody budgeted for. We hold every one of those contracts and every one of those invoices. What reaches your finance team is one document, in one currency, on one cycle, with the per-call ledger behind it if they want to check.
Attribution
The record is in the dashboard, per call, and the invoice is reconciled against it.
Per callThe command, the market, the carrier that answered and what it cost.
Per declared gapRecorded, and not billed. A call nobody could answer is not a call you pay for.
Per cost centreSplit by your own tags, so the invoice arrives already allocated.
Against our own recordThe ledger you see is the ledger we reconcile against the operators. There is not a second one.
ExportCSV and API, on the cycle your finance system wants it.
Commercials
The average cost of supply in that country plus a minimal markup, rather than a blended rate that quietly overcharges you in the cheap markets to cover the expensive ones. Finance can defend each line.
One agreement covers every market we have onboarded, and every carrier, country and command arrives on a single invoice, reconciled against the record in your console.
The Enterprise plan is not self-serve. Tell us the markets, the commands and the volume, and the licence and the per-country rates come back as one number your budget owner can defend.
What exists today
Exercise it in the sandbox today, or read it in the contract today.
Data flow description per command, naming the operator or supplier route and the fields returned
LiveResponse-level provenance: the carrier that served the call, the specification version, and a correlation identifier
LiveDeclared fallback per use case, documented before you integrate
LiveSub-processor list and the supply routes behind each market
LiveFailure modes
The call fails over to another path, and the response names whichever carrier answered.
The response declares the gap at request time, and the call is not billed.
Normalised before it reaches you, and the version it ran on is in the payload either way.
A post-mortem with the request and response data, inside seventy-two hours, under the founders' names.
Regulatory context
Member States have to have a digital identity wallet operational by 24 December 2026, and regulated private-sector relying parties have to accept it by 24 December 2027 where they are already obliged to use strong user authentication. The wallet proves who a person is. The network proves that the phone channel you are about to use has not been taken from them. Regulation (EU) 2024/1183.
Ask for the data protection documentation and the sub-processor list and we will send both before you sign anything.