To chase a customer who doesn't reply, write short, in the original thread, and ask for the next step. A Muzau agent finds the conversations in your inbox that went quiet over the last 60 days, follows up the ones you hand it, by default at D+3, D+7 and D+14, and stops as soon as the person replies. To begin with, every follow-up waits for your approval.
A customer's silence is rarely a no. Your email landed on a busy day, the decision is waiting on someone else, or the question needed an effort they put off until later. Without a follow-up, the conversation fades out and nobody decided it should.
The hardest part is not writing the follow-up, it is knowing which ones are due. Pending conversations are scattered across the inbox, mixed in with notifications, and nothing flags the one that has been asleep for ten days. Your team keeps the relationship and the judgment; the list and the follow-ups, the agent keeps. For a specific quote, see following up on quotes.
When you connect your mailbox from the Follow-ups screen (Gmail, Outlook or Microsoft 365, or an IMAP mailbox like those from OVH or Ionos), the agent rereads the last 60 days, messages received and sent, and shows you the conversations that went quiet. A conversation is only suggested if your business wrote last at least 3 days ago. At each reread, at most 48 conversations are examined: in a very busy mailbox, the others are counted and wait, and the screen says so.
Automatic messages, calendar invitations, exchanges between colleagues and people who have unsubscribed are set aside before the AI reads anything. The AI then reads the start of the last email in each conversation and keeps only those where a customer, prospect, partner or supplier still owes you an answer or a decision. Each conversation is judged three times; when the opinions differ, it is shown to you separately, and you decide.
You tick the conversations to chase and hand them to the agent, up to 30 at a time. For the others: “Not that one”, or “Never chase” a person, or even their whole domain, and the agent applies those choices to later rereads. You read and correct each text before handing it over: if you click “Send”, that reviewed text goes out as it is. Later follow-ups wait for your approval on the Manage page, under “To chase?”. After 10 follow-ups in a row sent without edits, Muzau offers to let them go out on their own: the decision is yours.
The follow-up goes in the same thread as your original email, with the team member who sent it in copy. It goes from your connected mailbox, or failing that from the agent's address. It goes by default at D+3, D+7 and D+14, a rhythm you set up to six follow-ups. For the tone and the phrases to avoid, see how to politely chase an email left unanswered. Everything stops as soon as the person replies, even a colleague in the same thread, or when someone on the team writes to them from the connected mailbox. An out-of-office message does not count as a reply; the details are in how to avoid a duplicate follow-up.
With or without a tool, a follow-up that gets a reply follows a few simple rules.
An example, to adapt: “Hi Marc, to move forward on the proposal we talked about, I only need your choice between the two options. Could you let me know by Friday?”
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.