Set two rules before your AI notetaker drafts client follow-ups

Consent comes before recording

A client call ends, and a draft follow-up is already waiting. For a small founding team, that speed is tempting, but it is a liability if nobody decided who could be recorded, who can see the notes, and where the action items go.

OpenAI made the ChatGPT Meetings plugin available at DevDay on September 29, 2026, initially as a macOS beta for Pro and Business subscribers. It records calls through the Mac microphone and system audio, so it does not appear as an extra participant in the meeting. That invisibility is the problem: the meeting feels ordinary, but a machine is building a record.

OpenAI places the consent responsibility on the user of the Meetings plugin, telling them to notify everyone and obtain consent before starting, while the on-screen reminder does not notify other participants. The consent rule is simple: the team decides which meetings the notetaker may cover, and the host says so out loud.

A small team meeting ritual can be different from a client call. For internal planning, the team can agree that the notetaker is always on. For client work, the host must say the consent line. The client hears the consent line before the record begins.

Name where action items land

The plugin writes its notes and summaries to a ChatGPT Page. A page is fine for a transcript, but it is not a system of record. If the follow-up email, the project plan, and the CRM all need the same facts, they need a named place to receive them.

The plugin proposes next steps, including an email draft or a project-plan update, and lets the user begin either action with a single click. That is useful, but it is dangerous if the team has not named where the action items land before the call begins.

For a small founding team, the destination rule is: every meeting has a named action-item destination. It can be a shared doc, a task board, a CRM field, or a weekly standup notes file. The notetaker feeds it; the team owns it.

If the action item is a follow-up email from meeting notes, the destination is the email draft. If it is a project plan from meeting notes, the destination is the plan. The next owner can find the task without asking who wrote the notes.

Keep the first sprint on human sign-off

Use this list before the first client call. Each item should be quick to check.

• Write down which meeting types the notetaker may cover, and mark client calls as opt-in.
• Put the consent line in the calendar invite or the opening sentence of the call.
• Name the action-item destination before the call starts, not after.
• Assign a human owner to approve every draft before it is sent.
• After the call, confirm the notes and action items reached the named destination.

The consent line should be plain: We are recording this call for internal notes. If you object, tell me now. That sentence does the work. It gives the client a chance to stop the record before it exists.

The destination rule should be boring. If the team uses a project plan, action items go there. If it uses a shared doc, action items go there. The notetaker can draft, but the named tool is where the team checks the work.

For the first sprint, human sign-off is mandatory. The founder or ops lead reads the draft, checks the names, dates, and commitments. If the destination is a project plan, the action item should carry an owner and a date before approval. If the destination is a shared doc, the same check applies. No one should let a machine send the first client follow-up on its own.

If a client objects, stop the notetaker and send a short host recap.