Call Flow and Transcripts

What actually happens on a real voice call — from greeting to hang-up — and where the transcript and recording end up in your inbox. Includes the inactivity timeouts the agent applies on its own and how blocking a known bad caller works before the call is answered.

A Call, End to End

Inbound dial

The caller dials a number you bought through Yaplet, and the call reaches your agent.

Greeting

The fixed AI notice plays first, then the agent's pre-generated greeting, starting about half a second after the call connects. By default the greeting plays in full and the agent only starts listening after — switch on Callers can interrupt the greeting on the agent's page if you want callers to be able to barge in earlier. The AI notice always plays to the end.

Conversation

The agent listens, responds and calls tools when needed. It starts in its configured language and stays in it, and changes language only when the caller clearly asks to continue in another one.

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

A call ends in one of three ways. The caller hangs up. Or the conversation reaches its end — the caller says goodbye, or the agent decides the call is over — and the agent says one farewell and the line drops. Or the silence continues: about 10 seconds after the check-in line the agent says a short goodbye, and the line drops about 5 seconds after that, roughly 25 seconds of silence in total. A fourth, rarer ending: when the caller's daily minutes (see Pricing and Limits) run out mid-call, the agent stops listening, finishes its sentence, says a short goodbye that cannot be talked over, and drops the line.

Wrap-up

The transcript is finalized and, if recording is switched on, an MP3 recording is added to the call's thread in the inbox.

The line always drops. From the moment the agent decides to end the call, the line is dropped within seconds, whether or not the goodbye finished playing.
The first word is normally heard well under a second after the call connects, because the greeting is prepared in advance.

Blocking a Caller

Before the greeting plays, Yaplet checks every inbound call. If the caller's phone profile (see below) is blocked in your organization, the call is rejected before it's even answered:

  • The call is declined before anyone picks up.
  • There is no ring to your agent, no greeting, no AI session.
  • No per-minute charge accrues because the call was never set up.

To block a specific caller, ban the visitor of the call's thread — the caller's phone profile — from the inbox sidebar, or from Audience → Security → Visitors (Security is one page with tabs across the top). Banning a website visitor whose profile merely shows the same phone number does not block calls from that number. Blocking is org-wide: a block on the caller's phone profile covers calls to all your numbers and brands.

Separately from manual blocks, callers over their daily usage limit (minutes or calls per phone number, set on Brand → Brand settings → Usage limits) are declined at this same check, automatically — those calls show as Declined — daily limit in the agent's call list.

You can't block first-time callers in advance. Yaplet only knows about a caller once their phone profile exists, and the first call creates it. 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 caller has their own phone profile, and each phone profile has one thread in the Inbox, tagged as a voice call (Inbox → Calls lists only calls). The first call from a number creates the profile and opens the thread when the call starts; every later call from that number joins the same profile and the same thread. The thread fills in line by line while the call is going on. (A test call made with Talk to it leaves no thread here: it shows only in the agent's Calls list, marked Test.)

  • Caller identity — the caller's phone number, plus the name from CNAM where available.
  • Full transcript — every utterance from both sides, the caller's and the agent's, labeled by speaker with timestamps relative to the start of the call.
  • Recording (optional) — playable / downloadable MP3 if recording was enabled on the agent.
  • Which inbox it lands in — the call is filed against the chat widget belonging to the agent's brand. That is what decides which team members can see it (access is granted per brand) and which widget filter it appears under.
A call never joins a website visitor. A website visitor who merely has the same phone number on their profile — for example one your website passed in with identify() — keeps a separate profile and is never given the call or its transcript. Anyone can type any number into a website, so a number on a website profile does not connect it to phone calls.
Voice call threads are read-only. The message box is replaced by a recording player, so you cannot reply in the thread by chat, email or SMS. The thread's side panel still works — you can edit the visitor, email them and block them from there.
Masking of the stored transcript is a brand setting. When Brand → Brand settings → Advanced → Privacy masking is on, email addresses, phone numbers and card numbers are stripped out of the call's inbox messages as they are written and out of the saved transcript shortly after the call ends.

Recording

When recording is enabled on an agent:

  • Yaplet auto-plays the fixed AI notice at the start of every call, but not a recording-consent line — consent to record is a separate requirement. If your jurisdiction requires one (two-party-consent states, much of the EU, etc.), add the consent wording to the agent's Greeting yourself — and keep Callers can interrupt the greeting switched off (its default) so the wording 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 organization-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.

Pricing & limits

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

Inbox

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

© 2026 Yaplet. All rights reserved.