voice.aai.dev
Docs · How calls are handled

What happens when your phone rings.

From the first ring to the email in your inbox — the life of one call on a voice.aai.dev line, step by step.

It answers on the first ring

Every call to your line is answered instantly — 2pm on a Tuesday or 2am on a Sunday, first ring, no hold music, no phone tree. The caller hears a warm, natural voice greeting them the way you chose during setup, in their language.

It finds out why they're calling

voice.aai.dev holds a real conversation, not a menu. It can answer the simple questions itself — your hours, your location, what you do — using the information you gave it, and for everything else it asks the questions your setup defines: your intake, in your vocabulary. Callers can interrupt it, ramble, and change direction; it keeps up, because that's what your callers will actually do.

Then one of two things happens

ConnectedIf your rules say this caller should reach a person — an emergency, a VIP, business hours — voice.aai.dev transfers the call to whoever you designated for that situation.
CapturedOtherwise, voice.aai.dev takes a complete message: name and number confirmed aloud, the reason in the caller's own words, and every intake question your setup asks.

Which calls take which path is entirely your call — it's the routing conversation from setup, and you can change it whenever your business changes.

After the call: the email

The moment the call ends, a summary and the full recording are emailed to you — and under zero retention, that email is the only copy anywhere. The details of what it contains, and why deliverability matters, live in the post-call email doc and privacy & retention.

Hear it for yourself

The fastest way to understand voice.aai.dev is to talk to it.

It's on the line right now. Call, ask it anything a customer would — then tell it you'd like voice.aai.dev for your business.

(213) 444-2632