Connect customer calls through a Voiceflow number, Voiceflow’s hosted SIP endpoint or your existing phone provider. Keep a RingEX, Zoom Phone or Teams Phone user number with its provider and forward calls to an independently configured Voiceflow number. Use a Voice agent for calls. Text conversations and notifications have their own connection and verification under SMS.
In Agent studio, open the project’s Phone numbers for calls. Provider manuals include the required Studio setup and programmatic calling path.
Choose your connection
For independent SIP call directions or multiple outbound gateways, choose Bring your own SIP. SIP connections keep the public numbers with your phone system; they do not acquire a new number.
Guides
- Connect and route phone numbers — connect the number and verify its agent, Environment and version.
- Make an outbound call — prepare the agent and caller connection, call a separate destination, and verify the answered conversation.
- Transfer a phone caller to a human — configure a separate support destination and verify the handoff.
- Troubleshoot SIP calls — distinguish authentication, routing, media and destination failures.
For incoming routing and caller behavior, see Inbound calling. Text follow-ups and SMS conversations are listed under SMS guides.
Installation guides
Use Connect and route phone numbers to verify the assigned agent, Environment and released route across number providers. Voiceflow numbers use the API for outbound calls; their Studio outbound-test panel is unavailable. The current SMS conversation path uses Twilio with a Chat agent. Provider messaging APIs send notifications separately from that channel.
For forwarded business lines, callbacks use the separately configured Voiceflow caller; forwarding does not automatically supply the business system’s original caller ID. RingCX, Zoom Contact Center and other contact-center routing retain their Contact Centers manuals.
Build the customer journey
- Answer support questions: build and test a phone support agent, connect approved Knowledge and verify its answers through an actual call. Phone-provider setup does not import support content.
- Call a customer: follow Make an outbound call for the complete workflow. Use the pickup-reminder example to build a reminder agent and the backend calling guide for an application trigger. The calling endpoint does not create a campaign scheduler.
- Reach your support team: follow Transfer a phone call and the provider’s transfer requirements. Provider-specific queues, authentication and mapping belong in Contact Centers.
Runtime and network references
Voice agents owns call lifecycle, audio and recovery contracts. Exact phone calling, SIP outbound calls, SIP network settings and SMS behavior remain with their existing references.
For an SMS action without a text conversation, use Twilio Send SMS or the Vonage and Telnyx notification recipes.