Run Lambda when a caller disconnects
I have a contact flow that transfers customers to an external number. There is a lambda that should execute after the call disconnects. I’m using the transfer to phone number block under terminate/transfer with resume flow enabled. If the agent disconnects first, the flow continues and executes the lambda. If the caller disconnects first, the lambda never executes.
Is it possible to trigger a lambda in the event a user disconnects? The only way I could see looking at documentation is to set up a firehose and responding to contract trace events. Am I overlooking something?
This seems unnecessarily complicated. Adding support for a Caller Hang-Up event in the transfer block seems like a really convenient solve to this problem.
Hi there!
One solution for this requirement would be to utilize EventBridge to monitor for DISCONNECTED contact events, and configure your EventBridge rule to trigger the Lambda.
You can read more around the contact events data model in the administrator guide for Amazon Connect: https://docs.aws.amazon.com/connect/latest/adminguide/contact-events.html#ContactEvent
Relevant questions
Is there an AWS service that can codelessly, serverlessly download an external file via HTTPS to an S3 bucket?
asked 2 months agoCan i execute an Athena saved query from lambda?
Accepted AnswerIssue with Transfer to Phone Number - External Attribute and Lambda
asked 2 years agoMy Lambda function is not getting invoked all of a sudden.
asked 3 months agoRun Lambda when a caller disconnects
Accepted Answerasked 2 months agoSpecify outbound caller ID using Connect Streams?
asked 3 months agosqs event triggers lambda directly, is there a way to delay that execution by 10-20 seconds?
Accepted Answerasked 2 years agohow do i delete a lambda@edge that isn't attached to a cloudfront?
asked 6 months agoTransferring the Amazon connect contact while waiting for the Agent in the Queue
asked a month agoHow do I link my Amazon Connect instance to a Lambda function outside the contact flow with automation
asked 7 days ago
Thank you gthomas. This is exactly what I ended up doing, but you beat me to reporting my solution, thank you very much for taking the time to respond. I had to relate the contactId to a record so I could correlate the disconnect event, but it worked great.