To answer your website visitors at any hour, a Muzau agent runs the chat: it replies on its own in seconds, using what your company's Brain knows and the pages of your site, and every reply is checked automatically before it is shown. With your calendar connected, it can book the meeting. What it does not know, it says so and, if you chose that option, passes it to your team with the visitor's contact details.
A visitor lands on your site in the evening, to compare options. They have a precise question: what is included, the lead time, how a first conversation works. The form promises someone will get back to them, and the phone only answers during office hours. They close the tab and ask their question on the next site.
Often, the answer already existed, on one of your pages or in your team's heads. What was missing was someone to give it at 10 pm, and to offer a meeting before the interest fades. Your team keeps the relationship and whatever takes judgment; the agent takes what already has a written answer.
A visitor is waiting at the bubble, so the chat replies in seconds, without waiting for approval, at 11 pm as at 10 am. The reply hours you set for emails do not apply to it. It relies on what your company's Brain knows (your tone, your rules, your answers) and searches the pages of your site for the answer to a precise question. What you keep for the team does not enter its replies. To install it (one line of code in WordPress, Webflow, Wix or Shopify), see how to put a chatbot on your company's website.
The chat is instructed never to state a price, a lead time or an availability that is not in your Brain. Every reply is also reread automatically before it is shown, and a reply that carries a specific warning sign is held back for your team: see what this check looks for. From the Autonomy page, you decide what it does on its own: book a meeting, send an email.
The chat offers up to three free slots, each on a different day, within the next 14 days and within your hours. It is the product, not the AI, that checks that the chosen time is free. Once the visitor has given their email, if your settings let it act alone, the meeting is booked in your Google Calendar or your Outlook calendar; with no calendar connected, the invitation goes out by email, if your company's email is turned on. Only then does the chat write "It's booked". See how a chatbot books a meeting.
When it does not know, the chat says so and then, if you chose that when creating it, asks once for the visitor's email or phone number. The request becomes a card in "To do", which your team picks up in the morning with the whole conversation. See what the chat does when it does not know the answer.
With or without an agent, an evening visitor goes through the chat, the form or the phone. Each one should tell them what they get right away, and what waits for opening time.
Two mistakes come up again and again. Writing "24/7" when only the chat answers at night. And promising, at 11 pm, a callback "within the hour": an announced wait is better than a promise that is not kept.
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.