- Le plus récent
- Le plus de votes
- La plupart des commentaires
The delay you're experiencing when using the AnsweringMachineDetectionConfig
with EnableAnswerMachineDetection: true
is likely due to Amazon Connect's mechanism for detecting whether a human or an answering machine has answered the call. This mechanism involves waiting for a brief period of silence before playing the prompt, as answering machines typically have a few seconds of silence after answering before the recorded greeting starts.
Unfortunately, there is no direct way to eliminate this delay when a human answers the call.
Possible Solution: One effective approach is to begin your contact flow with a brief greeting or a short sound clip before diving into the main message. This way, when a human answers, they hear something right away, which can reduce the likelihood of them hanging up during any detection delay.
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
Thank you for your answer. Unfortunately the solution of playing a brief greeting or sound before the main message also does not work as I have already tried it. I added a "Play Prompt" block as the very first block of the contact flow (immediately after "Entry"). However, it seems like the delay is introduced by the API call itself before it even gets to the contact flow execution. The Play Prompt greeting also only plays after the same delay of about 5-6 seconds. What that indicates to me is that the contact flow only begins after the delay.