After a meeting

How do you follow up with a customer after a meeting?

After each meeting, a Muzau agent reads your notes, taken in Granola or forwarded to its address, and drafts the recap email for the customer: what was said and decided, then the next step you agreed on. You approve it in one click. If it goes unanswered, the agent follows up with the customer, and stops as soon as they reply.

Why the follow-up gets lost

The meeting went well, and everyone leaves with a next step in mind. Then the next meeting starts, the day runs away, and the recap promised for that evening goes out three days later, or never.

The customer has received nothing. They no longer quite remember what was agreed, and the momentum of the meeting fades. Your team keeps the meeting and the relationship; it is the written follow-up that takes time, and that is the part the agent takes on.

How the agent goes about it

Input

Your meeting notes

It does

Drafts the recap, opens the follow-up, picks up the commitments

It delivers

An email ready to send, and follow-ups that stop when the customer replies

Notes, wherever they come from

Granola connects in Muzau's tools: every note arrives on its own, with nothing to do. With another tool, or notes typed by hand, you forward the write-up to the agent's address.

The recap goes to the right customer

The address comes from the meeting invitees the note knows about, never from the text. If there are several outside invitees, or none, the field stays empty and you fill it in before sending. An address on your do-not-contact list is set aside.

Nothing goes out twice

If someone on the team has already written to the customer since the meeting, the recap withdraws. An internal meeting does not produce a recap.

The follow-up is kept up

Once the recap is sent, the agent follows up with the customer at D+3, D+7 and D+14 by default, a rhythm you set, picking up what was said. Commitments made during the meeting are picked up and dated: you are reminded the day before a promise is due, and the customer gets a follow-up if they were the one who promised.

What a good meeting recap contains

A recap is not a set of minutes. The customer should be able to read it in a minute and know what to do next.

• What was said, in three or four points, in the customer's own words where possible.
• What was decided, kept apart from what is still open.
• The next step: who does what, and by when.
• A single question at the end, so the customer has only one thing to answer.

The tone follows the meeting: if you were on first-name terms, the recap is too. That is also what the agent does, picking up the way you talk to each other. For the detailed format, see the sales meeting recap.

What it does not do

• It does not record your meetings: it starts from the note your tool, or you, give it.
• It does not guess the recipient from the text of the note: the address comes from the meeting invitees, or from you.
• It does not send the recap without you, unless you turn that option on.

Frequently asked questions

Which note-taking tools work?

Granola connects directly: every note arrives on its own. Any other tool works by forwarding: you send the write-up to the agent's address, whatever tool wrote it, including notes typed by hand.

Does the recap go out without approval?

No. By default, every recap waits for your approval. Sending without review is an option the business can turn on if it wants.

What about meetings that already happened?

With Granola, Muzau rereads your meetings from the last 7 to 90 days and shows you the ones that got no follow-up: you prepare their recap in one gesture, one or several at a time.

What happens to what the customer said?

It goes on their record, visible only to the people who were in the meeting. On the morning of the next meeting, you receive a brief: the last meeting, the commitments, the emails exchanged since.