Call Flow and Transcripts

A Call, End to End

Inbound dial

The caller dials a Yaplet-managed number. Telnyx bridges the call to the Yaplet realtime server.

The agent's pre-generated begin message plays within roughly 400 milliseconds. By default the greeting plays in full and the agent only starts listening after — toggle the agent to interruptible if you want callers to be able to barge in earlier.

Conversation

Gemini Live drives turn-taking. The agent listens, responds, calls tools when needed, and stays in its configured language for the whole call.

Inactivity nudge

After roughly 10 seconds of silence from the caller, the agent says a short check-in line ("are you still there?") instead of waiting indefinitely.

Hang-up

If silence continues for another 25 seconds after the nudge, the agent ends the call. Alternatively the caller hangs up.

Wrap-up

The transcript is finalised and written to the inbox alongside (optionally) an MP3 recording.

Total cold-start to first audible word is normally well under one second. Pre-generation of the greeting accounts for most of that — the agent doesn't synthesise the greeting on each call.

Blocking a Caller

Before the greeting plays, Yaplet runs a preflight check on every inbound call. If the caller's phone number matches a blocked visitor record in your organisation, the call is rejected before it's even answered:

The realtime server tells Telnyx to hang up at the call.initiated event — Telnyx never picks up.
There is no ring to your agent, no greeting, no Gemini session.
No per-minute charge accrues because the call was never set up.

To block a specific caller, ban their visitor record from the inbox sidebar or the Security → Visitors page. Blocking is org-wide and applies to every phone number on that visitor record.

You can't block first-time callers in advance. Yaplet only knows about a caller once a visitor record exists for them. After the first call, the block applies on every subsequent call. If you need to block a specific number before any first call, contact support.

What Lives in the Inbox

Every call shows up as a thread under Inbox, tagged as a voice call:

Caller identity — the caller's phone number, plus the name from CNAM where available.
Full transcript — every utterance, labelled by speaker, with timestamps relative to the start of the call.
Recording (optional) — playable / downloadable MP3 if recording was enabled on the agent.

Voice call threads are read-only at the moment. You can listen to the recording, read the transcript, and block the caller, but you cannot reply by chat, email or SMS from the same thread yet. That's on the roadmap.

Recording

When recording is enabled on an agent:

Yaplet does not auto-play a consent disclaimer. If your jurisdiction requires one (two-party-consent states, much of the EU, etc.), add the disclaimer text to the agent's begin message yourself — and consider turning off the interruptible greeting so the disclaimer plays in full before the caller can barge in.
The recording is stored as an MP3 in the call thread, downloadable from the inbox.
The workspace-wide retention cap is 100 recordings by default. Once the cap is reached, the oldest recordings are auto-deleted to make room for new ones. Transcripts are kept indefinitely; only the audio is rotated.

Consent rules vary by country. Two-party-consent jurisdictions require explicit notice before recording. Review the wording with your legal team — Yaplet only provides the recording infrastructure, not the disclosure language.

What to Read Next

Pricing & limits

Per-minute cost, concurrency caps, recording retention details.

Inbox

How the inbox handles every conversation channel — chat, email and now voice.