The other 123 hours, a driver messages a workshop and hears nothing back until Monday. Ceptio's assistant Nova 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.
Not a website chatbot. A service assistant on the channel drivers already use.
Nova runs today and you can test her yourself in under a minute — the WhatsApp number in the header is the live assistant, not a scripted demo.
Which one fits depends on how close you want it to your own brand and billing. We're open to all three and have no preference we're hiding.
You introduce Ceptio to workshops in your network. We do onboarding, support and billing.
Nova runs under your name and in your visual identity. Your workshops see your product; we run the engine behind it.
Nova sits inside your own platform. Appointments appear in your planner as if they were entered by hand.
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.
The honest version, so your technical people can judge it in five minutes instead of five meetings.
Nova needs three things from a workshop management system. Nothing exotic, and nothing that writes where it shouldn't.
| What Nova 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 to appointments |
A documented REST API with those three capabilities is enough. Where no API exists, Nova 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.
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're happy to walk you through it in English or German).
No deck, no discovery process. Tell us what your network runs and we'll tell you straight away whether a connection makes sense and what it would take.
Othman Hajji
othman@ceptio.nl