![]() ![]() however, it can only do this with the first call (and worker) while other calls stack up without a reservation. During the maintenance window, there could be intermittent call disconnects to a subset of Twilio France phone numbers and delays delivering SMS to and from France handsets. I am handling an assignment callback via Flask app, so that is able to handle the reservation and conference it. Our Voice and SMS carrier partner in France is conducting a planned maintenance from at 15:00 PDT until at 16:00 PDT. However, after the user is dequeued by the other person hanging up (in this case, a Twilio Client), the Enqueue action URL is getting 401 Not Authorized responses. I might be overthinking it, but (for example) if 50 calls were in queue, and only one worker - what happens to the 49 calls while the "worker" accepts the reservation? Would I need to create 50 workers? It seems like a bulky workaround, but there has to be a solution by all of you Twilio wiz's out there! This works great - Twilio logs in, sees an Enqueue verb, and remains logged in as it follows the waitURL. ![]() Ideally the final functionality would be that anybody in the queue hears the hold music until they are connected to the call center (which has a significant capacity for concurrent calls). The Enqueue Call Widget requires several pieces of information to function properly. The caller will hear hold music until the call is dequeued by another caller. ![]() (2) I can essentially continually route folk in the queue to the call center until somebody picks up. (1) When a second call goes into the queue, it comes in without a reservation (because my one worker is on the "first" call?) (2) Handle reservations by conferencing with the outbound (cell center) number. (1) Create a flow in Twilio studio (to manage some inputs, etc, as well as enqueue the caller) I'll spare you the logical reason and pitfalls of the current call center, but this is the task at hand. I am building an "overflow" queue of sorts for a call center. ![]()
0 Comments
Leave a Reply. |