Salon, spa and fitness booking platforms are different from field service software in one important way: they usually already send appointment reminders themselves, over SMS or email, as part of the product. That changes what you should build.
Do not duplicate the reminder
Two reminders is worse than one
If the platform already sends an SMS reminder and you add an iMessage reminder, the customer gets both and neither feels considered. Either switch the platform's reminder off and own it, or leave it alone and spend your effort on messages the platform cannot send. Deciding this before you build is the whole point.
What these platforms cannot do
| Message | Why the platform will not send it |
|---|---|
| Rebooking at each client's own interval | Needs their history, and a judgement about cadence |
| Waitlist fill for a same-day cancellation | Needs a fast, conversational back-and-forth |
| Aftercare for a specific treatment | Service-specific content the platform does not hold |
| Win-back after a lapse | Requires deciding what "lapsed" means for each service |
| A real conversation | Platform messaging is usually one-way notification |
The waitlist fill is the highest-value one and the best fit for iMessage specifically. A same-day cancellation is perishable inventory, and filling it needs a short exchange — offer, reply, confirm — which is exactly what a conversational channel is for. The same mechanic as a restaurant cancellation.
Integration routes
- Mindbody publishes a public API through a developer programme. If you are on Mindbody and have someone who can build, this is the fullest route.
- Booksy and Vagaro have historically been more closed. Check what your plan actually includes before designing around an API — availability varies by tier, and the answer changes.
- Middleware where a connector exists, which is the pragmatic route for most single-location businesses.
- Export and import as a floor: even a weekly CSV of clients and last-visit dates is enough to run a rebooking play manually. Unglamorous, and it works.
Verify API access on your actual plan
In this category API access is frequently a higher-tier or partner-programme feature rather than something every subscriber gets. Confirm it against your own account before you scope a build — it is the assumption that most often derails these projects.
The rebooking interval is the product
Every one of these businesses has a natural cadence — four weeks for a cut, six for colour, eight for a treatment — and it varies per client. A message timed to *their* interval, referencing what they actually had, is the single most effective thing you can send. It is also the message that requires their history, which is why the platform's built-in tooling rarely does it well.
Before building
- Confirm API access on your actual plan, in writing.
- Decide who owns the reminder — the platform or you. Not both.
- Start with the waitlist fill or the rebooking nudge, not the reminder.
- Consent captured at booking, separately from the platform's own terms.
- Measure rebooking rate against the pre-launch baseline, not against a vanity metric.