To receive and reply to your customers' texts from a computer, Muzau gives your business a 09 number: incoming texts arrive in Muzau, open in the browser, with nothing to install. A Muzau agent replies there on its own or after your approval. When it hands over, your team sees the exchange and a drafted reply, reads it, edits it and sends it from the same number.
A customer texts a salesperson's mobile: "Does your proposal still stand?". The message stays on that device. Nobody else sees it, the reply gets typed with a thumb between two meetings, and when the salesperson is away, the customer waits. Apps that mirror the phone onto the computer give a bigger screen, but still for one person, from their personal number.
To read and reply from a computer, you first need a dedicated number for the business's texts, whose conversations open on the team's screen, with the history of the exchange. Your team keeps the relationship and the decisions; the agent replies to what it knows and drafts the rest.
Muzau runs in the browser: nothing to install on the team's computers. Incoming texts are kept there even when the agent is paused or the business has run out of credits, as the page on the AI that replies to your customers' texts explains.
The customer's number is shown in the French format (06 12 34 56 78) and the card carries the label "By text". The agent's messages and the team's are told apart: you see what has already been said before you write. When the agent hands over, a "Someone is waiting for a reply (text)" card arrives with the customer's number. An email, or a message in Slack or Microsoft Teams, can alert the team.
On the card, the agent drafts a reply for your team, written to fit in one text: one or two short sentences, with no sign-off or signature. You read it, edit it if needed, and send it. If the draft fails, the field is still there to write the reply yourself. The replies the agent holds for your approval, depending on your setting, wait in "To approve" and go out in one click.
The customer receives the team's reply from the agent's number, the one they wrote to. STOP, the cap of 100 texts a day and credits apply to the team too. What the team sends is filed as written by them: the agent rereads it before its next reply, and does not claim it as its own. A counter under the field shows how many texts the message will go out as, up to 3: see the right length for a business text.
With or without an agent, a text read on a shared screen can go unanswered, or get two replies. A few rules prevent that.
When an AI was leading the exchange, taking over without contradicting it takes a bit of method: see taking over a conversation led by an AI.
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.