Hey folks, We’re running into an issue while handling inbound calls using a transient assistant setup via the

assistant-request

flow. What’s happening: - After the call connects, our server receives the assistant-request and responds immediately with the assistant config. - But there’s a 4–5 second delay after our response before the assistant starts speaking to the caller. - During this delay, we’re seeing a noticeable increase in call drops, likely because the user hears silence and assumes the call isn’t working. Why it’s a problem: - That short gap before the assistant responds is creating a poor user experience. - It’s directly affecting production call performance — too many callers are hanging up before interaction begins. What I'm looking for: Suggestions to reduce or hide the perceived latency after assistant-request. Any workarounds like: - Playing a set message or background tone/music while the assistant initializes. - Keeping the phone ringing until the assistant is ready. - Preloading or caching the assistant setup somehow to reduce delay. Has anyone else encountered this? Any advice, hacks, or fixes would be super helpful.

Hey Amin Rane, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!