Speech recognition resources control how the agent processes user speech input on the voice channel.
These resources live undervoice/speech_recognition/ and are used to tune how the agent listens, recognizes, and post-processes spoken input.
ASR settings are platform-provisioned — update onlyASR settings are created automatically when a project is created. They can be updated with
poly push but not created from scratch. See the equivalent note on agent settings for details.Location
asr_settings.yaml is the core settings file; the others are optional.
What speech recognition controls
ASR settings
Configure global speech-recognition behavior such as barge-in and latency/accuracy style.
Keyphrase boosting
Bias recognition toward specific words or phrases.
Transcript corrections
Apply regex-based corrections after speech recognition.
ASR settings
ASR settings are defined in:Fields
| Field | Type | Description |
|---|---|---|
barge_in | bool | Whether the user can interrupt the agent while it is speaking. Default: false. |
interaction_style | string | Controls the latency/accuracy trade-off. Default: balanced. |
Example
Interaction styles
| Style | Behavior |
|---|---|
precise | Higher accuracy, higher latency |
balanced | Default balance of speed and accuracy |
swift | Faster responses, slightly lower accuracy |
sonic / turbo | Lowest latency |
Keyphrase boosting
Keyphrase boosting is defined in:- brand names
- product names
- specialist terminology
- domain-specific jargon
Structure
Akeyphrases list where each entry includes:
| Field | Required | Description |
|---|---|---|
keyphrase | Yes | The word or phrase to boost |
level | No | Boost strength: default, boosted, or maximum |
Example
Transcript corrections
Transcript corrections are defined in:- email domains
- repeated digits
- domain-specific phrases
- spoken forms that should be normalized into machine-friendly text
Structure
Acorrections list where each entry includes:
| Field | Required | Description |
|---|---|---|
name | Yes | Identifier for the correction group |
description | No | Explains what the correction fixes |
regular_expressions | Yes | Regex rules used for correction |
| Field | Required | Description |
|---|---|---|
regular_expression | Yes | Pattern to match |
replacement | Yes | Replacement text |
replacement_type | No | full or partial / substring |
Example
Best practices
- use
keyphrase_boostingfor terms the recognizer is likely to miss - keep boosted keyphrases focused and specific
- use transcript corrections for common, repeated recognition errors
- avoid overly broad regex rules that may alter normal input unexpectedly
- choose the ASR interaction style deliberately based on latency and accuracy needs
Related pages
Voice settings
See how speech recognition fits into the wider voice-channel configuration.
Response control
Configure what happens to output before it is spoken.

