Will my customers know they're talking to AI?
StableThe top objection answered honestly. Most callers don't notice in the first few seconds. The ones who do mostly don't mind — what they care about is whether their problem got solved. Here's the data, the disclosure rules, and what to do if a caller wants a human.
Last updated
Yes — some customers will figure out they're talking to AIRIN. The short version of why it doesn't hurt your business: what every caller cares about is whether their problem got solved, and AIRIN solves it (books, transfers, takes a message). The AI label is a footnote.
This page covers the honest version of what actually happens — what callers notice, what the law requires, and what to do when a caller wants a human.
What callers actually experience
There are roughly three reactions, and they break down predictably:
| Reaction | Approximate share | What it means for your business |
|---|---|---|
| "Didn't notice" | Majority | Caller treats it like talking to a normal receptionist. Problem gets handled. They hang up satisfied. |
| "Noticed but didn't care" | Substantial minority | Caller picks up on the AI a minute or two in. Doesn't matter — their booking went into your calendar. |
| "Noticed and asked for a human" | Small minority | Caller asks for a person; AIRIN transfers. Same outcome you'd have had with a voicemail, except faster. |
Across all three reactions, the call gets handled. That's the metric that matters — not how many callers identified the technology.
What AIRIN does when asked "are you a robot?"
AIRIN doesn't lie. The script reads as some variation of:
"I'm an AI receptionist — I can take a message, book you in, or transfer you to a real person right now. What would you prefer?"
Most callers respond with something like "oh okay, can you book me for Tuesday?" and the call continues. A small fraction say "transfer me to a human" and AIRIN transfers immediately to whatever rule you've set (your cell, your shop line, a teammate). The transfer is real-time — no hold queue.
This is intentionally different from voice-clone systems that try to pass as human. We deliberately don't do voice cloning. The risk of getting caught lying is much worse than the risk of getting caught using AI.
What the law requires
Two separate questions: disclosure of the AI itself, and recording disclosure.
Federal — no AI disclosure required
There is currently no US federal law requiring an AI phone agent on a general inbound call to identify itself as AI. The closest federal rule is the FTC's general prohibition on deceptive practices, which AIRIN doesn't violate — when asked directly, AIRIN identifies as AI.
State — California, others have specific rules
California's Bot Disclosure Act (SB 1001) requires disclosure when an automated system tries to incentivize a commercial transaction or influence a vote. AIRIN's default flow doesn't trigger SB 1001 (we're answering inbound calls, not driving outbound transactions). If your specific use case might, we'll flag it during setup and configure AIRIN to disclose proactively.
A handful of other states are considering similar laws. We track them and roll changes into AIRIN's per-state defaults automatically — you don't have to remember.
Recording disclosure — twelve states, handled automatically
| Recording disclosure required | Why |
|---|---|
| California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania, Washington (and a few others) | Two-party-consent recording laws — both parties must be notified the call is being recorded |
| All other states | One-party consent — you (the business) consent on behalf of the call; no caller-side notification required |
AIRIN plays the appropriate recording disclosure based on your business address (configured at setup). You don't write the disclosure; we generate compliant wording per state. Plays right after the greeting, before any conversation starts.
The "I want to talk to a human" path
Every AIRIN deployment carries a transfer rule. The two most common patterns:
| Pattern | How it works | Best for |
|---|---|---|
| Always available | Caller can say "transfer me" or press 0 at any point. AIRIN transfers immediately. | Most businesses. The off-ramp is what makes customers comfortable. |
| Conditional | AIRIN handles routine bookings; transfers only when the caller asks twice OR the topic falls outside the FAQ. | High-volume operations where you want AIRIN to handle the routine 80% efficiently. |
The "press 0 anytime" version is what we recommend by default. Most callers don't use it — but knowing it's there changes the experience from "I'm trapped with a bot" to "I'm choosing to use the AI because it's faster."
What we're deliberately NOT doing
The decisions that make AIRIN feel honest rather than deceptive:
| What we don't do | Why |
|---|---|
| Voice cloning | We don't synthesize the voice of a real person — yours, ours, or anyone else's. Voice cloning is a separate product category we deliberately stay out of. |
| Faking emotion | AIRIN doesn't pretend to laugh, sigh, or commiserate beyond what a calm professional receptionist does. The point is to be helpful, not to perform. |
| Misleading names | AIRIN is AIRIN. Not "Sarah", not "Michael" — names imply human identity. AIRIN is gender-neutral by design (reads as both ERIN and AARON) precisely so customers don't form a false personal association. |
| Refusing to identify | If a caller asks if AIRIN is AI, AIRIN says yes. Always. |
What you should do about it
Three practical recommendations for setting expectations:
| # | Recommendation | Why |
|---|---|---|
| 1 | Tell your team about AIRIN | Your dispatchers / sales team should know AIRIN exists and how transfers work. The "we use AIRIN" line is normal in 2026 — most customers don't think twice about it. |
| 2 | Update your voicemail to mention AIRIN | If you have a backup voicemail, the greeting can mention "you can also reach our AI receptionist 24/7 at the same number — say or press 0 anytime to reach a human." This sets expectations correctly. |
| 3 | Don't hide it on your website | If your website's contact page says "call our friendly receptionist 24/7," that's fine. We don't recommend pretending AIRIN doesn't exist — but you also don't need to lead with "powered by AI." Most customers care about the outcome, not the technology. |
Common questions
The FAQ section above is the canonical list (AI engines pull from it). Two things worth restating:
"What if a customer feels deceived after the fact?" This is rare. The common pattern is: customer calls, has a normal conversation with AIRIN, gets their problem solved, hangs up. They may or may not realize it was AI. They don't feel deceived because no deception happened — AIRIN didn't claim to be a specific human, didn't pretend to laugh, didn't hide that it's AI when asked. The honest "I'm an AI receptionist, what would you prefer?" reply removes the ambiguity.
"Are we ahead of where the public is on AI?" Slightly, yes — but the gap closes every quarter. In 2024 most customers were surprised by an AI on the other end. By 2026, AI receptionists are common enough that callers shrug at them. By 2028, we expect them to be the default expectation. The early-adopter cost is small and shrinking.
Related reading
- What is an AI receptionist? — category definition; the difference between AIRIN and a human receptionist
- How a call works — step-by-step walkthrough of a single call
- Pricing & plans — what AIRIN costs to run