A customer support playbook for bike, e-bike, and scooter rentals is a written set of plays your staff follow when a rider is stuck. It is not a hotel guest binder. It covers the lock that will not open, the battery that dies on a hill, and the bike that left your zone. Those tickets decide the next review.
Who answers when that text lands at 8 a.m. on a Saturday?
If one person runs the counter, the playbook is how they still sound steady. If you have a small fleet, it is how three people stop giving three different answers to the same failure.
What this playbook is actually for
Reactive plays handle the mess that already landed. A jammed lock. A bent derailleur. A rider who cannot get back because the battery packed up.
Proactive plays try to keep that ticket from existing. You confirm charge before the bike leaves. You brief lights, fit, and where they may ride. You notice a GPS ping that has not moved in 40 minutes and check in before they start walking.
Thing is, most shops already do fragments of this from memory. Memory fails when six people are waiting and the phone is ringing.
Write the play so a closer at 4 p.m. does what the opener did at 9. Keep the outcome concrete. Acknowledge a lockout fast. Say whether you are sending a spare, a mechanic, or a refund clock. Log the asset ID so the next shift is not guessing.
Rider touchpoints that need a play
The ride is short. Most of the pain sits in a few hours, not a week-long stay.
| Touchpoint | What the rider needs | Support play |
|---|---|---|
| Booking questions | Hours, deposits, helmets, real e-bike range | Honest reply on what the bike can and cannot do |
| Pickup briefing | Fit, locks, lights, local rules, charge level | A briefing nobody is allowed to skip |
| Mid-rental contact | Lock failure, flat, low battery, lost | Field play plus a spare or pickup plan |
| Late or missing return | The next rider is waiting | Escalation clock, GPS check, terms already signed |
| Return and inspection | Scratches, missing charger, wet ports | Same inspection every time, photos if needed |
| After the ride | Damage dispute, leftover charge, a rebook | Short follow-up, not a campaign |
A rental operations checklist for bike, e-bike, and scooter fleets already covers ID checks, brakes, lights, and explaining local speed rules at pickup. The support playbook sits on top of that. It tells staff what to say when those checks were not enough.
Build it in five passes
- List the tickets you already get. Pull a month of texts, inbox threads, and counter notes. Rank them by how often they happen and by how badly they wreck the next booking. Lockouts, flats, low batteries, and late groups usually sit at the top.
- Name the outcome for each one. "Rider rolling again in 30 minutes" beats "be helpful." "Protect the 2 p.m. booking" is a real outcome when someone is late.
- Write steps a new hire can follow. Who they message. Which spare they pull. When they call a mechanic versus when they extend time or refund. What they log against the bike.
- Assign an owner and a backup. Weekday opener. Weekend closer. After-hours phone. If nobody owns it, the play is a wish.
- Run it on a real shift. Pick one busy day. Do not rewrite the whole binder after one weird ticket. Change a play only when the same failure repeats.
A shared doc plus your booking tool is enough to start. Perfect software can wait.
Write these plays first
Turns out the first Saturday you feel ready is often the day that writes the playbook for you. An operator guide from Equipdash sketches that morning in a way any shop will recognize: three flat tires, a bent derailleur, an e-bike sitting at 12% charge, a rider who swears the saddle height was fine, and a hotel calling about eight people in twenty minutes, which is a lot to hold in your head while the cabinet is still locked and the first waiver is not even signed.
You do not need that exact day. You need a play for each piece of it.
Lock will not open. Staff confirm the booking and the bike ID, walk through the app or keypad steps once, then go to the bike or send a nearby spare. They do not argue about whose phone is at fault in the first message.
Battery died mid-ride. Ask where they are, whether they can still pedal, and how much assist is left. Range and charge should have been part of pickup. Still, write a swap or pickup rule. Charging advice has to match that model and battery chemistry. Do not send anyone to a random cafe charger.
Flat or other mechanical. Decide in advance which issues you fix in the field and which mean a swap. Carry a pump and tubes if that is how your shop works. If you do not do roadside service, say so in the booking reply so nobody invents a rescue under stress.
Rider is late and the next booking is on the dock. Check GPS first. Then a timed sequence: message, call, wait window, then put a different bike on the next reservation if you have one. Charge a late fee only if it was in the terms they already accepted.
Suspected theft or a geofence exit. Freeze the remaining ride if your system can. Record the last ping. Contact the rider. Involve police only under the policy you already wrote, not as a panic move on the sidewalk.
Injury. The play is get them help if they are hurt, keep the bike from becoming a second hazard, and document what you see. You are not their doctor. Helmet, path, and speed rules still belong in the briefing so you are not explaining them after a crash.
One person cannot run the counter and do a roadside rescue at the same time. Put that limit in the play so the closer is not guilted into leaving the shop empty.
Tools that actually carry the plays
A playbook that lives in a drawer fails. The booking tool, the inbox, and the lock or GPS have to show the same bike ID.
Connected e-bike fleets often run a rider app with QR unlock, in-app payments, live GPS, and geofences for no-ride or slow zones. Levy's e-bike rental playbook treats that stack as a baseline for a connected fleet. A walk-up shop with keyed locks can still run plays. You just replace "ping the GPS" with "check the slip and call the number on the waiver."
What you want from software is boring and specific. One thread per rider, not texts plus Instagram plus a sticky note. Asset status that flips when a bike is down. A way to block the next booking when a return is late.
Bike rental management writeups talk about cutting double-bookings and desk time when calendars and payments sit in one system. Treat vendor percentages as marketing unless you measure your own shop. The useful idea is simpler. If two people can rent the same e-bike at 2 p.m., your support plays start from a hole you already dug.
Self-built docs work for a single counter. They break when you add a second location or after-hours staff. Night coverage only works if the person answering can see bike status and has the same plays. Otherwise they read a script that does not match your dock.
Unstaffed hours need a live person who can unlock, disable, or send help. An inbox that opens at 9 a.m. is not a lockout play.
When riders ask about batteries and fire risk
E-bike and scooter tickets are not the same as a dead phone. Lithium-ion packs fail in ways that scare people, and they have reason to ask.
The U.S. CPSC has pushed work on lithium-ion fires in e-bikes and similar products, and a proposed safety standard for micromobility batteries has been on the federal docket. That is product regulation, not your rental script. It still belongs in staff training so nobody shrugs off a swollen pack or a charger that does not match the bike.
To be honest, the support play here is mostly what you refuse to do. Do not send riders to a gas-station charger. Do not green-light an aftermarket pack because it "fits." Do not park a damaged battery in the waiting area. Follow the manufacturer's charge and storage steps for that model. Those steps change with chemistry and pack design, so paste the model note into the play instead of a generic charge-overnight line.
If a rider reports heat, smoke, or a pack that will not sit flat in the tray, stop using it. Get people away from it. Treat it as a fire problem, not a swap-and-keep-the-clock-running problem.
Shop charging should use the supplied charger, on a hard surface, where staff can see it. Riders who take an e-bike overnight need that same instruction in writing. Where they may ride, and at what assist speed, is local. A UK hire briefing that cites a 25 kph electrical assist cap does not belong on a U.S. waterfront dock unless that is actually the rule in front of you. Path, sidewalk, and helmet rules change by city and sometimes by park. State the rule for your location. Do not mash several cities into one speech.
Pull last month's inbox. Pick the three ticket types you answered most. Write one play for each before the next weekend, and tape the lockout play next to the spare-key hook.
