Skip to main content
Question

Warm transfer failing between third-party AI voice platform (Twilio) and RingCentral call queue

  • July 23, 2026
  • 0 replies
  • 3 views

RJWreckCheck

We have a third-party AI receptionist platform built on Twilio called SimpleTalkAI that needs to warm-transfer calls into a RingCentral call queue. The transfer connection is unreliable/dropping delays in conversations.

Setup:

  • Inbound number: [Twilio number, e.g., 770-637-6424]
  • Destination: RingCentral call queue (770-675-1828)
  • Transfer method: [SIP refer? REST API call transfer? Attended transfer via API?]

This has been open with standard RingCentral support as case #31923806 without resolution. Looking for guidance on:

  1. Whether RingCentral's call queue supports SIP REFER-based warm transfers from external SIP trunks/Twilio
  2. Any known limitations on transferring into a queue vs. a direct extension
  3. Recommended API/webhook approach for reliable warm transfer performance between Twilio and RingCentral