Bookings taken in chat, written into a real calendar
The assistant offers only the slots the availability engine computed from your rules, then writes the booking into a real calendar: separate resources, confirmations, reminders and Google Calendar sync.
The starting point
Taking the appointment is easy, keeping it straight isn't
Taking the booking isn't the problem. The second book is.
Requests come from chat, phone, email and the door, and end up in different notebooks. Then somebody promises a slot that was never there, and the person who shows up pays for it.
- Slots promised in chat that were never actually free
- One calendar on paper, one on a phone and one in someone's head
- Large groups accepted without anyone deciding
- Seats left empty by a no-show nobody was told about
What it does
What the assistant actually does
It never invents a slot
It offers only what the engine computed from hours, closures, buffers, minimum notice and capacity. If it declines, it says which rule prevents it.
Separate resources, separate books
Tables, rooms, chairs, practitioners, agents or vehicles: each with its own book and capacity, so a table for two and a table for eight are not the same thing.
Services with their own duration
A 45-minute first visit does not go into a 30-minute gap. A service can carry an internal pause, like a colour's processing time: during those minutes the resource is bookable again.
You decide what it can confirm
Always, never, or with rules: large groups, short notice, new customers, specific resources or channels. The rest lands in the approval queue, with the reason for the wait.
A real calendar, not a list
Month view with a day detail panel, day, week and list views, a room-by-room timeline, drag to move, and undo on every action.
Confirmations and reminders
The customer gets the confirmation when you approve and a reminder before the appointment, so no-shows drop and free slots get filled.
How it works
Three steps, then it works
Describe how you work
Resources, services, durations, weekly hours, closures, buffers and notice: these are the rules the engine will use for every offer.
Choose who confirms
The assistant alone, with your own rules, or always a person. Every pending booking shows the reason and the conversation it came from.
Connect the calendar
With Google Calendar sync appointments land in the staff member's calendar, and their existing commitments block the slots.
Connections
What it connects to
Google Calendar
Two-way sync: we write the appointments and read the commitments that block availability.
The tool you already use
If you would rather not move the calendar, the assistant can notify staff who enter it, or send the customer the link to your booking system.
Every channel
Chat, social, email and phone write into the same calendar, under the same rules.
Reminders on WhatsApp
Confirmations and reminders use the approved templates prepared when the channel is connected.
Frequently asked questions
Does it work if I already use another system?
Yes. You pick the mode you prefer: internal booking, notify staff who then enter it in your system, or send the customer the link to your booking tool.
Can the assistant confirm on its own?
You decide: always, never, or with rules (large groups, short notice, new customers, specific resources or channels). Anything pending lands in the approval queue with the reason, the customer and the originating conversation.
Do customers get a reminder?
Yes. On approval they receive the confirmation and, before the appointment, a reminder. They exist to cut no-shows, the quietest cost line in any calendar.
Does the calendar use my sector's words?
Yes. A restaurant reads bookings and covers, a hotel stays and guests, a rental company rentals, a practice visits. The word comes from the sector and you can replace it with your own.
One calendar, kept current by whoever answers
Book a demo: we set up resources, hours and approval rules for your business and show you the engine at work.