You lose a customer before even sending a quote when their first request waits, or when a detail is missing and nobody asks for it again. A Muzau agent drafts the reply on receipt, day or night, asks again for what is missing on the dates you set, and finds in your mailbox the requests left unanswered for at least 2 days. Its replies go out on their own or after your approval, and the quote stays with your team.
A request arrives during a meeting. You will answer once you have the price. Then the day runs away. The customer may have written to others the same evening, and a reply reached them from somewhere else. They did not refuse anything: they simply heard nothing.
Or the reply went out with three questions, and the customer answered only one. Nobody asks for the rest again, and the quote never goes out. In both cases, it was not the price that lost the customer. It was the silence, at the moment when it was your turn to write. Your team keeps the quote, the price and the relationship; the agent holds those moments.
A request that arrives at the agent's address is handled as soon as it is received. A connected Gmail or Outlook mailbox, where an agent replies, is read again every minute. The reply is drafted right away, day or night, with what the Brain knows about your offers and your rules. You choose whether it goes out on its own or waits for you. When your website form, WordPress, Typeform or Tally, sends its notification, the agent replies to the visitor it points to; by default, that reply waits for your approval. In the site chat, the reply comes in a few seconds, and a text message received on the agent's 09 number gets one too.
When the agent lacks a price, a lead time or an agreement, it is instructed not to guess: it passes the request to you. A card arrives in "To do" with the reply already written, and each missing detail becomes a short question. You answer, the agent rewrites with your words, you say yes and it goes out. An email lets you know right away that a customer is waiting, and the alert can also arrive in Slack or Teams.
By default, the agent asks for nothing again. If you set it up, for example at D+2 then D+4, each follow-up asks again for what is missing, without repeating what the person has already given. The follow-ups stop when the file is complete. You then receive a card and an email with the customer's answers, and the next step already drafted: offer them a meeting, send them what you have planned, such as your price list, or decline politely. You read it before it goes out. See how to follow up a prospect who has not given everything.
When you connect your mailbox from the Follow-ups screen, the agent reads the last 60 days. It shows you the emails received that have waited for your reply for at least 2 days and that the AI judges useful. It then drafts their replies, up to 10 at a time, and each one waits for your approval. See also how to find requests left unanswered.
With or without a tool, these are the same moments you have to hold.
To find out where you lose customers, take last month's requests and note three dates for each: the request, your first reply, the quote. The longer of the two gaps tells you which moment to hold first. A request left with neither a quote nor a refusal is a customer lost without your knowing: reply to them, even late. Once the quote has gone out, it is up to the customer to write, and the risk moves: see how to follow up a quote.
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.