To stop the same time slot being booked by two customers, check that it is free when you book it, not only when you offer it. With no calendar connected, a Muzau agent books each slot in Muzau: it cannot be taken twice. With Google Calendar or Outlook, the agent only offers free times, rechecked when your team confirms a ready reply. A "To approve" card does not reread the calendar when you approve it: do not wait.
In the morning, two customers ask for a meeting. Each gets a proposal, and Thursday 10 a.m. is in both. The first accepts at noon, the second late in the afternoon: nobody removed the slot in between. Or a colleague took that Thursday over the phone without noting it in the calendar.
An offered slot is not a booked slot. Between the proposal and the reply, hours pass and the calendar changes. The double booking is found at best at the second confirmation, at worst on the day itself, when two customers are waiting and one has to be called back to apologize.
When no calendar is connected, Muzau books each slot in its own database: the same time cannot be taken twice there. If another customer has just taken it, the agent books nothing and replies: "Sorry, this slot was just booked in the meantime", inviting the customer to reply to get other availabilities. On a card you approve, a slot that is already taken shows an error and nothing goes to the customer. It only knows the meetings booked by Muzau: see meetings with no calendar connected.
A Muzau agent reads the busy hours of your calendar (see offering time slots in Outlook or Gmail) and only offers free times, with 15 minutes of margin by default before and after your existing meetings. When the customer picks a slot or asks for another, it is the system, not the AI, that checks the time fits entirely inside a free moment before booking the meeting. In Outlook, a meeting marked "free" or "working elsewhere" does not block the slot; busy, tentative or out of office does.
When a Muzau agent passes you a meeting request, a ready reply waits for you in "To do", with the first free slot already written. When you click Yes, the system rechecks that the slot is free before booking the meeting: if it was taken in the meantime, nothing goes out and the next one is offered in its place; if the calendar cannot be read, nothing goes out. The same applies when your team confirms by text message. In the website chat, "It's blocked" is only written after the calendar has accepted the meeting; if the slot was taken in the meantime, the chat says so and offers to pick another.
When you create it, you choose whether the agent books meetings on its own or submits them to you in a "To approve" card. With a connected calendar, this card does not reread the calendar when you approve it: a slot taken since can still be booked. Approve these cards without waiting, or let the agent book on its own: the meeting is then booked right away, even if its replies wait for your opening hours.
If the double booking happens anyway, tell the second customer as soon as you see it, not on the day itself, with one sentence of apology and two slots on different days. For example: "Hello, the Thursday 10 a.m. slot was taken just before your reply, and I apologize. I can offer Tuesday 2 p.m. or Wednesday 11 a.m.: which suits you?" If they reply with a time of their own, see what to do when a customer asks for another time.
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.