Bike and motorbike workshops: parts on order and collections

It's eleven on a Saturday morning in April. You've got three bikes on the stands, a motorbike with its fairing half off, and your phone buzzing in your apron pocket. Two of the messages ask the same thing: "has the part come in yet?" The third is from someone who left a road bike with you in November and still hasn't picked it up. If you run a bike shop with a workshop, or a motorbike garage, this article is about one specific job: getting parts-on-order updates and collection reminders off your hands, because those two conversations eat more of your week than almost anything else, and neither of them fixes a single bike.

Why a two-wheel workshop isn't just any workshop

A lot of it looks like a car garage, but three differences change how you should handle customer updates.

The first is how much you depend on distributors. A derailleur, a shock, brake pads for a particular brand, a fork seal for a less common motorbike: you rarely have it on the shelf. You order it, and the date the distributor gives you is an estimate that moves. That turns every repair into a small wait with an uncertain end.

The second is seasonality. The moment the weather turns, everyone pulls their bike or motorbike out of storage at once and wants a service before next weekend. In winter, on the other hand, you get motorbikes coming in to be stored and bikes left "for whenever you get round to it".

The third is attachment. Someone dropping off a road bike or a motorbike tends to ask more often than someone dropping off a family hatchback. It isn't distrust. For a lot of people it's their weekend, and they want to know when they're getting it back.

"Waiting for parts": the status that triggers the most messages

If you logged for one week why customers message you, "has the part arrived?" would almost certainly be at the top. The reason is simple: the customer has heard nothing since the day they dropped the bike off, so they ask.

The fix isn't answering faster. It's updating them before they need to ask. An AI agent needs very little to do that: when you order a part, note the order, the supplier and the estimated date in your sheet or workshop software. With that, it can send three messages.

1. On the day you order, with an honest range rather than a firm date: "We've ordered the derailleur for your bike. The supplier says 5 to 8 days; we'll message you as soon as it's in."
2. When the date changes, which is exactly when people get annoyed if they find out on their own: "The supplier has pushed the delivery back. The new estimate is next week. If you'd rather we look for an alternative, just let us know."
3. When the part arrives, with when it'll be fitted, if you already know.

Look at that second message: it offers an alternative but doesn't choose one. If there's a compatible component from another brand or range, whether to suggest it, and at what price, is your call. The agent just finds out whether the customer is open to it and passes it to you.

One practical point: don't ask the agent to check the distributor's stock itself unless you have a reliable connection to their system. It's better working from the date you noted down, even a rough one, than from one it makes up.

Collection reminders, and the bike that never leaves

The other big gap is at the end. You finish the job, ring once, they don't pick up, and the bike hangs from the ceiling for weeks taking up space you badly need in high season.

A simple sequence beats a one-off phone call:

• The day it's ready: a message with collection hours and the amount due, so nobody gets a surprise at the counter.
• Three or four days later: a friendly reminder, no telling-off.
• At two weeks: a firmer message that restates the terms on your drop-off ticket, if you have any.
• After that: it comes to you, because it's no longer a reminder, it's a conversation.

A word of caution on that third message: the agent should only repeat terms you've already put in writing when you took the bike or motorbike in (a storage charge after a certain period, for example). If your ticket says nothing like that today, the agent mustn't invent it. If you want to add a term like that, check it with your accountant or adviser first, because it needs to be clear from the start.

For motorbike garages that store bikes over winter, the same logic works in reverse: a message in March to everyone with a bike in storage, offering a service slot before they take it out, fills your spring calendar early instead of at the last minute.

Spring, when everything jams at once

In high season the problem isn't sending updates. It's not overpromising. If every customer who writes "can you have it ready by Saturday?" gets an automatic yes, by Friday you've got an impossible queue and a lot of disappointed people.

An agent helps here if you give it a clear rule and update it every week: how many services fit, what the real turnaround is right now, and which jobs you'll take in a hurry (a puncture or a gear adjustment, yes; a fork service, no). With that, it can offer real drop-off slots, state the current turnaround without dressing it up, and put anyone who can't fit this week on a waiting list.

It's boring, repetitive work, and that's exactly why it's where you win back the most hours: dozens of short, similar conversations that you currently answer between jobs.

What not to hand over

Some parts of the trade don't get delegated, and on two wheels a few of them are about safety.

• Remote diagnosis. "It makes a noise when I brake, is it serious?" isn't answered over WhatsApp. The agent takes the description, asks for a photo if that helps and offers a slot; the diagnosis is yours.
• Any question about whether it's safe to ride. Brakes, steering, forks, tyres: if someone asks whether they can ride it like that, a person answers. Always.
• E-bike batteries and motors. Warranty claims and diagnostics usually go through the brand, with its own timelines and criteria. The agent can explain that the claim is being handled with the manufacturer and pass on the status updates you give it, but it shouldn't promise anything about the warranty.
• Part prices you haven't confirmed. Distributor prices change. If a price isn't in a quote you've approved, the agent doesn't give it.

And a broader caveat: if your workshop is small and five people message you a week, you probably don't need an agent. A well-written set of message templates and ten minutes at the end of the day will do. Automation starts to pay off when parts on order and collection reminders run into dozens a week.

Where to start

Start with "waiting for parts", because it generates the most messages and carries the least risk. For two weeks, keep a column with the estimated date of every order and let the agent send updates when you order, when the date moves and when the part arrives. Count how often people ask "has it come in yet?" before and after. If that number drops, add the collection sequence.

If that sounds useful, it's exactly what our operations agent does: it keeps customers posted on every repair, sends the collection reminders and passes you anything that needs your judgement. You approve, it executes.