Browse the docs

Keep people coming back

Reminders go out before every session someone’s booked into, and a short welcome after their first visit. We can also invite people back when it’s time to book again or after a month away.

Booking reminders go before each session, so someone in a six-week course hears about every class, not only the first. Pick how many hours before. If a session moves, the reminder follows the new time.

The welcome goes after someone’s first visit: up to four short notes over the next days, and it stops once they buy a pack or membership. It goes only to people who came for the first time, and only once.

Rebooking reminders ask people to book again a set time after a visit, like 4 weeks for a haircut. Win-back invites back anyone who hasn’t come in a while, 30 days unless you change it. Both skip anyone who’s already been back or has something booked.

Messages go to whoever booked, so a parent hears about their child’s class. The welcome, rebooking and win-back notes are news and offers: they go only to people who agreed to hear from you. Reminders are about a booking, so everyone booked gets them.

Every booking sends one confirmation on its own, with the time, the place, the price and how it’s paid, and a link to its page to move or cancel it. A paid booking sends no separate order email. When a booking is cancelled, by them or by you, they get an email that says what comes back. That isn’t an automation, so it can’t be turned off. Your business’s kind turns on the right reminders and follow-ups when you start. Change or turn them off in Automations.

For agents

Turn one on with playbook.enable and its playbookId and params: playbookId: "offerings.reminder" (hoursBefore, 1 to 72; before every session a place is expected at), playbookId: "offerings.welcome" (days, up to four, the notes’ days after the first visit), playbookId: "offerings.rebook" (days after a visit) and playbookId: "offerings.win-back" (days away, default 30). Each message goes to the buyer. Rules can ask about visits: { visited: { offeringId?, kind?, since?: { days } }, gte? } and { daysSinceVisit: {}, gte: 30 }.