To send a customer the recap of a Granola note, connect Granola to Muzau, then create a meeting follow-up agent. Every minute, this Muzau agent rereads the notes you took yourself, without changing anything in Granola or reading your private notes, and drafts the recap email. The recap waits for your review in "To approve". It only goes out on its own if you allowed it and the customer's address is certain.
At the end of the meeting, Granola leaves you a note. It is written for you: your points, your remarks, sometimes what you think of the budget or of the person who really decides. The customer expects something else: what was agreed, and what they need to do next.
Between the note and the email, there is still sorting, rewriting and finding the customer's address. This work is short, and it is the work that slips to the evening, then to the next day. The agent drafts the email; you keep the review and the relationship.
Granola connects in one click from Muzau's Tools page. The connection alone sends nothing: the meeting follow-up agent is then created in the Workshop, with two questions. What should each recap contain, and on which days should the customer be followed up, or never? Just before creation, you choose what goes out without you; the setting opens on approval of every send. If you turn on sending without approval, only the recaps whose customer address is certain go out without you. An attachment, or a figure or deadline that is missing from both the note and the company Brain, always holds the recap in "To approve".
Every minute, Muzau rereads the meetings you took notes on yourself: the invitees, the summary and, when there is one, the transcript. It changes nothing in Granola and does not read your private notes. A note without a summary waits until Granola has finished it. Only meetings from the last two days count, counted from the connection. A note a colleague shares with you does not count: each team member connects their own Granola (see recaps from several salespeople).
The customer's address comes from the meeting invitees the Granola note knows about, never from a name spoken during the conversation. With a single outside participant, it is already filled in; with several, the agent suggests them and you choose; with no invitee, you type it in. An internal meeting does not produce a recap. If Muzau reads your Gmail or Outlook mailbox and sees that you have already written to the customer since the meeting, the recap withdraws, to avoid a duplicate. Before sending, you can still change the recipient, the copies, the subject and the text.
In Muzau, the "Your meetings" page lists your Granola meetings from the last 7, 30, 60 or 90 days, with the status of each: to approve, sent, set aside, internal, note not ready, already written to the customer. There you prepare the forgotten recaps in one go, ten meetings at most at a time, including those from before the agent was created. These recaps always wait for your approval. "Try a dry run" shows the recap the agent would write, without creating or sending anything.
A recap is only as good as the note it comes from. Whether the agent writes it or you do, a few habits around the meeting change the email the customer receives.
For the outline of the email itself, see the sales meeting recap. To get the recap into your CRM too, see how to connect Granola to HubSpot or Pipedrive.
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.