Telecom and VoIP providers
Add an AI assistant to the phone lines you already provide
For telecom providers, VoIP providers and managed service providers that want to offer AI telephony to their business customers under their own name. Your numbers and SIP trunks stay where they are. We connect a voice assistant to them, give every customer its own organisation with its own usage, and build the rollout with you.
no number porting · organisation per customer · € 0,07/min orchestration · EU-hosted · DPA included
What you can sell
Four services your customers already ask about
Each runs on the lines and numbers your customers already have with you. Most providers start with one and add the next once the first one runs.
An assistant that answers the main number
The assistant picks up, answers questions from the customer's own information, takes a message and sends it on, or transfers the caller to the right person. The caller is recognised by the number they call from, which takes more care than it sounds.
After hours and overflow
The assistant only takes the calls the team cannot: outside opening hours, or when everyone is busy. Your customer keeps answering the phone as before.
One option in an existing menu
The customer's menu stays as it is, and only the option you choose goes to the assistant. It is the usual first step, because it changes nothing for the callers who choose another option.
Transfers back into the customer's own team
When a caller needs a person, the assistant transfers the call, warm or cold, to an extension or another number over your trunk. Where transfers go wrong, and how to test for it, is written up separately.
On your network
How it connects to what you already run
The questions a telecom provider asks before anything else, answered the way we set it up with you.
| What you need to know | How it works |
|---|---|
| Numbers | Numbers stay with you and on your customer's name. Nothing is ported, and your customer does not take out a second subscription. |
| Connection | A SIP trunk from your platform to ours, over which calls for the chosen number are offered to the assistant. No call forwarding, so no double call time on the customer's line. |
| Signalling and encryption | SIP over UDP or TCP. If your side supports SIP over TLS, we set the trunk up on that. |
| Caller ID | The caller's number in E.164 format, so the assistant can recognise the caller and look them up in the customer's own system. |
| Capacity | You tell us how many calls may run over the trunk at the same time, so capacity is the same on both sides. |
| Transfers | Outbound traffic over the same trunk, so the assistant can transfer to an extension, a fixed line or a mobile number at your own rate. |
| If the connection drops | The trunk is set up so the call falls back to the existing route, and the caller always reaches someone or something. We agree the fallback per connection. On our side, traffic moves to another data centre without your number or trunk changing. |
| Data and contract | Orchestration, dashboard, API and storage on EU infrastructure. A standard data processing agreement under GDPR Article 28 at no additional cost, and hosting and sub-processors documented in the Trust Center. |
| Automation | Organisations, assistants and numbers through the REST API and webhooks, so a new customer can be part of your own onboarding. An MCP server lets your team manage assistants from an AI assistant. |
The commercial model
You set the price, we invoice you for the platform
Every customer of yours is an organisation of its own, with separate assistants, numbers, calls and usage. Your parent organisation covers their usage, with a price per organisation, so you decide what each customer pays. Our fee is € 0,07 per minute of orchestration, with model usage passed through at cost. Over your own trunk the telephony is yours: you bill your customers your own call rates, and we charge nothing for connecting the trunk. What a minute costs in total is worked out in full, and the pricing page lists every line.
Who does what
You keep the customer, we run the voice layer
The split we start from. The details, including the support model, are agreed with you before the first customer goes live.
You
- The customer relationship, the offer and the invoice
- Numbers, trunks and the call routing on your platform
- First-line contact with your customer
- Your price per customer
We
- The orchestration layer, and keeping it running
- Building assistants with you and your first customers
- Reading problems at the SIP level, where most failed calls can be explained
- Failover between data centres, drilled on live traffic
Together
- The rollout plan and the first pilot customer
- Who your customers call when something is off
- How callers are told they are speaking to an assistant, which the EU AI Act requires
- When a customer needs everything on its own hardware, the on-premise route
Rollout
From the first call to the first customer
We start small on purpose: one customer and one number, then the next ones.
- 01
Partner call
Thirty minutes with the people who build and run the layer. We look at your customers, your platform and how you want to sell it. - 02
One pilot customer
You pick one customer and one number. We build the assistant with you and your customer, from their own information and their own transfer destinations. - 03
Trunk and test call
We send you the connection details, you set up the trunk and route the number onto it. For a provider that does this regularly it is usually about an hour of work. Then we call the number and check the connection and the sound together with you. - 04
Live, then the next customer
The assistant answers. Changes to the assistant go through our platform and ask nothing of your network. Each following customer gets its own organisation, created by hand or through the API in your own onboarding.
Questions
What telecom and VoIP providers ask
Do numbers have to be ported?
No. The number stays with you and on your customer's name. Only the incoming traffic for that number is routed over the trunk to the assistant.
Can the assistant sit behind an option in an existing menu?
Yes. The menu stays your customer's; only the chosen option is offered to the assistant over the trunk. It is a common first step.
What happens if the connection drops?
The trunk is set up so the call falls back to the existing route, so the caller always reaches someone or something. We agree what that fallback looks like per connection. On our side, traffic moves to another data centre without your number or trunk changing, as described on the reliability page.
What does it cost us?
€ 0,07 per minute of orchestration, plus model usage at cost. We charge nothing for connecting the trunk, and a transfer to a person is a normal outbound call at your own rate. You set the price your customers pay. The details are on the pricing page.
Can we sell it under our own name?
Yes. Your customers buy it from you, and each one is an organisation of its own under your parent organisation, with your price per organisation. A full white-label setup, including your own branding, is arranged with us.
Can we create customers automatically?
Yes. Organisations, assistants and numbers can be created through the REST API, so a new customer becomes part of your own onboarding instead of a manual step.
Where are the calls processed, and is there a DPA?
Orchestration, dashboard, API and storage run on EU infrastructure, and the Trust Center lists where each model provider processes data. A standard DPA under GDPR Article 28 is ready to sign at no additional cost. Why that matters for voice is written up separately.
Who supports our customers?
You stay the first point of contact for your customers. We handle what happens in the voice layer and read problems at the SIP level. How the hand-off between your support and ours works is agreed before the first customer goes live; who carries the pager is a question worth settling early.
Tell us which customers you want to start with
Thirty minutes with the people who build and run the layer. We look at your customers, your platform and your route to market, and tell you honestly whether a partnership fits.