Consent first: how Jefferson asks every participant before recording

Meeting notes are one of the most practical things an assistant can help an insurance team with. Calls with colleagues, reviews of a renewal, a walkthrough of a new process: they all produce decisions and follow-ups that are easy to lose. A note-taker that captures them is genuinely useful.

But a note-taker only works if the people in the room are comfortable with it being there. In insurance that comfort matters more than usual. Conversations can touch on clients, policies and details that people reasonably expect to stay contained. So when we designed how Jefferson takes notes in meetings, we started from a simple position: consent comes first, and recording is something people are asked about, not something that happens to them.

This post walks through the four design choices that follow from that position.

Every participant is asked

The first choice is the most direct one. Jefferson asks each participant about recording.

Not just the person who set up the meeting. Not just the first person to join. Each participant.

It would be simpler to treat the organiser's decision as covering everyone. Plenty of tools work that way. But the organiser saying yes is not the same thing as everyone in the meeting saying yes. Someone who joins late, someone from a different team, someone who simply did not expect a recording: each of them gets the question too.

In practice this means nobody finds out halfway through a conversation that it has been recorded. The question is part of joining, and it is put to the person it affects.

The second choice is that the consent notice is part of Jefferson itself, rather than something a team has to remember to add.

When consent depends on someone remembering to say "just so you know, this is being recorded" at the start of a call, it works most of the time. Then one day the meeting starts in a rush, the person who usually says it is not there, and it does not get said.

Building the notice in removes that gap. The notice is there because the product puts it there, not because someone remembered. That makes it consistent from one meeting to the next, and it means the team does not carry the burden of getting it right every time.

Rooms can be limited to your organisation

The third choice is about who can be in the room at all. Jefferson meeting rooms can be limited to the organisation only.

Not every meeting needs this. Some conversations are meant to include people from outside. But many internal meetings are exactly that: internal. A team stand-up, a review of a difficult account, a discussion of how to handle a claim. For those, being able to restrict the room to people in your own organisation is a straightforward way to keep the conversation where it belongs.

This is a setting, not a rule imposed on every meeting. The point is that the option exists, so a team can match the room to the conversation it is about to have.

Recordings are kept on InsurEco servers

The fourth choice is about what happens after the meeting. Recordings are kept on InsurEco servers.

When a team asks where its recordings go, the answer should be short and clear. Here it is: they are kept on servers run by InsurEco, the company behind Jefferson. That gives a single, plain answer to one of the first questions people ask about any recording tool.

We are deliberately not dressing this up. It is a statement of where recordings live, and it is the kind of detail that should be easy to find and easy to understand.

How the pieces fit together

Each of these choices is modest on its own. Together they cover the questions people tend to have about a note-taker, in roughly the order they have them:

Am I being recorded? You are asked, individually.
Was I told? The consent notice is built in, so yes, every time.
Who else is here? The room can be limited to your organisation.
Where does the recording go? It is kept on InsurEco servers.

Picture a small agency team holding its weekly internal review. The organiser sets the room to organisation only, since the conversation is about live accounts. As each colleague joins, they are asked about recording, and the consent notice is there without anyone having to read out a disclaimer. Afterwards, the recording sits on InsurEco servers. Nobody had to remember a checklist; the defaults did the work.

Why we chose this trade-off

Asking every participant adds a step. A built-in notice is one more thing on screen. Restricting a room means thinking for a moment about who should be in it. None of these are frictionless.

We think that small amount of friction is worth it. Trust in a tool like this is built slowly and lost quickly. A single meeting where someone feels they were recorded without being asked can undo a lot of goodwill, both for the tool and for the team that uses it. Making consent part of the design, rather than part of a policy document, is how we try to avoid that.

It also reflects how we think about Jefferson more broadly. It is an assistant for insurance teams, and insurance teams already work with a strong sense of what is appropriate to share and with whom. A note-taker should fit that sense, not work around it.

In short

Jefferson's note-taking is built around consent:

Each participant is asked about recording.
A consent notice is built in.
Rooms can be limited to the organisation only.
Recordings are kept on InsurEco servers.

The aim is simple: useful notes from your meetings, without anyone wondering whether they agreed to be part of them.