Fleet messages fail when they sound like a generic app blast. Riders need the scooter ID, the pickup pin, and a clear next step. You need copy staff can reuse without rewriting every booking.
Want a pack you can paste into greenmoov.app this week?
No manufacturer manual or platform help center publishes a high-confidence e-scooter message library. You still have to confirm rentals, flag battery and parking issues, and chase a quote that went quiet. Treat everything below as draft copy. Swap the placeholders. Drop any line your city, your insurer, or your greenmoov.app setup cannot support.
Pick the channel before you pick the words
A forty-word email is the wrong tool for a scooter sitting two hundred feet away. Push and SMS carry time-sensitive ride events. Email holds the quote, the waiver, and the longer come-back note.
Thing is, hitting all three on every booking trains people to ignore you.
Use this split as a default, then trim it for same-day walk-ups.
| Channel | Use it for | Length and data |
|---|---|---|
| Push (in-app) | Ride start and end, battery, nearby unit, unlock | One or two lines with live fields |
| SMS | Pickup window, same-day confirm, last-minute change | ID, time, location, how to reply |
| Quotes, deposits, waivers, policy, re-engagement | One ask, full details in the body |
Quiet hours still apply to marketing. Don't fire a promo SMS at 10 p.m. because a campaign tool used a leftover default. Critical ride alerts can go through while someone is on a live trip. Promotional follow-ups wait for daytime and a real opt-in.
Limit volume per person. Five marketing texts in a day is already too many for most riders. Transactional trip updates sit in a different bucket, but they shouldn't pile up either.
Ride status copy for in-app pushes
Wire placeholders to real vehicle data first. If [Battery %] isn't coming off the scooter, leave the percentage out. A fake number is worse than a short check-the-app line.
These events match what most e-scooter apps already fire. Keep the tone plain. Don't add safety promises the model docs don't back.
| Event | Sample push |
|---|---|
| Ride start | Your ride on [Scooter ID] has begun. Battery: [Battery %]. |
| Low battery | Battery at [Battery %] on [Scooter ID]. Nearest charger: [Location]. |
| Nearby unit | E-scooter ready at [Location]. Battery: [Battery %]. Unlock in the app. |
| Ride end | Ride complete on [Scooter ID]. Park where the app allows and end the trip. |
| Maintenance hold | [Scooter ID] is due for service. Please return it to [Station]. |
| Unlock | Unlock [Scooter ID] with your code. Report problems in the app. |
Keep battery and maintenance lines factual. "Battery low" is enough. Don't claim a specific remaining range or a hazard in a push unless the model manual states it and someone on your side has approved the wording.
Pickup reminders for reserved scooters
Reserved scooters still get abandoned at the stand. Shops that rent timed gear often send a confirmation at booking, a fuller note about 24 hours out, and a short nudge about two hours before pickup. Skip the 24-hour email when the booking is already today.
Mid-morning works for the day-before note. Aim for 9 a.m. to noon in the pickup time zone so it doesn't land during dinner.
Turns out a lot of "is the red scooter free at 2?" threads start because someone confirmed a unit that was never locked in inventory. Confirm the asset first. Then send the reminder.
Write the day-before note like this: "Reminder: your e-scooter pickup is tomorrow at [Time] at [Location]. Reply YES to confirm." Two hours out, cut it down to "Pickup [Scooter ID] at [Location] in 2 hours. Battery [Battery %]. Questions? Reply." Same-day walk-ups only need "Today at [Time]: scooter ready at [Location]. Scan the QR in the app to start."
If you collect a deposit or a signed waiver, put that in the booking confirmation email, not in the two-hour text. The short ping should still make sense if they never open mail.
Same-day rentals drop the 24-hour note. Don't schedule a tomorrow message that fires after they've already rolled out.
Follow-ups after a quote or a finished ride
Rental inboxes go quiet, and two to four emails is plenty for a quote that didn't convert, because more than that starts to feel like junk even when your intent is helpful and you still have to keep a working unsubscribe on every commercial send. Keep each note to one job.
Day 1 thanks them and puts the number on the table. "Thanks for asking about an e-scooter rental. Quote: [Price] for [Duration]. Reserve with this link." Don't bury the price.
Day 3 only goes out if they haven't booked. "Still need a scooter? The fleet is open [Dates]. Updated quote is attached." Ask one question.
Day 7 is for people who already hold a booking and might change it. "Need a different time or extra coverage on [Scooter ID]? Reply and we'll adjust." Don't jam an upsell into a change window.
Day 14 is for past riders, not a third poke at a cold lead. "If you want another ride, here's [Code] off the next booking." After that, wait. A new opt-in or a real change in hours is a better reason to write again than a calendar reminder you invented.
Skip fluff like "past riders loved our scooters" unless you have reviews you're allowed to quote. A code is cleaner. So is a straight hours update.
U.S. email and text limits that affect this copy
Promotional follow-ups are commercial messages. A ride receipt is usually transactional. The CAN-SPAM Act compliance guide walks through that split, including examples where account details sit at the top and a short pitch sits at the end.
You must honor an email opt-out within 10 business days. Subject lines and from-names can't mislead. False claims about the rental can also run into deceptive-advertising rules under the FTC Act.
SMS is tighter. U.S. marketing texts generally need prior express consent. Autodialed texts to wireless numbers sit under the Telephone Consumer Protection Act, and some states layer extra privacy rules on top. Don't flatten that into one script for every market.
To be honest, the safe pattern is simple. Transactional ride alerts go to people who booked. Marketing sequences go only to people who opted in. SMS needs a visible STOP path. Confirm what greenmoov.app's tools allow, then have counsel look at anything that isn't a booking or trip notice.
The CAN-SPAM Rule is the federal regulation on the email side. It does not replace TCPA or local texting rules.
Leave city helmet, sidewalk, and parking law out of reusable templates. Point riders to an in-app rules screen or a page you update per city.
Wire the placeholders, then set the triggers
Automation only helps if the fields resolve. A send that still shows [Location] is worse than silence.
- Choose channels in your rental software: in-app push, SMS, and email. Give each event one primary channel so you don't triple-tap the same rider.
- Map fields. [Battery %] and [Scooter ID] should read from the vehicle or GPS feed. [Time] and [Location] should read from the booking calendar.
- Set triggers. Ride start, ride end, and battery thresholds fire notifications. A new booking fires confirmation immediately. Timed jobs fire 24 hours and 2 hours before pickup, and they skip the 24-hour job when start time is already today.
- Send to a test rider on a real phone. Confirm every placeholder fills. Confirm opt-out and reply keywords actually work.
- Watch bounces, replies, and no-shows in the dashboard. Open rate alone won't tell you if pickups improved.
Build a fallback. A morning list of bounced or unanswered pickup reminders catches the few the system "handled" that still need a person.
Test two variants on a small group
Nobody has published a proven e-scooter SMS library. Your cities and your rider mix will disagree with copy that worked for someone else.
- Read greenmoov.app help docs for built-in templates before you overwrite them.
- A/B test one change at a time, such as battery-alert wording, on a small group.
- Track replies, no-show rate, and repeat bookings after the copy change.
- Add only operational lines you enforce: deposit due, local parking, helmet check at pickup if you require it.
- Keep battery and maintenance language general unless the model manual supports more.
Refresh quarterly, or sooner after a fleet swap, a new city, or a rule change.
FAQ
What if greenmoov.app already ships templates? Start there. Use these drafts only where a real booking gap shows up.
How should battery or maintenance alerts read? Stay factual. "Battery at 18%" is enough. Don't imply remaining miles, legal parking, or a hazard the scooter's documentation doesn't support.
Will better copy raise utilization? There's no verified public dataset that proves a template lift for e-scooter fleets. Measure no-shows and repeat rides after a two-week test.
Do cities regulate these texts? Many do, on top of federal email and SMS rules. Check local telecom, privacy, and micromobility permit conditions before you add marketing language.
Pick three messages this week: booking confirm, 24-hour reminder, and ride-end. Send them to yourself on a test scooter, fix every placeholder, then turn the triggers on for one location only.