Playbook, bike shop
Stop riding it: the handover that begins with an instruction
Every other handover in retail collects details and moves on. This one has a job to do first, because the person typing is frequently about to get on the bike. A soft lever, a noise from a headset and a mark near a weld arrive in the same casual sentence, and nothing in the words distinguishes the trivial one from the one that ends badly on a descent.
Why this is not the general answer
The handling pattern for asking for a person holds across every trade. What follows is the part that does not.
- This is the only retail handover where the reply's first job is to change what somebody does in the next hour rather than to collect their details.
- A typed description cannot separate a harmless noise from a component about to fail, and both arrive in exactly the same words.
- The rider is often about to set off, so a reply that reads like a routine ticket loses the one chance to stop them.
- Advice about a brake, a fork, a steerer or a frame given in the shop's name is the shop's advice, and there is no version of it worth being wrong about.
How it arrives
- my brakes are making a noise
- there is a crack in my frame
- the bars moved when i braked
- my brake lever pulls to the bar
- the front wheel has developed a wobble
- is it safe to ride like this
What has to be indexed for this to work
| The safety wording, written to be returned whole | The stop riding instruction and the workshop route in one piece, so it comes back intact rather than assembled around a maintenance article. This is the wording to write first and change least. |
|---|---|
| How urgently the workshop can look | Whether you take a safety check as a drop in, whether there is a same day look for anything structural, and what a rider should do if they cannot get to you. A rider told to stop riding needs somewhere to go. |
| What the workshop wants to know | What the bike is doing, when it started, whether anything was recently fitted or adjusted, and a photograph of the area. Enough to triage, not enough to diagnose remotely. |
| The difference between a look and a booked job | That a safety check is not the same as a service slot, so a rider does not assume they have to wait three weeks for somebody to glance at a brake. |
The reply
Please do not ride it until somebody has looked at it. A lever that pulls to the bar can be air in the system or it can be a pad or a hose problem, and nothing in a description tells those apart, so I am not going to guess about a brake. Bring it in and the workshop will look at it, and if you cannot get here today, leave your name, email and what it is doing and they will call you.
The instruction comes first and without conditions, because everything else in the reply is wasted if the rider sets off. Naming two possible causes without choosing between them shows the question was understood rather than dodged, which is what stops a rider deciding the reply was useless and riding anyway. The in person route is offered ahead of the form, because a brake belongs in a workshop rather than in an inbox.
Where it stops
The trigger. Any mention of brakes, steering, a fork, a frame, a wheel that has moved, or a noise the rider cannot place.
Do not ride it until it has been looked at. Bring it to the workshop, or leave your name, email and what the bike is doing and somebody will get back to you today.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never say a described noise or fault is probably nothing.
- Never talk a rider through a repair to brakes, forks, steering or a frame.
- Never suggest riding carefully, or riding to the shop, on a bike described as unsafe.
- Never estimate how long a component will last before it fails.
Questions
- Is telling people to stop riding not alarmist?
- It is the only instruction that is right for both outcomes. If the noise is a dry pivot the rider loses a day. If it is a fork steerer the instruction is the whole point. There is no wording that hedges between those two without being useless for one of them.
- Why offer the workshop before the form?
- Because the form ends in an email and the problem is mechanical. A rider ten minutes away should be told to bring the bike. The form is for the person who cannot get there today and needs somebody to ring them instead.
- How do we stop it reaching for a maintenance article?
- Keep indexed maintenance material descriptive rather than diagnostic, and set the caution level so a weak match refuses instead of retrieving the nearest thing. A brake bleeding guide is the worst possible document to surface in this conversation.
Keep reading
- Everything for a bike shopFrame sizing, service turnaround and whether a part fits are the daily questions. Safety critical repair advice is an escalation.
- Handling asking for a person in generalThe design question at the centre of a support assistant. Offer early, offer once, collect what a reply needs, promise a time you can keep.
- Stock in a bike shop is a grid, and size is the axis that mattersHaving the bike is not having it in the size that fits. Floor stock, allocation from the brand, and why a restock is a season not a date.
- The shop can quote a named job and not the repair it turns intoBike tickets and a workshop labour menu are both quotable exactly. A repair is not, until the bike is on a stand and stripped.
- What an estimate can honestly bound on a machine still assembledThe deciding facts sit behind parts that have to come off first. What an estimate can bound, the inspection charge, the uneconomic repair.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.