Leexi, Noota, Fathom

How do you follow up on a Leexi, Noota or Fathom meeting summary?

To follow up on a Leexi, Noota or Fathom meeting summary, connect your tool to Muzau. A Muzau agent turns it into the recap email for the customer, which waits for your approval by default, and picks up the commitments made on both sides, each with its exact sentence. The day before a date the seller promised, they get a reminder; if the customer has not written the day after the date they gave, the agent sends them a short follow-up.

Why the promises in a meeting summary stay in the tool

Leexi, Noota or Fathom leave you a summary of each meeting. Written for your team, it often stays in the tool. Somewhere in the middle, "I'll send you the quote on Thursday", said in passing. Thursday comes, and nobody has reread the page.

The customer promised something too: "I'll send you the specifications on Monday". Nothing arrives, and nobody notices. Following up means sending the customer what was agreed, then keeping to the dates, yours and theirs. Your team keeps the relationship and honors its commitments; the agent keeps the list: who promised what, and by when.

How the agent goes about it

Input

The Leexi, Noota or Fathom summary of the meeting

It does

Drafts the recap, picks up the commitments on both sides, and dates them when the sentence allows

It delivers

A recap to approve, a reminder the day before, a follow-up if the customer forgets

A Leexi, Noota or Fathom summary becomes a recap to approve

Once your tool is connected to Muzau, each summary reaches the meeting follow-up agent you create in the Workshop, with its participants and its date. The customer's address comes from the participants: with a single person from outside the company, it is already filled in; with several, you choose. By default the recap waits for you in "To approve". For the language and tone of the recap, see the Fireflies meeting summary in French.

The seller's and the customer's commitments, picked up word for word

In each summary, the agent spots the commitments made, by the seller as well as the customer: sending a quote, calling back Monday, passing on a document. Each one keeps the exact sentence that states it. A sentence that cannot be found word for word is set aside, as is a commitment that carries a misheard name, and a mere idea does not count. This tracking needs a single outside participant: with several, the recap is drafted, but no commitment is tracked.

The due dates the agent can date, and the others

The agent dates the promise from the day of the meeting when the sentence says "today", "tomorrow", "the day after tomorrow", "in 3 days", a day of the week, or a full date written in digits. No date is guessed. "End of the month", "next week" or a date written out in words give a "Promise to track" card: it stays in front of you, with no reminder or follow-up.

A reminder for the seller the day before, a follow-up for the customer the day after

The day before a seller's promise is due, in the morning, they get a reminder by email and in "To do". Just one reminder, and none if the promise has already been kept. If the customer made the promise and has not written the day after the date, the agent sends them a short, courteous follow-up on that one point, on its own or after your approval depending on your setting: the details are in the customer promise not kept. The promise closes as soon as the customer writes to you, or the seller writes to them from a mailbox Muzau monitors. A single email from the seller to that customer closes all their promises to them, except a commercial proposal prepared by Muzau, which stays open until the email attaches it.

Before following up: reread the summary in five minutes

A summary says what was said; a follow-up says who does what, and by when. Five checks, with or without an agent:

• Every action has a name. "Send the quote" is not enough: write who sends it, you or the customer.
• Every action has a day. "Next week" becomes "Tuesday". A vague deadline reminds no one.
• A lead is not a promise. "We could run a trial" stays an idea until someone says "I'll take care of it".
• The original sentence settles it. A summary can give a commitment to the wrong person, or round off a figure.
• The recap repeats the commitments. End it with two lines the customer can reread: "On our side: the quote, Thursday. On your side: the specifications, Monday."

To turn "next week" into "Tuesday", ask the question in the recap: "I suggest sending you the quote on Tuesday, does that suit you?" The customer confirms or corrects. To avoid these vague promises from the meeting itself, see how not to forget what you promised a customer.

For a call noted by hand, see the recap of a phone call.

What it does not do

• It does not track any commitment from a meeting with several outside participants: the recap is drafted, with no reminder or follow-up on the promises.
• It does not date "end of the month" or "next week": these promises stay a card to track, with no reminder or follow-up.
• It does not read the text of your emails to know whether a promise has been kept: it looks at who wrote to whom, and when.

Frequently asked questions

Can you simply forward a Leexi, Noota or Fathom summary by email?

Yes: a summary forwarded by email to the Muzau agent's address produces a recap, to which you add the customer's address before sending. Tracking promises requires connecting the tool: it needs the participants and the date of the meeting, which a forwarded email does not carry.

Can the Fathom summary be sent to the customer automatically?

With Muzau, the recap drawn from a Fathom summary waits for your approval in "To approve" by default. What can go out on its own, and what always waits for your review, is detailed on the automatic meeting summary page.

How do you follow up on a call recorded with Leexi?

The summary of a call recorded with Leexi reaches the Muzau agent like that of a meeting, and it drafts the written recap. If the summary does not carry the customer's address, you fill it in before sending, and no promise is tracked. Muzau does not make calls: it writes, and the phone stays with your team.

Does a team meeting recorded by Noota produce a recap for the customer?

No, when all its invitees are on the team: Muzau recognizes it as internal and does not draft a recap. A colleague invited from a personal address passes for an outsider, and a meeting with no invitees at all produces a recap, with the recipient to fill in.

How do you spot who promised what in a Leexi, Noota or Fathom summary?

A Muzau agent picks up the seller's and the customer's commitments, ten at most per summary, each with the exact sentence that states it. It sets aside a sentence that cannot be found word for word, a commitment that carries a misheard name and a mere idea. With several outside participants, no commitment is tracked.