Skip to main content
EzyConn
Two cars raised on lifts in a working service bay, a stripped bumper and wheel on the floor between them

3 processes for automotive · 2 complete

Booking for independent workshops and mobile mechanicson the ramp diary you already keep.

A driver messages while you are under a car. EzyConn asks what it is in for, offers times the ramp is genuinely free — two hours for a full service, forty-five minutes for the annual inspection — and books it. For mobile work it checks where the car is before it promises anything.

Start freeRead the limits first

The limit, up front: No dealer management system, no VIN decode, no parts or warranty lookup.

The problem

What a workshop week looks like

Four situations that need answering and need no judgement at all. Every one of them is somebody being interrupted, or a customer going somewhere else.

  1. 01

    Every call is answered with oil on your hands

    There is no counter separate from the workshop. Whoever picks up puts a job down to do it, and the calls that need no skill at all are the ones that interrupt the most.

  2. 02

    A ramp booked to a car that never arrives

    It is the most expensive hour of the week, and it is only re-sellable if somebody hears about it in time to sell it. Most cancellations arrive at eight in the morning, by phone, to a workshop already under a bonnet.

  3. 03

    The customer cannot tell you what the job is

    They can tell you what the car is doing — a light, a noise, it will not turn over. That is a different set of questions from "book my annual inspection", and asking the wrong set is how a forty-five minute slot gets a two-hour job in it.

  4. 04

    Mobile work starts with the question nobody asks first

    Where is the car? Half a mobile operator’s enquiries are forty minutes outside the patch, and you normally find out after taking the name, the number and the symptom.

Gloved hands working across the valve seats of a cylinder head on a bench

Real enquiries

What arrives, and what happens to it.

The two booking processes recognise different intents, and the difference matters — one is a driver who knows what they want, the other is a driver whose car is on a driveway.

  • Car's due its annual inspection — what have you got next week?

    Ramp times offered, booked at your own length

  • Engine light's on and it's driving rough. Can someone come out to it?

    Coverage checked, callout booked at the vehicle

  • It won't start at all. It's on a driveway in LS12 — do you come out that far?

    Coverage answered from your own postcode list

  • Brakes are grinding. How long would you need the car for?

    Your own job length quoted back, then booked

  • I'm booked Friday for a full service and can't get it there.

    Job found, moved to a free ramp time or cancelled

The processes

Three processes, built for automotive.

Each one is published with its status. Complete means every step runs. Available with a limit means it runs and something named is missing — and the name of the missing thing is on this page and on the process page.

Every industry runs on the same handful of shapes carrying different data, which is why a new trade is a configuration change rather than a rebuild. Browse the whole catalogue.

The outcome

What a finished job looks like.

An appointment against the ramp diary, for the length that job actually ties a ramp up — because a full service and an annual inspection are not the same hour.

AUTO-01

Appointment booked — service booking

These are the starting labels and lengths. You replace all of them with your own, and the times offered are computed from yours.

Full service
2 hrs
Interim service
1 hr
Annual inspection
45 min

AUTO-02

Appointment booked — diagnostic or repair request

These are the starting labels and lengths. You replace all of them with your own, and the times offered are computed from yours.

Mobile diagnostic
1 hr
Brakes
2 hrs
Battery & charging
45 min

It carries the customer name, a number the format check accepted, an email, whether the car is off the road or drivable, and whatever they typed about what it is doing. Mobile jobs also carry the postcode you confirmed you cover. A confirmation email goes to the customer.

What you configure.

Your own jobs, your own lengths, your own prices, your own hours. The service area is only needed if you do mobile work — a workshop customers drive to has no catchment.

  • Your opening hours

  • Your timezone

  • The postcodes you cover

  • Your services, their length and their price

  • Your price list

Without opening hours and a timezone, a booking process offers nothing and hands every customer to a person. That is deliberate — an appointment at a time you are shut is worse than no appointment.

The limits

What EzyConn will not do for automotive.

The honest scope here is the independent workshop and the mobile mechanic. It is not a franchise service drive, and pretending otherwise would waste a dealer group’s time in the first week.

No dealer management system, no VIN decode, no parts or warranty lookup.

  • No dealer management system, and no connector to one

    A booking made here does not reach a dealer management system, because there is no such connector in the product and none is declared as coming. Warranty position, prepaid maintenance, open recalls, advisor capacity and courtesy cars are all invisible to it. A main-dealer booking that never reaches the DMS is one an advisor has to re-key, which is worse than no booking at all.

  • The car is prose, not data

    There is no registration lookup and no VIN decode. No parts check, no labour-time lookup, no operation-code menu, no recall lookup and no inventory of any kind. What the customer types about the car is stored as words on the job for whoever reads it.

  • It books a visit. It never books a price

    Your price list carries one flat price per job with no variants, so "what will it cost for my car?" cannot be answered and is never implied. The visit is booked; the price comes from whoever looks at the car.

  • The coverage check on mobile work runs first, and it is blunt

    Postcode before anything else. That is the right order — but it means a driver just outside your list is turned away by a rule, even though you would happily have gone. There is no override in the conversation.

  • Two cars, one customer

    The appointment has no registration, make or model on it. A customer with two cars booked in the same week is matched on their contact details alone, and when more than one job matches, the process stops and asks a person rather than guessing which one to move.

  • No calendar sync, of any kind

    Not Google Calendar, not Outlook, not Calendly. Availability is worked out only from appointments EzyConn made itself, so a time you blocked out in your own calendar is still offered to a customer.

  • No system connectors

    There is no customer-record, scheduling-system, order or field-service connector in the product. Everything that leaves does so through Zapier or a signed webhook to your own endpoint.

  • The confirmation is an email, never a text message

    No process sends SMS. The confirmation email is best-effort: if the queue behind it is down, a real appointment can be made without the email arriving. A cancellation sends the customer nothing at all — the chat window is their only confirmation.

  • Nothing is paid for in the conversation

    There is no payment step anywhere in a process. No deposit, no card, no voucher, no balance.

  • A service area is a list of postcodes, not a radius

    You give a list of postcodes or a prefix to match on, for one country. A radius is refused outright, and so is covering everywhere.

Every limit these three processes publish

Written by the people who built them, carried onto this page unedited, and shown in full on each process page.

  • A confirmation EMAIL is sent.
  • No individual member of staff is chosen.
  • No registration or VIN decode, no op-code menu, no labour-time lookup and no parts check.
  • This is not a franchise service drive.
  • Urgency is written onto the appointment for whoever works it.
  • The vehicle is described in free text and nothing decodes it.
  • It books a VISIT, never a price.
  • A cancellation sends the customer NOTHING.
  • IDENTIFICATION IS NOT AUTHENTICATION.
  • A cancelled appointment is not RE-booked.

Channels

Where your customers already are.

A garage is reached by phone and by whatever the customer already has open. Both go to the same agent, with the same diary behind it.

  • Your phone line

    The call that comes in while both ramps are occupied, answered on your own Twilio number.

    You connect your own Twilio number. Inbound only — EzyConn does not make outbound calls.

  • Your website

    The evening booking. Most service bookings are made after the workshop has shut.

  • WhatsApp

    Where a driver sends a photo of a warning light and expects a reply the same evening.

  • Email

    The enquiry form and the reminder chase, answered or routed rather than queued.

  • Slack

    Where the office picks up a handed-over conversation without another login.

EzyConn has no CRM, dealer-management, practice-management, EHR, order-management or field-service connector, and it does not sync with Google Calendar, Outlook or Calendly. Availability is worked out from bookings EzyConn made itself. Everything else leaves through Zapier or a webhook.

The product turns on at Starter.

The booking processes, the phone line and custom actions all turn on at Starter. The free plan answers questions; it does not run a process. Every plan has a published seat count and a published message allowance — no plan on this site is described as unlimited.

See what each plan includes

Questions

What automotive businesses ask first.

Will bookings appear in our dealer management system?
No. There is no connector to any dealer management system, and none is declared as coming in the product catalogue. Appointments live in EzyConn and reach your other tools through Zapier or a signed webhook, which someone still has to wire up.
Can it look a car up from the registration?
No. There is no registration lookup and no VIN decode, no parts check, no labour-time lookup and no recall lookup. The car is described by the customer in their own words and stored as text on the job.
Can it quote for a repair?
No. Your price list holds one flat price per job with no variants, so a figure for a specific car would be a guess a customer would hold you to. It books the visit and leaves the price to whoever looks at the car.
How does the mobile side know where the car is?
It asks for the postcode first, before any other question, and checks it against your own list or prefix. If it is outside your area the conversation ends there in your own wording, instead of collecting a name and a number for a job you cannot take.
Can it offer a courtesy car?
No. There is no loaner, courtesy car or vehicle inventory in the product — nothing exists to hold one, reserve one or check whether one is free.
What happens when two of our customers share a name?
The appointment is matched on the name, email and phone number it was booked under. When more than one matches, the process refuses to guess and hands the conversation to a person with that fact recorded — which is also what happens when nothing matches, so that nobody is told they have no booking on the strength of a typo.

Keep reading.

Or read all the processes and everything EzyConn does not do.