To acknowledge a quote request, restate the request in the customer’s own words, say what happens next and when, and ask no question. A Muzau agent can acknowledge the requests it receives: it reuses their words, announces the next step, and if its reply still asks a question, Muzau has it rewritten, once. You choose whether it sends on its own or after your approval, and the quote stays with your team.
A quote request often arrives while the customer is comparing options. Until they have received something, they do not know whether it got through, or whether anyone has read it. The quote itself takes time, and in between, silence breeds doubt.
The stock message “We have received your message” says neither which request nor what comes next. A good acknowledgment proves someone read the request and tells the customer when they will hear back. Your team keeps the pricing and the relationship; it is this first message, to be written for every request at any hour, that the agent takes on.
If you ask it to acknowledge requests, a Muzau agent confirms receipt using the words of the request and says what happens next. Its instruction is to ask the customer nothing: if its draft still asks a question, Muzau has it rewrite its reply, once at most, and the second version stands as it is. The one exception is a message too vague to tell what it is about: the agent then asks a question, just one.
A request that reaches the agent’s address is handled on receipt, and a connected Gmail or Outlook inbox is reread every minute. The acknowledgment is written right away, day or night. You choose whether the agent sends it on its own or shows it to you first, and reply hours can push the sending to the next opening. By default, the email carries a line at the bottom saying it was prepared by your company’s AI assistant. For a request that came from a WordPress, Typeform or Tally form, see replies to the contact form.
An acknowledgment promises a next step. In a reply in French, Muzau spots the promise to get back to the customer, and the reply then waits for you in “To approve”. It is not held if the agent also passes you the request in a “To do” card, or if it keeps a file: Muzau then tells you when it is complete. A reply that suggests a date that neither your calendar nor the message provided also waits for you. As for the lead time announced, the agent is instructed to take it from the Brain, what Muzau knows about your business. When a customer is waiting for an answer that depends on you, Muzau lets you know right away, by email or in Slack or Microsoft Teams, then reminds you if it is still waiting after four hours.
A follow-up agent opens one line in its file for each request received by email: the date, the customer, the subject. Two requests from the same customer make two lines. The date stays that of the request, and follow-ups are counted from it. You have to give the agent permission to write in the file, which is refused by default, and the file can be copied into Google Sheets. To see what happens to each line next, see request tracking.
An acknowledgment fits in four or five lines, in this order.
The right moment is the same day, while the customer still has their request in mind.
Three mistakes come up again and again. The identical message for everyone, which could answer any request. Questions slipped into the acknowledgment: the customer answers them and waits for a real reply that nobody has prepared. The deadline promised then missed, which does more harm than no deadline. If you can answer the substance right away, do; if you lack information to price the job, ask for it in the reply to the quote request, not in the acknowledgment.
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.