Twilio Call Flow + livekit + twilio leg hangup
Budget: $250 – $750 USD
I need an expert in Twilio Programmable Voice, Elastic SIP Trunking, and call flow design who can configure my outbound call system to work as follows:
- A = AI system (LiveKit -( Twilio SIP Configured as Outbound Trunk )
- B = Customer
- C = Human Agent
Call Flow:
1. A (AI) initiates an outbound call to B (Customer).
2. The AI interacts briefly with B.
3. When B requests to speak with a human, A transfers the call to C (Human Agent).
4. After initiating the transfer, A disconnects from the call.
Twilio Call Leg Structure:
- The A to B call is logged as the parent call
- The B to C call is logged as the child call. .
Problem:
- The A to B (parent) call ends correctly after the transfer.
- However, the B to C (child) call continues in Twilio’s system and is billed for the entire duration of the conversation between B and C.
- This is happening even though the AI (A) has already disconnected and is no longer part of the call.
Billing Concern:
- We only want to be charged for the AI-to-customer interaction (A to B).
- We do not want to incur any Twilio charges for the B to C (customer to human agent) leg, since that call should be between external parties outside the AI system.
- Currently, Twilio is billing us for both:
- The A to B interaction (which is expected),
- And the full B to C human conversation (which we do not want to be billed for).
If you can resolve this issue and assist with development, we would appreciate the opportunity to discuss it further. Please ping me.
NOTE: WE ALRADY HAVE AI CALLING AGENT BUT WE STUCK IN A TWILIO NOT HANGING UP THE CALLS AFTER TRANSFER AND LETTING CUTOMER AND MY DID ONLY TALK
- A = AI system (LiveKit -( Twilio SIP Configured as Outbound Trunk )
- B = Customer
- C = Human Agent
Call Flow:
1. A (AI) initiates an outbound call to B (Customer).
2. The AI interacts briefly with B.
3. When B requests to speak with a human, A transfers the call to C (Human Agent).
4. After initiating the transfer, A disconnects from the call.
Twilio Call Leg Structure:
- The A to B call is logged as the parent call
- The B to C call is logged as the child call. .
Problem:
- The A to B (parent) call ends correctly after the transfer.
- However, the B to C (child) call continues in Twilio’s system and is billed for the entire duration of the conversation between B and C.
- This is happening even though the AI (A) has already disconnected and is no longer part of the call.
Billing Concern:
- We only want to be charged for the AI-to-customer interaction (A to B).
- We do not want to incur any Twilio charges for the B to C (customer to human agent) leg, since that call should be between external parties outside the AI system.
- Currently, Twilio is billing us for both:
- The A to B interaction (which is expected),
- And the full B to C human conversation (which we do not want to be billed for).
If you can resolve this issue and assist with development, we would appreciate the opportunity to discuss it further. Please ping me.
NOTE: WE ALRADY HAVE AI CALLING AGENT BUT WE STUCK IN A TWILIO NOT HANGING UP THE CALLS AFTER TRANSFER AND LETTING CUTOMER AND MY DID ONLY TALK