General Settings
Workflow-level settings that apply across every node: dictionary, ambient noise, transcript detail, context compaction, call limits, and external PBX field updates.
An agent's Settings → General page (plus the separate Dictionary section) holds several workflow-wide settings that aren't tied to a specific node.
Dictionary
Add words the agent should actively listen for — company jargon, names, industry terms — as a comma-separated list (e.g. billing department, tretinoin). This improves transcription accuracy for terms your STT provider might otherwise mishear. Depending on your STT provider, using this may incur extra cost.
Ambient Noise
Adds a low background ambience to the call so it sounds less like a synthetic voice in silence and more like a real environment (e.g. an office). Toggle it on, set the Volume (0–1), and optionally upload your own audio file (max 10MB) instead of the default office ambience.
Transcript
Enhanced Timestamped Transcript adds start/stop timestamps for each speaker turn to the uploaded call transcript, e.g.:
[2026-07-06T10:00:00.000Z -> 2026-07-06T10:00:04.800Z] assistant: Can you confirm your date of birth?
[2026-07-06T10:00:06.200Z -> 2026-07-06T10:00:08.700Z] user: January fifth, nineteen ninety.Context Compaction
When enabled, conversation context is automatically summarized on node transitions rather than kept as a full raw transcript in the LLM's context window — useful for long, many-node workflows where context length would otherwise grow unbounded.
Not applicable in Realtime (speech-to-speech) mode — the realtime provider manages its own conversation state, and this setting is ignored there.
Call Management
- Max Call Duration (seconds, default 600) — hard ceiling on how long a single call can run before it's ended automatically.
- Max User Idle Timeout (seconds, default 10) — how long the agent waits for the caller to say something before treating them as idle.
External PBX Field Updates
Only shown when your organization has external PBX integrations enabled. Optionally copy final gathered-context values (from variable extraction) into provider-native fields before a transfer or hangup — for example, writing an extracted qualified value into a PBX-native address3 field so it's visible to the receiving system. Each mapping needs:
- Gathered context field — the extracted-variable name or path (e.g.
qualifiedorextracted_variables.qualified). - Destination field — the PBX-native field name (letters, numbers, and underscores only).
Related
- Interruption Handling — per-node interruption, plus workflow-level Turn Detection and Interruption Strategy tuning.
- Agent Node — where extracted variables (referenced by External PBX Field Updates) come from.