AI meeting notes: from recording to tasks, from tasks to follow-up

The first rule: permission before recording

Before recording a meeting, tell every participant it will be recorded and get their agreement. This isn't only courtesy. Many jurisdictions restrict recording conversations without the consent of the people in them: in Turkey, for example, recording a non-public conversation you take part in without the other speakers' consent is an offence under the Turkish Penal Code (Article 133). Data protection laws such as KVKK and GDPR also treat voice recordings as personal data.

In practice:

• Add "This meeting will be recorded for note-taking" to the invitation.
• Say it again at the start of the meeting.
• If a participant objects, don't record; take notes by hand.
• Decide how long recordings are kept and who can access them.

Bot or no bot?

AI can join a meeting in two ways:

• Note-taker bot: joins an online meeting (Zoom, Google Meet, Teams) as a participant. Everyone sees the bot in the list, which keeps the recording transparent.
• Botless recording: the audio on your own computer is recorded. Used for in-person meetings or with customers who don't want a bot. Here, informing participants is entirely your responsibility.

The parts of a useful meeting summary

For an AI summary to be useful, it needs a structure:

A full transcript is valuable for the archive, but nobody reads it. The real value is in decisions and tasks.

Tasks: no task without an owner and a date

The part of meeting notes most often lost is the tasks. "We'll update the price list" is not a task; "Ayşe will update the price list by Friday" is.

AI extracts tasks from the conversation, but a person should confirm owners and dates before the meeting ends. Confirmed tasks belong in the team's task list, not a notebook, with a reminder when the date comes.

After a customer meeting: the follow-up email

The most effective close to a customer meeting is a short follow-up email the same day:

AI can draft this email from the meeting, but it must be read before sending. A wrong commitment sent to a customer is worse than no email at all.

Before the meeting: quick preparation

AI's least-used but most valuable job is preparing a briefing before the meeting: what was last discussed with this customer, is there an open quote, is an invoice overdue, what was their last complaint? Five minutes of reading saves the first ten minutes of the meeting.

Connecting to the sales process

A meeting with a prospect is a stage in the sales process. Afterwards, the lead's stage should be updated and the next meeting put in the calendar. AI can suggest this ("Shall we move this lead to the offer stage after this meeting?"); the decision is yours. Sales stages are covered in our small business CRM guide.

Privacy: who sees what?

Meeting notes are often sensitive: price negotiations, staff matters, customer problems. So:

• Decide who can see each meeting.
• Delete recordings and transcripts after the period you set.
• Check how the AI service handles data (whether it trains on it, where it stores it). We cover this in our subscription or API key guide.

When it doesn't help

To be honest, AI note-taking isn't the right tool for every meeting:

• In noisy rooms and meetings where many people talk at once, transcript quality drops.
• Technical terms and proper names may be misspelt; teaching the system speaker names helps.
• Sensitive conversations (dismissals, health) should not be recorded.

Example: a consultancy's customer meeting

Picture a three-person management consultancy holding about ten customer meetings a week, most online and some at the customer's office.

Before the meeting: ten minutes before, the consultant reads a short briefing: what was said last time, which tasks are open, where the quote stands, whether the last invoice was paid.

At the start: "We record meetings for note-taking; is that OK?" The invitation says the same. The customer agrees. Online, the note-taker appears in the participant list.

At the end: in the last five minutes the task list goes on screen. One of the seven tasks the AI extracted was misunderstood ("we'll prepare the report" should be "the customer will send the report"); it is corrected. Each task's owner and date are confirmed.

After the meeting: the consultant reads the follow-up draft, fixes one sentence and sends it the same day. The lead's stage moves to "offer" and the next meeting goes into the calendar.

A week later: overdue tasks show in the consultant's list; one isn't finished, and the customer gets a short update.

The consultant focuses on the customer instead of note-taking, and nothing after the meeting gets forgotten.

Which meetings shouldn't be recorded?

• Performance reviews and exit conversations,
• Conversations about health or private life,
• Meetings about legal disputes,
• Any meeting where a participant objects.

In these, short handwritten notes and a separate written record of decisions are better.

Meetings in Era

Era's Meetings module joins meetings in two ways: send Era's note-taker to the meeting, or record botless from your own computer. Before the meeting it prepares a briefing; afterwards it writes the notes, tasks, follow-up email and next steps.

• Tasks are extracted from the meeting; each becomes a task, or is dismissed, with your approval.
• The follow-up email is a draft: you edit, approve and send it, or discard it.
• Suggested next steps (moving the lead's stage in Sales, booking the next meeting) are applied with your approval too.
• Connect your calendar and meetings are read from it; you can choose not to record a meeting.
• You can tell Era who a speaker is, and make it forget a remembered name.
• You choose who can see each meeting.

Era does this with the AI source you connected; the AI module lets you choose which model handles which kind of work. The person the meeting is with sits on one Customers record. Ask in chat: "Which tasks from last week's meetings are assigned to me and overdue?"

Checklist

1. 01
   Recording notice in the invitation and at the start.
2. 02
   Bot or botless, and participants know.
3. 03
   Summary: decisions, tasks, open questions, next step.
4. 04
   Task owners and dates confirmed before the meeting ends.
5. 05
   Follow-up email read and sent the same day.
6. 06
   Meeting visibility and recording retention decided.