Inconsistent "end-of-call-report" responses
# support
m
I am having this massive issue where for some agents when a call ends with "customer-did-not-answer" with no transcript it sends an "end-of-call-report", but for others it does not. Why is this happening? This call log returned a "end-of-call-report": e25d8922-8e84-405d-aa1e-8edfff542746 This call log did not: 0e003ac7-8333-41d9-acaf-5e27ffdd1bf0 Both didn't answer their phones and both didn't go to voicemail, yet they both have different behaviours, why?
c
Hi mm, The discrepancy in "end-of-call-report" behavior could be due to differences in the call configurations or handling logic for different agents. Here are a few possibilities to consider: 1. **Assistant Configuration**: Ensure that both agents have identical configurations regarding the handling of missed calls and end-of-call reporting. Check the assistant or workflow settings to confirm uniformity. 2. **Call Handling Logic**: Review the logic implemented in the server messages or call handling that might trigger different behaviors based on specific conditions or flags. 3. **Call Flow Variations**: Different paths within the call flow might be affecting how these reports are generated. Any custom scripting or API integrations could influence this if set differently between agents. 4. **Telephony Provider**: Sometimes, differences can occur from the telephony provider end if there are additional settings or mismatches in the handling of calls that don't connect. If you need specific insights into the configurations or logs, a closer review of both call logs might help identify the variations leading to different outcomes.
4 Views