Booking
BetaLet the client’s customers book themselves.
A booking page in the client’s brand, on their own portal address. Customers pick a time in four steps at most, in their own time zone, with no account to make.
Each booking lands in the client’s CRM and can start a workflow, so the confirmation, the reminder and the follow-up take care of themselves.
Thrum opens soon. Sign up now and you’ll be among the first in.
Services and staff
Only real free times are offered.
Set each service’s length, the gap before and after, notice, how far ahead it can be booked and how many a day. Give each staff member their hours and days off.
The times offered respect all of it, through the clock changes too, and one staff member can never be double-booked.
After they book
Confirmed at once, reminded twice.
The confirmation offers a calendar invite and Google Calendar and Outlook links. A reminder goes by email the day before and by text two hours before, and no text arrives in the middle of the night.
A private link lets the customer move or cancel, up to a window you set.
Inside a form
Book the visit as part of the enquiry.
Add a booking question to any form and the time is booked when the form is sent. If the answers fail to save, the booking is undone, so nobody holds a slot for an enquiry that never arrived.
The client’s team
The client runs their own diary from their phone.
The client sees today’s, upcoming and past bookings in their portal. Their managers can add a booking taken by phone, move or cancel one, and mark who turned up.
Specs
Booking details
- Service length
- 5 minutes to 24 hours
- Group size
- 1 to 500
- Reminders, by default
- Email 24 hours before, text 2 hours before
- Quiet hours for texts
- 21:00 to 08:00
- Change window, by default
- 24 hours
- Calendar links
- Calendar invite, Google Calendar and Outlook
- Connected calendars per staff memberOnly start and end times are kept
- 3, read every 15 minutes
Questions about booking
Does it know when my client is already busy?
Each staff member can connect up to three calendars by their private iCal address. They are read every 15 minutes, and busy times there are never offered. Only the start and end of each event are kept.
Can the booking page go on my client’s website?
Yes. It lives on the client’s portal address, and one script tag puts it on any site.
Do customers need an account?
No. They pick a service and a time, give their details, and get a confirmation with a private link to move or cancel.
Can a booking start a workflow?
Yes. A booking being made, moved, cancelled, missed or over can each start a workflow, such as a review request after the visit.
What does Beta mean?
Beta means the module is built and tested, and hasn’t yet run against the live service it depends on, such as Stripe or Twilio. The tag comes off once it has.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.