Integrations

An appointment that only exists with us is not an appointment.

This is the layer where most loose tools fail. If someone has to retype an appointment, that happens for two weeks and then no longer. That is why this page states, per integration, what actually exists, without a wall of logos.

Book a demo Where this sits in the system

Three words

Live, in development, planned.

Nearly every supplier lumps them all together. Here they mean something, and we stick to it.

live

It runs at a garage.

You can see it working in a demo, with real data. Not "nearly finished", not "in the test environment".

in development

It is being built.

There is code, but it is not yet at a customer. We do not name a delivery date we cannot meet.

planned

It is on the list.

There is nothing yet. It is listed because garages ask for it and because they decide the order.

The state of play

Everything on one page, including what does not exist.

Google Calendar live Appointments land directly in the calendar many workshops already plan with. This works today.

AutomaaT GO in development Appointments and customer data into the package, and availability pulled out of it before anything is promised. RDW registration in development Make, model, year and MOT expiry date based on the registration the customer gives. Autoflex planned From appointment to work order, with the workshop planning as the source instead of a separate calendar. WinCar planned Customer history and vehicle file as context under every conversation and every reminder.

Your package on request Is your package not listed? Tell us which one it is. The order in which we build comes from the garages taking part.

Without an integration this simply works

All ten workflows running
Appointments in Google Calendar or a calendar you designate
A daily list of everything that has been booked
Read back and export every conversation
A one-off export of your customer records as a starting point

Most garages start this way. An integration makes it neater, but no workflow is waiting on it.

What an integration does add

Nobody has to retype anything
Availability is correct at the moment of booking
One customer base instead of two that drift apart
Customer history as context under every conversation
An appointment that immediately becomes a work order

The order

Garages decide what is finished first.

Building an integration without someone who uses it straight away almost always produces the wrong integration. You then build what seems logical instead of what is needed. That is why we only build when there is a garage that will put it to use the following week.

See the pilot Tell us your package

Which package does your workshop work in?

Say so in the first conversation. We will tell you honestly whether it can be done today, how you start without an integration, and when there is more in it.

Book a demo