trx598
01/16/2026, 3:37 PMAI Evy
01/16/2026, 3:37 PMAI Evy
01/16/2026, 3:37 PMboosted_keywords field. This biases the transcriber to recognize those specific words more accurately. [(1) ]() [(2) ]()
javascript
"boosted_keywords": [
"retell",
"kroger"
]
[(1) ]()
You would add common names or specific names relevant to your use case to this array.
2. Change STT Mode to Accurate
Set stt_mode to "accurate" instead of "fast" for better transcription quality. [(1) ]() [(2) ]()
javascript
"stt_mode": "fast"
[(1) ]()
Change this to "accurate" for improved recognition.
3. Adjust Denoising Mode
Try different denoising settings to reduce background interference that may affect transcription. The available options are "noise-cancellation" and "noise-and-background-speech-cancellation". [(3) ]()
4. Prompt Engineering
In your prompt, instruct the agent to ask for spelling confirmation when capturing names, or to repeat back what it heard so the caller can correct it if needed.AI Evy
01/16/2026, 3:37 PMAI Evy
01/16/2026, 3:37 PMtrx598
01/16/2026, 3:42 PMAI Evy
01/16/2026, 3:42 PMAI Evy
01/16/2026, 3:43 PM{{current_time}} variable defaults to the America/Los_Angeles timezone. [(1) ]()
To get the correct date and time for your specific timezone, use the timezone-specific variable format:
{{current_time_[timezone]}}
For example:
- {{current_time_Australia/Sydney}}
- {{current_time_America/New_York}}
- {{current_time_Europe/Rome}}
, [(2) ]() , [(3) ]()
Troubleshooting steps:
1. Specify your timezone explicitly rather than using the default {{current_time}}. [(1) ]() , [(3) ]()
2. Publish your agent after making changes—some users have reported date issues that resolved after publishing. [(4) ]()
3. Use {{current_calendar_[timezone]}} if you need a 14-day calendar view in your specified timezone. [(1) ]() , [(3) ]()
Example usage in your prompt:
Context: current time is {{current_time_America/New_York}}AI Evy
01/16/2026, 3:43 PMAI Evy
01/16/2026, 3:43 PMtrx598
01/16/2026, 3:43 PMtrx598
01/16/2026, 3:44 PMAI Evy
01/16/2026, 3:44 PMAI Evy
01/16/2026, 3:44 PM{{current_time_[timezone]}} variable should be placed in your Global Prompt (global settings) , which sets the context for conversations across all nodes. [(1) ]()
Global settings apply to the entire conversation and help maintain consistency across all nodes.
By adding the current time context in your global prompt like this:
Context: current time is {{current_time_America/New_York}}
...the agent will have access to the correct date/time information throughout the entire conversation flow, regardless of which node it's currently in.
You only need to set it once at the agent level in the global settings, not per-node.AI Evy
01/16/2026, 3:44 PMAI Evy
01/16/2026, 3:44 PMtrx598
01/16/2026, 3:56 PMAI Evy
01/16/2026, 3:56 PMAI Evy
01/16/2026, 3:56 PMcall_started, call_ended, and call_analyzed. If you're seeing duplicates, you may be receiving all three events. [(1) ]() [(4) ]()
How to fix this:
- Ensure your webhook endpoint responds with a 2xx status code within 10 seconds. [(1) ]() [(2) ]()
- Return the response immediately, then process the data asynchronously if needed.
- Check your logs to identify if the issue is timeouts or error responses. [(3) ]()
- If you only need post-call analysis data, filter for the call_analyzed event type in the payload. [(1) ]() [(4) ]()
The webhook payload includes an event field that tells you which event triggered it:AI Evy
01/16/2026, 3:56 PMAI Evy
01/16/2026, 3:56 PM