An AI assistant can read booking requests, check your calendar, propose suitable times, and draft the reply for your approval. Once a booking is confirmed, it can add the event and send reminders you have approved.
Back-and-forth scheduling is one of the most common time drains in a small business. "Does Tuesday work?" "Only after three." "How about Thursday?" Each exchange is small; together they eat hours. An assistant handles the logistics and leaves the yes to you.
How does it handle a new booking request?
- It recognizes the message as a booking request.
- It checks the calendar for open times that fit your rules, such as working hours, buffer time between appointments, and travel time.
- It drafts a reply offering two or three options.
- You approve, edit, or discard the draft.
- When the client confirms, it proposes the calendar event for your approval or adds it if you have allowed that.
What rules should it follow?
Write your booking rules down once:
| Rule | Example |
|---|---|
| Hours | Weekdays 9 to 5, Saturdays by request |
| Length | Consultations 30 minutes, sessions 60 |
| Buffer | 15 minutes between appointments |
| Travel | 45 minutes between on-site visits |
| Lead time | No same-day bookings |
| Limits | No more than four sessions a day |
The assistant uses these to propose times; you can always override.
What about rescheduling and cancellations?
It treats them the same way: find the original booking, check alternatives, and draft a reply. If you have a cancellation policy, it can mention it in the draft using your exact wording. It does not charge fees or issue refunds.
Should you use a booking page instead?
Booking pages are great for simple, standard appointments. Many businesses use both: a booking page for standard slots, and the assistant for everything that arrives by email, text, or message and needs a human touch. The assistant can also point people to your booking page in its drafts.
How does it send reminders?
With your approval, it can draft reminder messages for upcoming appointments, using a template you agree. Some businesses let reminders go out automatically after watching it work well; that is a choice you make explicitly.
What access does it need?
Read access to the inbox where requests arrive, and access to the calendar at the level your rules require: see free/busy to propose times, or make changes to add confirmed bookings. See sharing Google Calendar and Outlook Calendar.
What should stay with you?
Exceptions and judgment calls: squeezing in a regular client, handling a no-show, or anything involving money. The assistant flags these and drafts options.
How does it handle a team?
For a team, it can check several calendars and propose times with the right person. Agree who approves bookings for whom, and keep each person's private events private by sharing free/busy only.
How do you get started?
- Write down your booking rules, even roughly.
- Make sure every appointment lives on the calendar the assistant will read.
- Choose the inbox or channel where requests arrive.
- Give it two or three examples of booking replies you have written, so it learns your tone.
- Run it in draft-only mode for a couple of weeks, approving each reply.
- Review together and adjust the rules before allowing anything more.
What about time zones?
If you work with clients in other places, the assistant should always state the time zone in its drafts and check it against the client's message. Ask it to flag any request where the time zone is unclear rather than guessing.
Questions
Will it double-book me?
It checks the calendar before proposing times, but a person approves the booking. Keep events on the calendar it reads so it has the full picture.
Can it book on my behalf without asking?
Only if you explicitly allow it for specific cases. By default it drafts and you approve.
Does it work with text messages?
It depends on the tool and channels you use. We check during setup.