To write a sales meeting recap, the one you send to the customer, restate in a few lines what was said and decided, then the next step you agreed on. A Muzau agent writes it from your notes, in the first person and signed by whoever took them, in the language of the meeting. By default, it waits for you in "To approve": you read it, correct it if needed and send it to the customer.
Meeting notes are not yet a recap. They mix what the customer said, what you promised them and what you think of them: their real budget, the objection left hanging. Before writing to the customer, you have to sort, rephrase and find their address. Between two meetings, that sorting waits, and the recap goes out late, or not at all.
For the customer, though, it is often the only written trace of the conversation: they come back to it, forward it to the people who decide with them, and reply to it if the next step is clear. Sent early, it keeps the momentum of the meeting.
By default, a Muzau agent puts in the recap what was said and decided at the meeting, then the next step you agreed on. You can change this content when you create the agent, in the Workshop. An internal meeting, with no one from outside the company, does not produce a recap.
The recap prepared by the Muzau agent is written in the first person, signed by whoever took the notes, in the language of the meeting. With the Granola transcript, it also picks up the tone of the conversation and the register heard (see first-name or formal terms with a customer by email). Without a transcript, it is written from the summary alone, and the summary of a note forwarded by email carries no first name in the signature.
The Muzau agent is instructed never to write that something was said if the note does not contain it, and never to copy to the customer what the team noted for its own use. The writer does not receive the transcript, only what was drawn from it: the tone, the expectations, the commitments. One check is added: a recap that cites an amount or a figure for a deadline that appears neither in the note nor in what Muzau knows about your business waits for your review. The rest relies on your approval.
The customer's address comes from the meeting invitees the note knows about, never from a name spoken during the conversation: with a single outside participant, it is filled in; with several, the agent suggests them to you; with no invitee, you type it in. Before sending, you can change the sending address, the recipient, the copies, the subject and the text. Sending without approval exists, off by default, and a recap with no certain recipient or with an attachment always waits for you.
A sales recap does not tell the story of the meeting: it fixes what was agreed, so that the customer knows what to do next. In this order:
For the customer, or for yourself? Write two texts. The customer receives only what they heard and what was agreed; your impressions, their room to negotiate, your view of their budget stay in your internal note, which the sales visit report helps you keep without a spreadsheet.
The right moment. Send it the same day, while the customer still has the conversation in mind. Put in it no price or deadline that is not in the note: once written, it commits you. To thank someone for a lead or an introduction, see the thank-you email after a meeting; if the customer does not reply, what comes next is covered in the follow-up 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.