Tandem pairs book one bike and then argue, politely, about helmets, height, who sits in front, and whether you even have a second helmet that fits. A thin confirmation almost always produces another text.
Why not answer those questions in the first send?
Quote the greenmoov.app record, not a sticky note. If the dashboard and the SMS disagree, the morning disappears into availability calls.
Log the booking before you confirm it
Availability questions pile up when walk-ins, phone holds, and app checkouts live in different places. Type the reservation into greenmoov.app first. Then send the message.
That sequence is dull. It also stops two staffers from promising the same tandem.
Turns out most "is the red tandem free at 2?" threads start because someone confirmed a bike that was never locked in inventory. Don't send a booking ID the dashboard cannot find.
Walk-in customers who pay at the counter still need that log, even if they are standing three feet from you and you feel silly tapping details you just heard, because the next person on shift will not have heard any of it.
- Enter rider name, party size, pickup window, return time, and tandem ID in greenmoov.app.
- Recheck the calendar so the slot is still open.
- Copy the booking ID into the template.
- Send one confirmation. Skip a second send unless the time, bike, or price actually changed.
If they want a text receipt, send it after the record exists. Not before.
What the first confirmation has to carry
Rental CRMs keep repeating the same fields because customers actually use them at the desk, in the parking lot, and when they forward the note to the second rider. Keep the SMS short.
Pipedrive's confirmation advice is generic sales copy, not a tandem manual. The fields still hold: booking ID, pickup and return times, what was reserved, a price summary, and a working contact number.
Park longer tandem notes in email. You'll get fewer repeat questions if the second rider can read that email without calling.
Vendor posts love giant SMS open rates. TextBolt claims a 98% open rate for reservation texts, with 95% opened inside three minutes, and a 209% higher response rate than phone, email, or social combined. Treat that as one company's marketing, not a local guarantee. Test your own list.
Sample SMS:
Booking [ID] confirmed.
Tandem: [model]
Pickup: [date] [time] at [location]
Return: [date] [time]
Total: [price]
2 riders. Helmets per shop policy.
Questions: [phone]
Reply STOP to opt out.Sample email you can paste into greenmoov.app:
Subject: Tandem booking [ID] - [pickup date]
Hi [first name],
Your tandem is reserved.
Bike: [model / color]
Pickup: [date, time, location]
Return: [date, time]
Riders: 2 (captain in front, stoker in back)
Total: [amount] ([deposit / tax / helmet fee if charged])
Bring closed-toe shoes. We set saddle height at pickup.
Practice starts in the lot, not in traffic.
Reply to this email or call [phone] if the time or rider count changes.
Give booking ID [ID] at the desk.Verify every bracket against the dashboard before anything goes out. A wrong return time is worse than silence.
People will still call. They always call about something, usually parking or whether a third cousin can hop on, and the template will not retire your phone. It just stops the obvious answers from arriving as five separate threads.
Write tandem caveats from the manual, not from memory
No manufacturer publishes a rental SMS pack. You still owe riders the limits in the owner's paperwork.
A Cannondale tandem owner's supplement talks about the captain (front) and the stoker (rear), plus stem and seatpost hardware that customers should not wrench on in the lot. Other brands use the same two-rider layout with different torque figures and weight caps. Copy the numbers from the model you actually rent. Don't invent a universal weight limit.
Helmet rules are local. Some cities require them. Some don't. State the shop policy in the message, then add any city or state rule that applies to your pickup spot.
To be honest, a flat-area start line prevents more scraped knees than a clever subject line. Useful copy, after you check the manual and the law:
Tandem notes: two riders only. Captain steers from the front. Stoker matches cadence from the rear. We set saddle height at pickup. Don't adjust clamps yourself.
If a child is booked on the back, stop the auto-confirm. Check that the model is rated for that rider, the stoker reach is safe, and your waiver covers it. A template can't fix an unfit bike.
Time the sequence so people actually read it
One dump of instructions at booking gets ignored. Split it.
EquipDash's booking-confirmation timing uses confirmation at booking, a fuller reminder about 24 hours before start, and a short nudge about two hours out. Same-day rentals drop the 24-hour note. Email open rates there are described as often sitting around 20-30%, with spam risk, which is why the long copy stays in email and the last ping is SMS.
| When | Channel | What it should say |
|---|---|---|
| Right after the dashboard save | SMS plus email | ID, times, location, total, 2-rider cap, opt-out |
| 24 hours before pickup | Parking, helmet policy, captain/stoker setup, what to bring | |
| About 2 hours before | SMS | Still on for [time] at [place]. Bring IDs. Reply if late. |
| After return | Email, only if they opted in | Thanks, damage-check note, optional review ask |
Late returns need a written grace window, not a surprise fee in a cheerful text. Put that window in the 24-hour email so the desk is not inventing policy at 6 p.m.
It's easy to over-message same-day walk-ins. Skip the 24-hour email when pickup is already today.
Consent is not optional on automated texts
Thing is, a booked tandem is not a license to keep texting after someone opts out.
US operators sending automated SMS should collect prior express consent before the sequence starts. The FCC robotext consent rules also cover revocation: if a rider texts STOP, halt marketing and non-essential pings. A single confirmation of that opt-out is typically allowed. Transactional notes about an active rental can sit in a narrower bucket, but you should still keep a consent record and a way out.
Other countries use different tests. If you rent across borders, you can't reuse the US script and assume it travels.
Store the consent flag on the greenmoov.app customer record. A new staffer won't then re-enroll someone who already left.
Load the templates and run a dry booking
Automation only helps if merge fields match live inventory. Wrong bike names train people to ignore you.
- Attach the SMS template to new tandem bookings in notification settings.
- Attach the longer email to the same trigger, plus the 24-hour reminder.
- Place a sample booking from the app, then one by phone, then a walk-in.
- Confirm each message quotes the real ID, times, and model.
- Change a pickup time and check that the update fires once.
- Put waiver, insurance, and helmet lines in the email, not as a counter surprise.
- Read the week's message log. Duplicate texts mean a trigger is firing twice.
Staff still need a human path. The customer support playbook for rentals puts it plainly: anyone on shift should be able to say who is riding, which bike it is, where the problem is, and who owns the next action. Templates don't replace that.
FAQ
Do tandem messages need different copy than single bikes?
Yes. Capacity, captain/stoker roles, and a "don't wrench the clamps" line do not apply to a solo city bike. Pull model limits from the owner's manual.
What if someone books two adults and a child?
Don't auto-confirm a two-seat tandem for three people. Reply with the model limit and offer a second bike or another time.
Can I treat vendor SMS open rates as local fact?
No. Run a small test on your own list before you drop email.
How do I avoid double-messaging walk-ins?
Log the sale in greenmoov.app first. Send the confirmation only if they want it, and only once.
Pick one tandem model you actually rent, copy its rider limit from the manual into the email template, then run five live bookings and fix whatever the desk still has to explain out loud.