A thank-you email after a sales meeting restates what was decided and the next step, then thanks the customer for what they gave you: a lead, an introduction, a piece of advice. A Muzau agent drafts it from your Granola note. It only keeps that thanks if the transcript contains the customer's exact words. By default, the email waits for you in “To approve”: you read it, then send it.
“Thanks for your time, looking forward to speaking again.” The customer gets that line from almost everyone they meet. It does not remind them what was decided, does not tell them what comes next, and nothing sets it apart from the one they received yesterday from another supplier.
What makes a thank-you useful happens during the meeting itself. The customer gave you the name of a colleague to call, advised you on how to present the project internally, pointed out a constraint you had not seen. A thanks that names that gesture shows you listened, and it fits in one sentence. But you still have to find it again in the evening, between two other meetings, and word it well.
When Granola's transcript allows it, the agent spots what the customer gave you during the conversation: a lead, an introduction, a piece of advice. That gesture is only kept for the thanks if the customer's sentence appears word for word in the transcript. A proper name that no written source confirms, or a sensitive subject, is set aside. There is only one thank-you per recap, even if the customer gave you several leads.
If the transcript shows what the customer expects from what follows, the email answers it, three expectations at most. The rest follows the content set when the agent was created: by default, what was said and decided, then the next step you agreed on.
The email is written in the first person, in the name of whoever took the note, and signed with their name. It follows the language of the meeting. When Granola's transcript allows it, it also picks up the tone of the conversation, formal, friendly or relaxed, and the formal or informal “you” that was heard. For that choice, see whether to use tu or vous with a customer by email. Under the signature, a discreet line says the message was drafted by your company's AI assistant; you can reword or remove it.
By default, every recap waits for your approval. You can change the subject, the text, the recipient or the copies, then send it. If you have already sent your own thank-you from Gmail or Outlook, and Muzau monitors that mailbox, the pending recap is withdrawn to avoid a duplicate. The one exception: a recap that attaches a commercial proposal stays, if your email does not attach it.
A good thank-you reads in a minute. It follows a simple order.
An example, to adapt: “Hello, thank you for our conversation this morning. Thank you also for advising me to present the project to your management on one page: I will send it to you by Thursday. We went with the first option in the proposal. On your side, you present it internally next week. Does that plan work for you?”
Three mistakes come up often. Thanking for a gesture that did not happen, or inflating it: the customer remembers. Piling up thanks, for the time, the welcome, the trust, until none of them carries weight. Waiting several days: send it the same day, or the next morning at the latest. For the full format, see the recap of a sales meeting, and for what comes after sending, following up with a customer after a meeting.
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.