Monitor DialNexa Retries Transfers And Audio Cache
Audio Cache Metrics
The call detail Audio Cache tab reads the cache summary stored on the call when available. The summary can include the welcome message. DialNexa checks for a matching pre-generated greeting before it synthesizes a new one. A matching greeting counts as a hit only after the cached audio is ready for that call. If cached audio cannot be used, DialNexa synthesizes the greeting normally and records the outcome as a miss.If Audio Cache was disabled, the UI can still label some numbers as potential cache behavior when data exists. That helps users see whether a repeated script would likely benefit from turning it on.
Why Cache Misses Happen
Transfer Evidence
Transfers should be reviewed as sessions, not just as a transcript moment.Investigate A Special Call
1
Open the original call row
Keep route, agent, batch, workflow, and call id context together.
2
Check retry history
If the call came from a batch, inspect attempts before judging the final recipient outcome. For current-billing workspaces, retry rows can include the charged amount and billed duration for each attempt.
3
Open Transfers
Review session state, representative leg state, bridge behavior, timing, and failure reason.
4
Open Audio Cache
Review cache status, hit rate, lookups, hits, misses, and new cache entries.
5
Fix the owning setting
Change retry rules, transfer configuration, voice setup, or Speech Settings based on evidence.