Live routing
Every call, the route it took, the carrier that answered and the latency it cost. Filter by market, by command, by outcome.
Enterprise
Sixty operators, thirty-five countries, one audit 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
One endpoint and one contract.
Every operator behind it is our challenge.
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
Three reviewers, three different questions.
01
The Data Protection Officer wants the lawful basis, the data flow and the retention, settled before anything ships
Documented rather than promised, and early enough to enable the launch instead of blocking it.
02
The security architect wants to know the dependency cannot become an incident
The failure modes rather than the happy path. They are named below, including what happens when nobody can answer at all.
03
Procurement wants the price comparable and the contract exitable
The nine questions and the no-spread rule sit on the pricing page, and five of the nine we cannot yet answer.
What you operate
A console, not a support queue.
The KPIs you are measured on
Answer rate, declared gaps, p95 latency and cost per resolved decision, per market and per command. Exportable, and the same numbers we hold.
Controls that are yours
Turn a command on or off per market, cap spend, set the fallback behaviour, rotate a credential, add a user. No ticket, no waiting on us.
Evidence on demand
Any call retrieved by correlation id with the carrier, the version and the timestamp, in a form an auditor accepts.
Billing
Carrier invoices arrive on different cycles and units. You get one.
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
Where every number on that invoice came from.
The record is in the dashboard today. The export into your own audit systems is in build, and it carries a date rather than a promise.
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 Enterprise plan.
Each market priced as itself
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.
Orchestration Full
Routing you configure rather than presets you select, data enrichment, one contract and one invoice across every market, and compliance and DPO support through your review. This is the enterprise edition and it is priced as one.
Clean Transparency, not available yet
Bring a contract you already hold. That supply runs at your rate on your paper, the supplier invoices you directly, and we take no margin and no per-call fee on it. Available on this edition and no other.
What exists today
What a reviewer can exercise today, and what is still being written.
Exercise it in the sandbox today, or read it in the contract today. Anything not marked live carries a date and no other claim.
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
LiveThe data protection and audit dossier as a single artefact for your reviewerThe capability is in the product. The document is being written.
In buildThe routing ledger: per-call supplier, route, latency, outcome and cost in your own account
In buildThe pass-through audit right, letting you or your auditor inspect the supplier invoices behind your own callsIn drafting.
In buildThe consumer consent portal with change callbacks
DesignedData flow
Three tiers, and they differ in what happens to the data.
The tier is chosen per command, not per contract, and it is the tier that decides whether the controller and processor analysis changes.
| What happens | Tier 1 passthrough | Tier 2 multi-source | Tier 3 enriched |
|---|---|---|---|
| The request | Routed to one supplier and returned | Sent to several suppliers for the fullest set on that line | Routed, then enriched with our own data |
| Manipulation of the answer | None | Responses reconciled into one shape | Network answer combined with our own record |
| Retention of subject data | The number and the answer for up to 2 years, logs for 180 days | The same | See the Security page, which is the reference |
| What the response names | The carrier that served it | Every source called | The sources called and what was added |
| Relative cost | The base rate | Twice tier one | Quoted per command |
| Controller and processor split | Unchanged | Unchanged | This is the tier where it changes |
The tier a command runs on is visible in your console and stated in the contract.
Failure modes
What happens when it does not work.
01
A route is down
The call fails over to another path, and the response names whichever carrier answered.
02
No operator has launched
The response declares the gap at request time, and the call is not billed.
03
An operator changes a version
Normalised before it reaches you, and the version it ran on is in the payload either way.
04
Something breaks in public
A post-mortem with the request and response data, inside seventy-two hours, under the founders' names.
Regulatory context
Two dates your programme is already planning around.
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.
Bring your reviewer to the first meeting.
Ask for the dossier and the sub-processor list and we will send both before you sign anything.