For DMS vendors, distributors and data providers
Your workshops are open 45 hours a week.Their customers have questions the other 123.
A driver messages a workshop at eleven at night and hears nothing back until Monday. Ceptio’s assistant Mika takes those hours: she answers over WhatsApp, runs the intake like a service advisor would, and books the appointment straight into the system the workshop already runs. We’d rather bring that to your network than to one workshop at a time.
plate recognised · booked in Autoflex · handover: no
What Mika does
Not a website chatbot. A service assistant on the channel drivers already use.
Runs the intake
Licence plate, complaint, since when, preferred slot. She asks the follow-up questions a first-line mechanic would ask, and if she isn’t sure, she hands it to the workshop.
Identifies the vehicle
From the plate, via the national vehicle register and the workshop’s own customer history.
Books the appointment
With a DMS connection she writes it in directly. Without one, the complete intake lands at the front desk in a form the advisor can enter in one action.
Answers in the customer’s language
Dutch, German and English out of the box. She replies in whatever language the message arrives in.
Steps aside on request
The workshop can take over any conversation from the dashboard; Mika stays silent until they hand it back. Nobody is locked out of their own customer relationship.
Escalates instead of improvising
Damage, warranty, complaints, anything outside her scope: she says a colleague will be in touch and alerts the workshop.
Mika runs today and you can test her yourself in under a minute. The WhatsApp link above is the live assistant, not a scripted demo.
Ways to work together
Three models. No hidden preference.
Which one fits depends on how close you want it to your own brand and billing. We are open to all three.
| Model | Brand | Customer relationship | Your revenue | Effort on your side |
|---|---|---|---|---|
| 01 · Referral | Ceptio | Ceptio, with you introduced | Recurring commission on every workshop you bring in | Lowest, no build |
| 02 · White-label | Yours | Yours | You set the retail price; we invoice you wholesale | Branding + first line |
| 03 · Embedded | Yours, as a module | Yours | A module you can price into your existing plans | Joint integration |
Early partners set the order of the roadmap. The integrations we build, we build in the order our partners need them. Whoever comes in now decides what gets built first, and keeps that position as the list grows.
Integration
What an integration actually takes.
The honest version, so your technical people can judge it in five minutes instead of five meetings. Mika needs three things from a workshop management system. Nothing exotic, and nothing that writes where it shouldn’t.
| What Mika needs | Why | Access |
|---|---|---|
| Look up a customer and vehicle by licence plate or phone number | To recognise a returning customer and confirm the right vehicle | Read |
| Read availability | To offer slots that are genuinely free | Read |
| Create an appointment or work order | To put the booking in the system without anyone retyping it | Write, scoped |
A documented REST API with those three capabilities is enough. Where no API exists, Mika runs in intake-only mode from day one and the connection follows later. The workshop is never blocked waiting for it.
| System | Status | What that means |
|---|---|---|
| Autoflex | Connected | Appointments are written directly into the system |
| Any other system | Intake mode | Full intake delivered to the front desk; a direct connection is built on partner demand |
Typical build time for a new connection, once we have API documentation and a test environment: four to six weeks from first call to a workshop booking live. What we need from your side is documentation, a test environment and one technical contact, not a project team.
Why this is worth your attention
Four reasons, in plain terms.
For your platform
- It makes your platform stickier. A workshop that gets bookings out of your system at eleven at night has a reason to stay that has nothing to do with price.
- It’s a channel you don’t have yet. Phone and email are staffed. WhatsApp is where the customer already is, and almost nobody in this market is there properly.
For your timeline
- It’s built, not planned. The conversation engine, the vehicle lookup, the appointment booking and the human handover all work today.
- It crosses borders as it is. Mika replies in the customer’s own language without configuration, so a network spanning several countries doesn’t need several versions.
Data, security and who owns what
The workshop is the data controller; Ceptio is the processor. We don’t sell data on, we don’t use conversations to train AI models, and every sub-processor we rely on is listed publicly by name, purpose and region. A data processing agreement is signed before any workshop goes live. Our full security and privacy statement is published at ceptio.nl/beveiliging (in Dutch; we are happy to walk you through it in English or German).
Talk to us
Let’s find out in half an hour whether this fits.
No deck, no discovery process. Tell us what your network runs and we will tell you straight away whether a connection makes sense and what it would take.
Othman Hajji · othman@ceptio.nl