BlogSales Stack

Copilot Already Summarizes Our Meetings. So What Does a Sales Meeting Bot Add?

If your team records in Teams and gets a Copilot summary, the honest question is what a dedicated sales notetaker adds. Sometimes the answer is nothing. Here is where a general summary stops, what a sales meeting needs on top of it, how to handle buyers who feel a bot changes the conversation, and what to do about customers whose contracts say no AI.

Oscar Uribe, Co-Founder ·

A sales manager at a large company was polite about it in our first meeting. They record their customer meetings in Teams, Copilot writes a summary, and the summary is fine:

"It's quite similar to Copilot, you get a summary there too."

It's a fair point, and it's one we hear more and more. Another buyer told us that everyone on their team was already happy with their note taker, so meetings simply weren't where it hurt. A sales trainer we spoke with went further, from the vendor side: the biggest threat to every meeting recorder is that Teams does it natively.

So let's take the question seriously, including the answer that is sometimes "you don't need one."

What a general summary is built for

Copilot, Teams, Zoom and Google Meet all produce good summaries now. They are built for the people who were in the room: what was discussed, what was decided, a list of next steps. For an internal project meeting, that is the whole job.

A sales meeting has a different reader. The summary is read by the seller who was there, once, maybe. The thing that actually matters is read later, by other people and other systems: the follow-up that has to happen on Thursday, the colleague who takes over the account in March, the manager wondering why the deal has been quiet for three weeks, the CRM that should know a meeting took place.

A summary tells you what happened. A sales meeting needs something to happen next. That's the gap, and it's why "it's quite similar to Copilot" is true for the summary and not for much else.

The same sales manager put their finger on exactly that, a few minutes later in the same meeting. What landed was not the summary. It was that the things agreed in the meeting became tasks on the customer card, so both sides could see who was doing what.

Five things a sales meeting needs that a summary doesn't do

1. The promise becomes a task with an owner and a date. "I'll send the reference case by Friday" is a line in a summary. In a sales meeting it should be a task, assigned to the person who promised it, due on Friday, with the buyer's own words attached so nobody argues later about what was promised.

2. The meeting knows the history. A general notetaker only knows this meeting. A sales meeting is one step in a longer conversation: the cold call that started it, the email thread, the meeting three weeks ago. A summary that knows the history can say "they raised price again, the same concern as on the first call."

3. The next meeting starts with a brief. The most valuable moment for a meeting record is ten minutes before the next meeting with the same customer: what happened since last time, what we still owe them. A summary in last month's chat thread is not where anyone looks.

4. The record lives on the customer, not in the meeting app. A Teams summary lives with the Teams meeting. When the seller who held the meeting leaves, or the account moves to a colleague, the record has to be on the company and the deal, where the next person will look.

5. The buyer's signals get picked up. Objections, competitors mentioned, who decides and who only influences. These matter to the deal, not to the meeting, and a general summary doesn't hunt for them.

The trainer's point from the start of this post also cuts the other way. The meeting platforms will keep getting better at recording and summarizing, and a vendor whose only product is a summary should worry. What a meeting platform will never have is your prospect lists, your contacts, your call history and your customer records. The value of a sales meeting bot is not the transcript. It's what the transcript gets connected to.

When Copilot is enough

Be honest with yourself about this. If your sellers mostly hold internal meetings, if your sales cycle is one meeting long, or if your follow-up already happens reliably and lives in the CRM, a general summary is probably enough. Paying for a second notetaker to get a second summary is a poor trade.

"The robot changes the meeting"

There's another objection, and it deserves respect. A seller at a technology company told us what bothers them about notetakers:

"When a robot sits in and takes notes, it changes the meeting. It no longer feels like two people talking face to face; it's suddenly something else."

Some buyers feel that too. Others don't notice at all. The head of sales at a manufacturer, asked how it felt to have their meeting recorded, said:

"No, I didn't feel watched at all. It's the same summary you could have written from memory afterwards."

Both reactions are real, and the difference is usually not the bot. It's how it's introduced. Four habits help:

  • Say it at the start, in one sentence. "We record so I don't have to take notes and can actually listen. Is that okay?" Most people say yes, and the ones who don't are glad they were asked.
  • Offer to switch it off, and mean it. If anyone hesitates, take it out without making a point of it.
  • Take it out for the sensitive part. A pricing discussion, a personnel issue, something under NDA. Remove the bot for ten minutes and invite it back.
  • Don't record every meeting by default because you can. First meetings and follow-ups where something is agreed benefit the most. A coffee with a long-standing customer may not.

The same seller who worried about the robot also had a sharp idea about proving its value: switch it off for a while and see how much more tedious it is to take all the notes yourself.

Customers whose contracts say no AI

The hardest version of this question came up last week. Some of a company's customers have confidentiality agreements that say their information may not be processed by AI. The company's AI policy is all or nothing: one person can't make an exception. The fear is buying a tool that can't be used for a share of the customers it was bought for.

There is no clever answer to this, only a careful one:

  1. Find out which customers it applies to. Read the agreements, don't guess. It's often fewer than people fear, and sometimes it covers only certain projects or certain information.
  2. Put the exceptions where every seller will see them. A field or tag on the customer record, not a list in someone's inbox.
  3. Make recording a per-meeting decision for those customers. Turn off automatic joining for the people who handle them, and only send the notetaker when it is clearly allowed.
  4. Check what else touches their information. Meeting recordings are the obvious case. Mail reading and call recording may be covered by the same clause.
  5. Ask the customer. Some clauses were written before anyone used AI notetakers, and a customer may happily agree to recording with data stored in a known place, with no model training on it.

Seven questions before you choose (or keep Copilot)

  1. Who reads the meeting record after the meeting, and where do they look?
  2. Do the promises made in the meeting become tasks with an owner and a date, without anyone typing?
  3. Does anything reach your CRM, and what exactly: tasks, the summary, a link?
  4. Does the analysis know about earlier calls, emails and meetings with the same company?
  5. Is there a brief before the next meeting with the same customer?
  6. Can a seller take the bot out of a meeting halfway through, and bring it back?
  7. Where is the recording stored, who can see it, and is it used to train models?

If you answer the first three with "the seller who was there, in the meeting app, and no," a general summary is doing what it was built for, and your follow-up is still manual.

How we do it

The Funnelfeedr notetaker joins Google Meet, Teams and Zoom meetings, either automatically from your calendar or when you send it to a specific meeting. Everyone in the meeting sees "Funnelfeedr Notetaker" join.

After the meeting, the analysis gives a summary, decisions and next steps, and action items with an owner, a due date and the buyer's verbatim quote. They become tasks, and with Pipedrive or HubSpot connected, they're copied to the CRM as activities with a link back to the meeting. The meeting is linked to the company automatically and to the deal it belongs to. The analysis reads earlier calls, meetings and emails with the same company, and before your next meeting with them, a pre-meeting brief arrives with what has happened since last time and which commitments are still open.

During the meeting, "Remove notetaker" takes the bot out, for example while something confidential is discussed, and you can send it back in. Recording can be switched on or off per meeting, and automatic joining is a setting per user. The notetaker runs on our own infrastructure, so no third-party notetaker service sees your meetings, and per our AI policy your data is never used to train models.

The notetaker is the Meet seat. Objections, competitors, qualification and stakeholders from the same meetings are the Close seat.

What we don't do yet, said plainly: there's no do-not-record setting per customer, so the NDA case above is handled per meeting and per user today. The summary itself is not written to the CRM, only the tasks with a link. And we don't import Teams or Copilot transcripts; the analysis uses our own notetaker.

Want to see what a meeting turns into after the summary: tasks with owners, a brief before the next one, all on the customer? Book a demo and we'll record it, if that's okay with you →

meeting notetaker · AI notetaker · Copilot · Microsoft Teams · meeting summary · follow-up · sales stack · confidentiality · B2B

Every rep, your best rep.

See how Funnelfeedr puts your sales process in the system, in a short demo.