Some outbound calls show 'customer-did-not-answer'
# support
k
b471fd10-1d78-400c-9c1e-e1e9e042d57b 87db4da2-cd57-4c04-8e0b-830da6f18d40
k
@kolbykskk, could you please clarify your issue and specify the assistance you require?
k
Yes, it's in the title sorry Some outbound calls show 'customer-did-not-answer' The two call IDs are above
I'm wondering what this means and how to prevent it. It seems to happen at random for us
k
The
customer-did-not-answer
status is triggered when an outbound call is initiated from Vapi to a customer's phone number, but the customer doesn't pick up the call. **Actual No Answer**: The most straightforward case - the customer's phone rings, but they don't answer it. When making an outbound call, if the system waits for the configured time but doesn't receive an answer. Twilio reports 'no-answer' status which we map as an
customer-did-not-answer
for more friendly description.
k
Yeah but it’s happening for inbound calls, such as the call ids I pasted above
k
Hey Kolby, could you please provide me with a inbound call ID that this happened on?
k
b471fd10-1d78-400c-9c1e-e1e9e042d57b 87db4da2-cd57-4c04-8e0b-830da6f18d40
k
Hello Kolby, do you have any call IDs that are under a month old? I'm not able to locate either of those IDs.