Skip to main content

Recording and call control

The Call card

Recording and call control live in one card of the agent settings, Call. The card is always open. Each row shows its current value in short, and the details are behind a gear. How changes are saved. The switches, the Ring duration field and the Action on detection choice write to the draft at once. A gear or the pencil opens its own window with a copy of the values: Save writes them to the draft, Cancel drops the edits. A dot on the gear means a value behind it differs from the default. These settings are versioned with the agent, so Draft and Published versions can have different values.

Recording

The Call recording switch turns voice call recording on for telephony and browser tests. Recordings are stored as MP3 files and contain the agent and caller audio. The gear Recording parameters:
  • Channels: Stereo — stores the agent and caller on separate audio channels, making it easier to distinguish the speakers.
  • Channels: Mono — stores both sides of the call in one mixed audio track.
  • Audio retention: Keep forever — keeps recordings without an automatic deletion date.
  • Audio retention: Delete after N days — deletes recordings after the retention period.
  • Retention period — how many days recordings remain available when deletion after N days is selected: a slider from 1 to 365 days and a number field.
The Recording parameters gear: channels and retention period Call recording is regulated by law. The party operating the call is responsible for notifying participants, for example with an announcement at the beginning of the call.

Call control

The other rows of the card manage call timers and silence behavior. Max call duration. The gear Max call duration and closing phrase:
  • Limit or No limit — enforce a maximum duration or leave the call duration unrestricted.
  • Cap — the maximum call duration in seconds when Limit is selected: a slider from 60 to 7200 seconds in steps of a minute, and a number field.
  • Closing phrase (optional) — the phrase spoken when the duration limit is reached, such as a short apology and goodbye.
No limit means “no limit of yours”, not “no limit at all”. A platform-side session ceiling applies on top: a conversation longer than the ceiling is force-closed together with its telephony room, even if participants are still on the line. The default ceiling is 4 hours (the value is configured at the platform level). It exists so a stuck session cannot live in the history for days and skew reports; if your scenario needs multi-hour conversations, raise it in advance.
Ring duration — how many seconds an outbound call can ring before it is canceled as No answer. This value can be overridden for an individual call. When the caller is silent. One gear, Silence: reminders and end of call, holds both parts; its Save writes them together.
  • Reminders — a switch that turns on reminders when the caller stops speaking. Under it:
    • First after — how many seconds of silence trigger the first reminder;
    • Then every — the delay between subsequent reminders, in seconds;
    • Up to — how many reminders can be sent;
    • Message type — Text for a fixed reminder or Prompt to let the language model generate the line;
    • Reminder message — the reminder text. When empty, the agent uses the built-in “Are you still there?” message in the current call language.
  • End the call — a switch that ends the call after a period of silence. Under it, Silence timeout: a slider from 5 to 120 seconds and a number field.
The Call card: rows with summaries, gears and switches, the answering machine and call screen handling When silence handling is enabled, reminders are sent first up to the configured maximum. The call then ends when the silence threshold or reminder limit is reached, whichever comes first. Any caller speech resets the timers and the counter. The duration cap is applied independently. Transfer failure message — the line to say when a transfer fails and the flow has nothing to say. The pencil opens the editor: Text with the Text (variables allowed) field, or Prompt with the Instruction for the agent field. An empty field means a silent ending: the caller listens to dead air until they hang up. After the line the call ends; bringing the conversation back into the flow is the job of the transfer node’s failure routes. Farewell on platform shutdown and No media detection are not in this card. They are in Additional → Operations.

No media detection

Sometimes an outbound call is answered, but no sound comes from the callee’s side at all — the carrier sends no audio. Ending such a call like a call with a silent callee would skew the share of failed connections in reports. The No media detection switch is in Additional → Operations and is on by default. With it, an answered outbound phone call where not a single sound came from the callee’s side for the whole call gets the outcome No media from callee (RTP). The first second after the answer is not counted, and at least 5 seconds of audio must be measured; a shorter call gets no such label.
  • It is a label, not an early hang-up. The call goes on as usual: the agent talks, sends reminders and ends the call by its usual rules. Only the outcome in the history changes.
  • It replaces only ordinary endings: by silence, by the duration cap, or a normal end. Voicemail and transfers never get this label.
Turn it off for carriers that send no audio while the callee is silent. On such a line a callee who stays silent until the end of the call gets the No media label by mistake instead of a silent-callee outcome. The call itself is not affected — only the report.

Outbound SIP headers

The Outbound SIP headers card in Additional → Operations adds the agent’s own headers to the INVITE of every outbound call of this agent — for example, to pass a client id to the carrier or to the customer’s PBX. Inbound calls are not affected.
  • Pairs “name → value”, up to 50. A name is a token of Latin letters, digits and hyphens that starts with a letter, such as X-Customer-ID — the same rule as for the SIP headers of the transfer node.
  • A value is text and/or call variables, such as {{customer_id}}: the agent’s default values, the values a campaign or the Web API passes, the results of pre-dial functions and the call’s own data such as the dialed number. Environment secrets {{env.*}} are never expanded here.
  • A header is not sent if its variable has no value, the value is empty or contains a control character. The call is dialed anyway.
  • If the trunk subgroup sets a header with the same name, the subgroup’s value is sent.
  • Every header that was not sent as configured shows up in the call details as an Outbound SIP headers event — with the header names, without their values. This works for calls that never connected too.
The headers are versioned with the agent, like the other settings.

Answering machine detection (AMD)

The Detect answering machines row decides who answered a call — a live person or a voicemail — and what the agent does with an answering machine. It works on outbound calls, and on inbound calls by the Detect on inbound calls too toggle in AMD parameters. While the switch is on, Action on detection is chosen right under the row, and the gear opens AMD parameters. How detection works, which checks to turn on, what happens after the decision and where to see the result is on its own page, Answering machine detection. The Call screen handling row below it teaches the agent to tell a call screening assistant and a key-press menu from a person and a voicemail. See Call screeners.

Pause on client request

A caller who says “hold on” or “one moment” needs time — to find a document, to step away from a noisy room — and an agent that answers such a request with a full reply, or starts reminding them after a few seconds of silence, sounds like it was not listening. With Pause on client request on, an explicit request to wait — a short one or one with an explanation — makes the agent skip its turn and send no reminders for the pause window. The switch is in the row; the gear Pause window and phrases holds the rest:
  • Pause window — how long the agent waits, in seconds: a slider from 10 to 300 and a number field. A repeated request extends the window; a substantive reply from the caller ends it.
  • Trigger phrases — the phrases that count as a request to wait. Empty means the default phrases in all agent languages.
  • Ask the model when the request comes with an explanation — on by default. What it does is below.
  • Briefly acknowledge the request — off by default: the agent stays silent during the pause. On, it first replies with a short line such as “Sure, take your time” and then waits.
  • Acknowledgement phrases — appears under the previous switch; one phrase per line, the agent takes them in turn. Empty means the default phrases in the current call language.
A short request is recognised by the platform itself, a request with an explanation — with the help of a model. A trigger phrase with nothing else in it turns the pause on at once, without a model call; in Russian this also works with hesitations such as «эээ», «щас» or «так» around the request. If the request comes with an explanation — “hold on, I’m opening the app” — the agent’s fast classifier model decides. The pause turns on only when the model answers with confidence that it is a request to wait; on any other answer, on an error, or if the model has not answered within 1 second, the agent replies as usual. The check adds up to 1 s to such turns only. With the switch off, utterances with an explanation take an ordinary turn, without the model. The request works over the agent’s own speech. If the caller asks to wait while the agent is talking, the agent stops right away, however few words the request has — the minimum word count for an interruption does not apply to it. Two or three requests in a row are each recognised, and a longer trigger phrase is matched before a shorter one it contains. The request stays in the transcript. It is kept as a caller utterance with the asked to wait label in the call details: there was no turn for it, the agent paused. In the transcript column of a report such a line ends with [asked to wait].