No: automatic meeting notes summarize the conversation, they do not follow up with the customer. From the meeting note, taken in Granola or forwarded by email, a Muzau agent drafts the recap email, which by default waits for your approval in "To approve", then follows up with the customer who does not reply. With a Granola note, it reminds the salesperson of their dated promises and files what the customer said on their record.
A note-taking tool delivers a summary of the meeting: the topics covered, what was decided, sometimes a list of actions. It is a document for the team. It stays in the tool, and it does not say which address to write to, what to tell the customer, or when to follow up.
The follow-up starts after that summary. The customer expects an email that picks up the conversation and the next step, then the promised document on the day announced. If they do not reply, someone has to follow up. Your team keeps the meeting and the relationship; the agent takes the written follow-up: the recap, the follow-ups, the reminder to the salesperson of what they promised.
After each meeting, the Muzau agent writes the recap email and puts it in "To approve": by default, what was said and decided, then the next step you agreed on. It is instructed never to write that something was said if the note does not contain it. Nor should it copy to the customer what the team noted for itself alone. The address comes from the meeting invitees, never from a name mentioned during the conversation. With no invitee, as with a forwarded note, you fill it in before sending. An internal meeting, with no outside participant, does not produce a recap.
Once the recap is sent, a follow-up file opens. With no reply, the agent follows up with the customer at D+3, D+7 and D+14 by default, on its own or after your approval depending on your setting. It restates in one sentence what was agreed and asks for the next step. The follow-ups stop as soon as the customer replies, or someone on the team writes to them from a Gmail or Outlook mailbox that Muzau picks up. For the whole sequence, see following up with a customer after a meeting.
With a Granola note and a single outside participant, the agent picks up the commitments made during the meeting, by the salesperson as well as by the customer, each with the exact sentence that states it. For a salesperson's promise whose deadline is stated simply (tomorrow, Friday, in 3 days), they receive a reminder the day before, in the morning, by email and in "To do". A promise with no clear date becomes a "Promise to track" card. The details are on the page not forgetting what you promised a customer.
Their need, their budget, their deadline, who decides, their objection: what the customer said themselves goes on their record in "Customers met", each item dated and linked to the note. Nothing is kept on a sensitive subject. On the morning of the next meeting, if it is in your connected Google Calendar or Outlook calendar, the salesperson receives a brief covering all of this. Promises and the record need the participants, the date and the transcript of the meeting, which a Granola note provides: a write-up forwarded by email gives only the recap and its follow-ups.
With or without a tool, reread each set of automatic meeting notes with these five questions. A missing answer is a hole in the follow-up.
A simple test: if the salesperson is out tomorrow, does a colleague know, from reading the notes, who to write to, what to say and by when? If not, the summary may be good, but the follow-up is not yet covered.
For a Granola note, see the recap of a Granola note; for a Teams meeting, the Teams recap.
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.