Wrong Call Ended Reason – "customer-ended-call-aft...
# support
g
I am noticing many calls with "customer-ended-call-after-warm-transfer-attempt" as the call ended reason. The most recent one was an attempted transfer where the destination didn't answer the call. The conversation continued and the call was never transferred again. Somwhow, the reason is still "customer-ended-call-after-warm-transfer-attempt".
c
Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!
g
I think this is a new feature. Not a bug. Marked as solved. Is there one that specifies "during" warm call transfer attempt so I know if they disconnect in the middle of the transfer?
c
There is currently not that call status but if you would like to see that on our platform, feel free to add it to the feature request list here -->
2 Views