- Newest
- Most votes
- Most comments
A workaround for this is to put the call into a queue as a callback. Since Connect callback is agent first, you will always secure the agent first than the requested caller.
Another way is after the bot collected all the info, create a task to be routed, the instruction on the Task is for the agent to call the customer that left all the info.
Actually, my scenario is opposite. We are the callers that start outbound call, we have a responding bot that answers to those question that are asked by some company's bot. So, your solution would work for the company not for us who are starting the outbound call. We have control on the first IVR (or contact flow) not on the second IVR. If you still need more information then please ask.
This is a very interesting use case you are trying to solve for, I wonder what real life use case you would apply this to. We do not have any way to detect "human" voice today to solve for your use case. You can build an integration that leverages a control backplane, but it will be complex and not easy to support operationally.
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Can you please provide the details of actual the use case rather than a solution? An outbound call placed via API will trigger a contact flow as soon as it's answered by the recipient, so if your destination is another Amazon Connect instance flow there will actually be two contact flows executed at the same time. What are you trying to do? Why are you calling another Connect instance? Also, are you using the outbound campaign or simply call the API from a web page or a job/service?
@Magda, the question is updated, If you are still not getting this, please let me know. I think you will get this now easily.