Once you're in — yes. Text or call anytime. Access itself is application-reviewed, not self-serve overnight.

Will my manager see what I tell Sara?

No. Sara reports to you. Nothing goes up the org chart unless you choose to share it.

Does she record my customer calls?

Never. No bot in the meeting. You reach out after — by text or call.

How is this different from Gong or Chorus?

Gong owns the recorded call — for your manager. Sara owns what happens after you hang up — for you.

Why do customers ask if a sales call is being recorded?

Because they've been on calls where the honest answer was uncomfortable — a tool logging the conversation for someone who isn't in the room. The question is rarely about the technology. It's a check for whether the rep is going to be straight with them.

Does using AI on a sales call hurt customer trust?

Not on its own. What hurts trust is a vague or defensive answer to a direct question. A rep who can say exactly what a tool does and doesn't do, without hedging, comes across as more trustworthy than one with no tool at all and a nervous answer.

What should a rep actually say when a customer asks about AI on the call?

The specific truth, in one sentence. Not being recorded, not being sent to a manager, not stored as a transcript — whatever is actually true. Customers can tell the difference between a rehearsed reassurance and a plain fact, and only one of them holds up if they ask a follow-up question.

PILLAR

Customer AI Trust: What to Say When They Ask If This Is Being Recorded

Customers don't distrust AI on a sales call because it's there. They distrust it because the answer to 'is this recorded?' is usually vague. The honest one works better.

2026-08-15 · SARA — KEEL'S AI DEAL ASSISTANT · GETKEEL.IO

Two silhouetted figures across a small table in a glass-walled room, a single ember-orange dot glowing on a device between them.

"Is this being recorded?"

The question lands mid-sentence, usually right after something the customer actually cares about. A pricing concern. A real objection.

What happens in the next five seconds decides more than the rep realizes.

The question isn't about the technology

Customers aren't asking for a technical explanation. They're asking whether they can keep talking freely.

A hedge — "it's just for internal notes," said while looking away — answers a different question than the one they asked. It tells them something is happening that the rep would rather not detail.

That reads as evasion, even when nothing improper is going on. The customer stops volunteering the thing they were about to say.

Vague answers cost more than honest ones

The instinct is to minimize. Downplay the tool, wave off the question, move back to the pitch.

It backfires because minimizing implies there's something to minimize. We've written before about what a recording actually is once it exists: an artifact that outlives the conversation, sits on a server the customer never sees, and can be pulled up by someone who wasn't in the room.

A customer who senses that — even without naming it — reacts to the vagueness, not the AI.

What actually earns the trust back

The fix isn't a longer disclosure. It's a shorter, truer one.

Say exactly what the tool does. Say exactly what it doesn't do. Stop talking.

"It's a note for me, not a recording — nobody else sees it, and it's not saved as a call transcript." That's a full answer. It's specific enough to check, and specificity is what a vague answer can never fake.

Why the honest version is easier to defend

A rep who's vague has to remember the vague story and keep it consistent across every follow-up question.

A rep telling the truth doesn't have that problem. There's only one version of what's actually happening, and it doesn't change no matter how the customer probes it.

That's the real advantage of a tool built not to record in the first place: there's nothing to explain away later, because there's nothing sitting on a server that contradicts what the rep said in the room.

The states where this isn't optional

In two-party consent states, this stops being a trust question and becomes a legal one — the rules vary enough by state that "everyone does it" isn't a defense.

Even outside those states, treating disclosure as optional trains reps to hedge by default. The hedge is the habit that actually costs deals.

Build the answer before the question comes

The reps who handle this well aren't more honest by nature. They decided the answer in advance, so nothing has to be improvised under a customer's direct gaze.

Know what's true. Say it plainly.

Sara doesn't record, transcribe, or store customer conversations — the rep's own account afterward is the whole record. That's what makes the honest answer to "is this being recorded" the reassuring one, not the risky one.

Founders Club is invite-reviewed. Apply at getkeel.io/founders.

Trust is the answer, not the apology

Customers don't need a rep to apologize for using a tool. They need one who isn't afraid to say what it is.

The AI on the call was never the trust problem. The unwillingness to describe it plainly always was.

By the team at Keel. We're building Sara, an AI deal assistant for the moments that don't get recorded.