A new revenue line from the customers you already have.
Your customers are asking for AI. You don't have to build it, staff it, or maintain it. We integrate our agent engine into your software — patients book through their own AI assistants (MCP + A2A), the phone line and WhatsApp. Under your brand, on your invoice.
Three reasons that cost you no roadmap.
Practices now switch practice software over AI features.
In the last 18 months almost every sizeable vendor in the German-speaking market has responded: built one, bought one, or picked a partner. The UK is running the same play a little later. For a vendor your size that makes a phone assistant less an innovation project than a reason for customers to stay — and for switchers to come.
- ✓Vendors who picked a partner early are selling the module into their base today.
- ✓Vendors without an answer still get the question — just without a solution.
- ✓The integration is the slow part. Build it early, sell it earlier.
- ✓Patients' AI assistants are the next booking channel — we make your practices reachable on it first.
Anyone can forward messages. We write into the calendar.
Most phone-AI vendors deliver transcripts your support team gets to re-type — or hang off file handoffs that know nothing about real-time availability. Our engine reads true availability (working hours, breaks, holidays per practitioner), books patient-linked, cancels as a status instead of deleting, and logs every action. The same write-path powers every door — the patient's AI assistant, the phone, WhatsApp. That's the difference your customers notice on day one.
What we need from your interface →Any practice software with an appointment calendar.
The speciality matters less than the fact that appointments are created in your system. From vendors with a few dozen practices to several thousand.
Four steps. Terms before code.
Questions from software vendors
What does the integration cost us?
Nothing. We build it at our own cost. Your contribution is technical access — an interface or a test system — and a point of contact who can answer questions.
What does the commercial model look like?
It depends how you want to sell it: as a module on your plan, bundled into a higher tier, or as a referral. We deliberately don't publish a one-size price — a vendor with 40 practices needs different terms from one with 4,000. We work it out on the call and put it in writing before anything is built.
Our software has no public API — is this still possible?
Yes. Our first production integration ran against a closed system with no official interface at all. With your cooperation the path is much shorter: a calendar layer, an internal API or a documented data model is enough for a plan measured in weeks.
Who handles support?
The proven split: your team takes first line (setup, customer questions), we take everything technical behind it — monitoring, model behaviour, integration maintenance. Your customers keep one point of contact: you.
Will our customers know a third party is involved?
Only if you want them to. White-label is the default: your name, your interface, your invoice. Some partners name us as their technology partner deliberately — that's your call.
What happens to our practices' data?
The practice stays the data controller, you're the processor, and we come in as a sub-processor. So you don't need a new legal framework — a data processing agreement with us and a sub-processor notice to your customers. We supply the DPA draft, sub-processor list and deletion concept.
What are MCP and A2A — and why should our platform care?
The open protocols AI assistants use to talk to services: MCP for ChatGPT/Claude-style connectors, A2A for agent-to-agent. In practice: a patient asks their assistant to book, the assistant talks to the engine, the patient confirms an SMS code, and the appointment is written into your system — with a full transcript. Being reachable over these protocols is what makes your practices bookable on the agent web — under your brand, before your competitors.
The model, not a menu.
We deliberately don't publish a one-size price — a vendor with 40 practices needs different terms from one with 4,000. What we do publish: how the money works, and what's always true before anything is built.
Three ways partners run it
Always true, whichever model
- ✓The integration is built and maintained at our cost — your contribution is access and a point of contact.
- ✓Terms go in writing before anything is built. No exclusivity without consideration.
- ✓Your brand, your invoice, your customer relationship. We never sell to practices directly.
- ✓Support split: your team takes first line, we take everything technical behind it.
- ✓Every channel is included — patients' AI assistants (MCP + A2A), phone, WhatsApp. No per-channel surcharges.
- ✓Pilot first: 3–5 practices from your base, measured results, then rollout.
Your customers are already asking.
20 minutes is enough to establish fit and a plan — including a live demo on the phone.