Hello team, I am seeing a behaviour which is hampe...
# agents
c
Hello team, I am seeing a behaviour which is hampering my customer experience. here is the case 1. User calls AI number. AI agents joins room and talk. 2. User ask for human assistance. Call gets transferred via call conference. 3. AI session is closed. 4. Process getting killed . But user and Human agent are talking 5. New job request is received with same room name 6. New AI agent session is created and it joins the same room. Now three people are talking.. How to resolve this issue. Please help
l
We have a similar scenario described at https://docs.livekit.io/telephony/features/transfers/warm/, using a separately named consultation room for the human <> human conversation.
c
I am using the same warm transfer mechanism in my setup... i have separate room for supervisor and transfer AI agent for summarisation. after that supervisor is transferred to user room and transfer agent and original agent sessions are closed... after some time agent server receives new request with same job_id and same room name...which creates new AI agent session.. is this a bug? how to resolve this
l
What does your SIP dispatch rule look like? Would you not want to create a new room for each caller? https://docs.livekit.io/telephony/accepting-calls/dispatch-rule/#caller-dispatch-rule-individual-