When a customer promised to send a document after the meeting and didn't, follow up the day after the date they gave, about that one document only. A Muzau agent picks up the promise from the Granola note, dated when it was stated simply (tomorrow, Friday, in 3 days). If the customer hasn't written the day after that date, the agent sends the follow-up, on its own or after your approval. Only one follow-up goes out, then the conversation goes back to your team.
At the end of a meeting, the customer says “I'll send you the specifications tomorrow” or “I'll get you our figures on Friday.” They fully mean it. Then they go back, their week starts again, and the document sits in a folder. That isn't necessarily a bad sign: often, they just need a reminder.
On your side, the sale hangs on that document: without it, no quote, no next step. Following up means remembering the promise, the day given, and finding a tone that reminds without pressing. The agent takes on that memory and that first reminder; the relationship and what comes next stay with your team.
After the meeting, a Muzau agent reads the Granola note and spots the commitments made on both sides, including the customer's: sending a document, passing on a plan, confirming a figure. Each one keeps the exact sentence that states it, as with your team's promises (see not forgetting what you promised a customer). This follow-up needs a note with a single participant from outside the company.
The date is read from the customer's sentence, with the same rules as for your promises: “tomorrow,” “the day after tomorrow,” “in 3 days,” a day of the week or a full date in figures. Otherwise, the promise becomes a “Promise to follow” card, which stays in front of you, with no follow-up. The agent never sets a date itself.
If the customer still hasn't written the day after the promised date, the agent sends them a short, courteous follow-up that is only about that document, without mixing in the meeting's other promises. It goes out on its own, or waits for you in “To approve,” depending on your setting. There is only one follow-up per promise, and the agent has to be active, with follow-ups set up. A person on your do-not-contact list does not receive it.
As soon as an email from the customer arrives after the meeting, at the agent's address or in your Gmail or Outlook inbox connected to Muzau, the promise closes and the pending follow-up is withdrawn. Muzau looks at who wrote, and when, not at what the email says.
The customer committed themselves: the follow-up only reminds them of their word, as long as it doesn't sound like a reproach.
A skeleton that works: “Hello [first name], following our meeting, you offered to send me [the document]. Once I have it, I'll prepare [the next step]. The file as it is is enough for me. Have a good day, [signature].” If nothing arrives after this follow-up, change channel: a two-minute call often settles what a second email doesn't. For what comes after a meeting that went unanswered, see following up with a customer after a meeting.
The safest approach is still to have the customer name the day before leaving, in their own sentence: “I'll send it Thursday.” A date they say themselves commits them more, and it is also the kind of date the agent can pick up.
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.