member badge
Suhana Hamzah
Business problem:
  • As an enterprise customer with existing telephony infrastructure, such as PBX, SIP trunks or another CPaaS provider, I want to connect my own carrier to respond.io’s VoIP channel so I can manage customer calls without being locked into Telnyx or having to port/purchase new numbers
  • Currently, respond.io only supports Telnyx as the VoIP provider. Enterprise and mid-size customers who already have established relationships with other providers, such as Twilio, Vonage or Bandwidth, or existing PBX setups, are blocked from adopting respond.io’s calling feature. This can become a deal-breaker for larger accounts
Desired outcome:
  • Customers should be able to connect their own SIP trunk / carrier to respond.io’s VoIP channel
  • respond.io should support a carrier-agnostic approach for voice calls, so customers are not required to use Telnyx as the only VoIP provider
Use cases:
  • An enterprise customer with an existing Twilio or Vonage SIP trunk wants to manage inbound/outbound calls in respond.io without migrating to Telnyx
  • A corporate customer with existing PBX infrastructure wants to integrate respond.io for customer communication without disrupting their telephony setup
Current workaround:
Not available - customers must use Telnyx as the VoIP provider, which requires purchasing or porting numbers to Telnyx.