Aller au contenu
← Retour au blog
16 novembre 2026 capacity planningworkshop managementAI receptionist

Workshop capacity planning in week one with an AI receptionist

Turned on an AI receptionist and the phones stopped being missed? Here’s how to stop the diary bursting in week one: guardrails, triage, buffers and overflow.

Switching on an AI receptionist that answers every call and books straight into the diary (Garage Hive, Tyresoft, etc.) feels brilliant until the ramp lights stay green and the diary goes red. Week one is where most garages either bank the upside or burn the team. Here’s a practical plan to turn the booking surge into revenue without wrecking capacity.

What changes when every call is answered

An AI receptionist for UK garages answers every call, captures the booking details, and pushes it into your diary against the right slot type. The big shift in week one is simple: latent demand lands. Missed calls, out‑of‑hours voicemails, tyre price shoppers and “tried you last week” all convert. Expect two things:

  • Bookings lift fast. Typically 20–35% more jobs try to land in the first 3–7 days.
  • Job mix skews short. More MOTs, tyres and inspections surface than complex repairs.

The risk isn’t too much demand. It’s the diary accepting it in the wrong places. Capacity planning in week one is about guardrails, triage and buffers.

Before switch‑on: set guardrails in the diary

Don’t let day one be the first time the diary rules are tested. In the DMS, set simple, hard limits that protect the workshop:

  • Cap the big hitters per day:
    • Diagnostics: max 2 per technician per day. Book a 60–90 minute assessment first, not “full fix”.
    • Clutch/gearbox/suspension overhauls: 1 major per bay per day.
  • Protect a rolling buffer: keep 15–20% of each day unbookable to the AI. Use these for overruns, walk‑ins and VIPs. Release them manually the day before if unused.
  • Default durations that reflect reality:
    • Interim/Basic service: 60–90 minutes depending on vehicle age.
    • Full/Major service: 120–180 minutes.
    • MOT: 45 minutes for a single lane with admin. Set retests at 20–30 minutes.
    • Puncture repairs: 30 minutes. Tyre swaps: 20–30 minutes per wheel with balancing.
  • Gate courtesy cars and collection/delivery:
    • Tie courtesy cars to specific slot types and cap by keys available, not by hope.
    • If collection is offered, add 20–40 minutes travel time into the booking.
  • Parts‑led gating:
    • Any job likely to need parts with a lead time greater than same‑day should be booked as assessment first. Switch the AI booking script to “inspection/estimate” for timing belts, EML faults, DPF issues, major brakes on prestige models.
  • Skill and bay rules:
    • Map jobs to technicians and bays (e.g., EV high‑voltage to EV‑qualified techs; 2‑post ramp for exhausts, 4‑post for wheel alignment). The AI can only book where a compatible resource exists.

If you run two MOT lanes that can theoretically do 16 MOTs per day, cap the first week at 12. The extra four become shock absorbers for fails and late arrivals.

Days 1–2: throttle and triage the surge

The first 48 hours are the spike. Aim to shape it, not stop it.

  • Hold back mornings: in week one, allow the AI to book no more than 60–70% of morning capacity. Keep the rest for overruns and walk‑ins. Let afternoons carry more volume.
  • Make “assessment first” your default for unknown faults:
    • 30–60 minute paid inspection slots. Clear description: “Investigate and estimate.” This avoids a three‑hour hole being taken by guesswork.
  • Split tyres into quick vs tricky:
    • Standard sizes and steels/alloys under 18”: normal durations.
    • Run‑flats, TPMS reseats, 19”+: add 10–15 minutes per wheel automatically.
  • Set a same‑day ceiling:
    • Allow a maximum of 2–3 same‑day bookings per technician. Everything else starts from next day. This prevents the AI from “being helpful” at the team’s expense.
  • Midday diary sweep (10 minutes):
    • Service manager skims the board at 11:30 and 15:30. Pull obvious clashes, convert questionable “repairs” into assessments, and rebalance between bays.

Train one person to own these tweaks. A daily 10‑minute huddle is cheaper than overtime.

Days 3–5: smooth the load and protect technicians

Once the initial rush is captured, improve flow and prevent burnout.

  • Batch similar work:
    • Group MOTs back‑to‑back on the same lane.
    • Cluster tyre work to minimise machine changeovers.
    • Line up services to align with a tech’s strengths.
  • Push non‑urgent into next week with a fair script:
    • “Earliest assessment is Thursday. If you’re happy with next Tuesday, we’ll aim for same‑day turnaround.” Many customers will trade wait time for certainty.
  • Use the buffer intentionally:
    • Overrun from the morning gets first dibs. Then warranty comebacks. Only then new work.
  • Keep an eye on technician utilisation:
    • Aim for 80–85% booked hours per tech in week one. Below 75% leaves money on the table; above 90% causes late nights.
  • Courtesy car reality check:
    • If cars are the choke point, tie them to longer jobs only. Short jobs get collection/drop‑off or waiting areas instead.
  • Manage retests:
    • Reserve 2–3 late‑afternoon retest slots per lane. If unused by 14:00, release them to the AI for quick wins.

If overtime is on the table, choose Saturday mornings for bolt‑on work (tyres, simple services) and keep weekdays focused on diagnostics and planned repairs.

Overflow demand: capture it without breaking the team

Not every caller needs this week. The job is to keep them, not cram them.

  • Use a waitlist with rules:
    • Priority order: safety‑critical (brakes/tyres with cords), no‑start vehicles, key workers/fleet, then convenience jobs.
    • Review at 16:00 when no‑shows and cancellations reveal gaps.
  • Confirm and remind:
    • Same‑day bookings: SMS confirmation plus a 2‑hour reminder.
    • Next‑day+ bookings: confirmation on booking and a day‑before reminder. This lifts show rates and frees slots earlier when people cancel.
  • Take deposits where no‑shows hurt:
    • High‑demand slots (first thing Monday, last thing Friday) or major jobs. Even £20–£30 reduces flakiness.
  • Offer call‑backs for quotes:
    • If parts pricing will delay a booking, park it into a “quote follow‑up” list with a target time (e.g., 2pm same day). Don’t let the AI guess on parts.

If you partner with mobile fitters or machine shops, pre‑agree overflow rules in week one so work can be offloaded cleanly without surprises.

After the first week: lock in permanent rules

Use what the diary just taught you.

  • Update durations based on actuals:
    • If 1.5‑hour services ran to 2 hours on 2015+ SUVs, change the template. Don’t wish it smaller.
  • Tune caps and buffers:
    • If diagnostics overflowed, reduce daily cap by one and increase assessment slots by two.
    • Keep a permanent 10–15% rolling buffer. It pays for itself in on‑time handovers.
  • Track three simple metrics weekly:
    • Show rate by job type.
    • Average overrun minutes by job type.
    • Rebook rate from assessments to paid repairs.
  • Align parts and courtesy capacity:
    • If parts are the real bottleneck, move more unknown faults to morning assessments so orders can land same day.
  • Refresh the AI booking rules:
    • Tighten scripts where the AI over‑promised (e.g., EV brake jobs, seized fasteners on older cars).
    • Loosen where you left money on the table (e.g., more MOTs if retests were smooth).

Handled well, the week‑one deluge becomes a clearer, calmer diary, higher billed hours, and fewer end‑of‑day scrambles.

Looking to see how an AI receptionist built for UK garages manages bookings and protects capacity in real shops? Have a look at the case studies at /case-studies or start a trial at /get-started.

Découvrez ReceptionMate gérer vos appels

Réceptionniste IA conçue pour les garages — réservations directement dans votre agenda, 24h/24 et 7j/7, sans engagement.

Commencer