A chatbot books an appointment in Google Calendar or Outlook if it reads your free hours and writes into the calendar itself. The chat of a Muzau agent offers the visitor up to three free slots in the next 14 days. The visitor picks one and gives their email, Muzau checks the time, then books the appointment: your calendar sends the invitation, and only then does the chat write "It's blocked". In your settings, you decide whether it books on its own or passes the request to your team.
A visitor asks for an appointment in the bubble on your site. If the chat answers "leave your details, we'll get back to you", the rest goes by email: a slot offered the next day, a "Thursday would suit me better", another exchange about the time. Meanwhile, the visitor has gone on looking, and a request ready to move forward is sitting in an inbox.
Booking the appointment in the conversation takes two things: knowing what is really free in your Google Calendar or Outlook, and saying "it's booked" only once the event has been created. A chat that confirms a slot it has not put anywhere creates an appointment that nobody is expecting the customer for.
When a visitor wants an appointment, the Muzau chat immediately offers up to three free slots, each on a different day, within the next 14 days and within the hours you have set, avoiding lunchtime on its own. It only offers the slots the product gives it. To find them, Muzau reads only the busy hours in your calendar, never the title, place or description of your appointments. If the calendar is full or briefly unreadable, the chat offers no slot rather than invent one.
The visitor writes "Thursday", "the second one", or asks for another time: "Friday at 4 pm?". The AI recognizes which one they want, then it is the product, not the AI, that checks the time fits entirely inside a free window before blocking it. A time that is already taken or outside your hours is not booked.
Once the slot is chosen, the chat asks for the address if it does not have it yet: "To block this slot and send you the invitation, please leave me your email address." The appointment is then booked in your calendar, which sends the invitation to the visitor, and the chat only writes "It's blocked" once the calendar has accepted it. The appointment carries the mode you have set, video call or in person: see how the place is shown to the customer. If the slot has just been taken, the chat says so and offers to pick another. With no calendar Muzau can write to, the invitation goes out from your business's email, to the visitor and to you: that is the case of the appointment without a connected calendar.
The chat answers without waiting for approval, because a visitor is waiting at the bubble. What it is allowed to do on its own, however, is set on the Autonomy page. If your settings do not let it book an appointment, it passes the request to your team, who get back to the visitor to confirm it. It does the same if the visitor writes an IBAN in the conversation: that is how a transfer fraud begins. Unless one of your rules asks to know something first, its questions to prepare the conversation come after the chosen slot: see why to ask them after the appointment.
Whether a chatbot books in Google Calendar or in Outlook, the same settings decide whether appointments hold. Check them before putting it online:
Then try the chat as a visitor would: ask for "Thursday", then a time outside your hours, then the only slot of a busy day. At Muzau, these tests are done from the cockpit, without any appointment being booked or any invitation sent.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.