To find the customer requests left unanswered in your inbox, connect it to Muzau: the agent rereads the last 60 days and shows you the emails received that have been waiting for your reply for at least 2 days. The AI sets aside notifications, newsletters and personal exchanges along the way. The agent drafts a reply to the requests you choose, up to 10 at a time, and each one waits for your approval. Reading marks nothing as read on your side.
A request read on a phone, between two meetings, loses its "unread" mark. A few days later, nothing sets it apart from the emails that already got a reply. To know whether it is still waiting, you have to reopen the thread and see who wrote last, thread after thread.
Meanwhile, the customer waits, and may have asked elsewhere. The older the request, the more care the reply needs. Your team keeps what commits you, a price, a deadline, a decision, and approves each reply; the agent finds the requests, sorts them and drafts the text.
You connect your Gmail, Outlook or Microsoft 365 inbox once, or one hosted at OVH or Ionos. The agent then rereads the last 60 days, messages received and sent. You widen or narrow that period in steps of 15 days, from 15 to 180 days. Nothing is marked as read on your side, no attachment is downloaded, and the text of an email is read only if it needs a look.
An email received is suggested when the person has been waiting for your reply for at least 2 days. For a given person, only the latest exchange counts: if you have written to them since, the old request does not appear. Automatic messages, calendar invitations, exchanges between colleagues and people who have unsubscribed are set aside before anything is read. The AI then reads the start of the latest email and keeps only what comes from a customer, a prospect, a partner or a supplier: no administrative matters, no personal exchanges, no newsletters. Each conversation is judged three times; when the opinions differ, it is shown to you separately, and you decide. In the same list, conversations where the customer owes you a reply are offered for follow-up, which lets you follow up on old quotes left unanswered.
You choose the requests to answer, up to 10 at a time. The agent writes each reply on its next pass, not right away, from the email received and what the Brain knows about your business. Each one waits for you in "To approve", under the message received: you send it, edit it, have it rewritten with an instruction, or do not send it. Approval is lifted only if you let the agent send on its own and your business allows it for emails reread in the inbox. Even then, a reply it is unsure of waits for you, with the reason.
From your first edit to the tone, the length or the sign-off, a writing rule is created for all your agents. A correction to a price or a date becomes a suggested addition to the Brain, which goes in only after you click "Keep". For requests still to come, see how to leave no customer request unanswered.
With or without a tool, one criterion matters: who wrote last.
To apologize for replying late, one sentence is enough. The customer wants their answer, not the story of your week: acknowledge the delay, answer the question asked, and end with a simple next step.
An example, to adapt: "Hi Claire, sorry for the delay, your message slipped past me. For your request, here is what I can offer: ... Would you like to talk on Thursday or Friday?" Avoid "I'll get back to you" without a date, and do not promise a deadline you will not meet.
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.