Reply to a customer by text if they wrote to you by text, by email if they wrote by email, and switch to email for anything they need to keep, such as a quote. When they text your business's 09 number, a Muzau agent replies with one short text, on its own or after your approval. It asks for their email only for a meeting invitation, and your team picks the conversation up by text when the agent hands it over.
A customer who sends a text has chosen a short exchange. They write from their phone, often between two things, and they will read the reply in the same place. Answering by email means asking them to go and look for the rest elsewhere, and first to give you an address they had not planned to give. The question was simple, the answer becomes a chore.
The opposite is true too. A quote, terms, a document to reread have no place in a 160-character text. The rule has two parts: reply on the channel where the customer wrote to you, then switch to email when there is something to keep. Muzau's text agent handles the first part, alongside your team: it replies by text, and asks for the email only for a meeting invitation. The second part stays with your team.
A customer's texts to the agent's number form one conversation, and the agent rereads the latest messages before replying. From the very first text, it replies to that number: it does not ask for contact details to do so. Its first message begins with "Hello, this is the AI assistant of" your business, so the customer knows right away who they are writing to.
The agent replies with what the Brain knows about your business, your site and your documents, and only with what is marked public. It writes plain text, with no lists or formatting: a reply made for a text, not a shortened email.
The text reply follows your setting for what goes out without you, the same as for your email replies. It goes out on its own, or it waits for your approval in a "To approve" card. When the agent does not know how to reply, your team writes its answer from the card, and it goes out from the same number: see the AI that replies to your customers' texts.
When the customer picks a free slot, the agent asks for their address: "To hold this slot and send you the invitation, please leave me your email address." It books the meeting if your setting allows it, and the invitation goes out by email (the details are on booking meetings by text). The address stays in the conversation. If the agent keeps a tracking file and is allowed to write to it, it files the customer there with the origin "SMS" and their first question. If it is also the address for your email follow-ups, it makes the link: a text reply stops the follow-up, just like an email reply.
The right channel depends on what the customer will do with your reply. If they read it and answer in a word, a text is enough. If they need to keep it, reread it or pass it to someone, it is an email.
For the shape of the message itself, see how many characters a business text should be.
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.