Overview
Let Voiceflow answer calls to an existing RingEX user’s business number. Forward that user’s calls to a separate, callable Voiceflow-connected number, and send callers who need a person to a different RingEX number your team answers.
- Connect the business line while keeping its number with RingEX.
- Receive support calls with the assigned Voice agent and verify the complete forwarded route.
- Make an outbound call through the independently configured Voiceflow caller.
- Transfer callers to a separate teammate line, then maintain or restore the route.
This manual covers RingEX phone-user routing. RingCX queues, IVA configuration and contact-center workflows remain in Contact Centers. The worked setup uses a provider user with a public number, rather than a contact-center queue.
Studio
Prepare the answering agent and number in Agent studio, then configure the user’s forwarding in RingEX. The two systems keep separate routing and release settings.
Code
Configure RingEX user call handling through its authorized API, then use Voiceflow management/runtime APIs for the answering agent and callbacks. Use a Voiceflow management bearer credential for number lookup and agent configuration, and the assigned project’s runtime API key for outbound calling. Keep all credentials on your backend; provider authorization is separate from Voiceflow authorization.
Connecting RingEX
Route an existing business number to a separately tested Voiceflow destination.
Prepare the answering number
Start with a reviewed Voice agent, a test Environment and a callable number already connected to that agent. Voiceflow telephony supplies a number through Voiceflow; the Twilio, Vonage and Telnyx manuals cover existing carrier numbers. Complete the chosen number’s setup first. RingEX stays responsible for its existing business number.
The Northstar example uses three different resources: the business entry number +1 206 555 0111, the Voiceflow answering number +1 415 555 0120, and a teammate’s unforwarded number +1 312 555 0145. Replace them with your actual numbers. The business entry and answering numbers must differ; forwarding the number back to itself creates a loop. Calls use the provider’s PSTN service and the Voiceflow connection’s credits/capacity; check both plans before a customer cutover.
Studio
In Agent studio, open the Voice project’s Phone numbers. Inspect the answering number, open Environment, select the test Environment and Draft, then Save. Call that number directly from a separate phone. Confirm the intended opening and two-way speech before changing RingEX routing.
Code
Use Bash for the curl/jq examples, and PowerShell where a block is labelled PowerShell. Obtain VF_TOKEN with workspace number-list access, the authorized WORKSPACE_ID, the Voice PROJECT_ID and its test ENVIRONMENT alias. Set VF_NUMBER to the already connected answering number in E.164 format. In this dedicated trusted Bash session, stop on failed requests or checks before any later write:
Confirm the alias and version are the controlled test release. Correct them through the number-assignment operation before proceeding. A business number held by RingEX is not this PHONE_NUMBER_ID. Have the builder call the answering number directly and verify its agent before the provider administrator enables forwarding.
Forward the RingEX user’s calls
Use an active RingEX user with a public number and permission to change that user’s call handling. Record the existing Forward all calls destination, its enabled state and schedule before testing. Forward all calls takes precedence over the user’s ordinary work/after-hours rules; calls arriving through a RingEX queue do not become direct user calls. Follow RingCentral’s user call handling for that distinction.
Studio
Have the intended phone user sign in to their RingCentral desktop/web app and confirm the business number on that account. Open Settings → Phone → Call handling → Edit for that signed-in user. Turn on Forward all calls, choose Contact or phone number (under Show more options if needed) and enter the tested Voiceflow answering number. Save, then reopen the setting and confirm its destination and current schedule. RingCentral’s call-handling instructions illustrate these controls.
Use the all-calls override for the controlled test only. For an after-hours route, turn that override off and configure After hours → Missed calls → Forward to external number, including the work-hours schedule. Check an actual call in the intended time window; a saved schedule alone does not test the route.
Code
Obtain a RingCentral production OAuth access token authorized for this user, with app permissions ReadAccounts and EditExtensions and the user’s corresponding read/edit rights. RingCentral’s OAuth setup supplies the authorization flow. Set RC_TOKEN to that token and RC_EXTENSION_ID to the user’s actual extension resource ID, rather than its dialling extension or public number. Use the authenticated user’s ID only when that is the intended line.
Check the call-handling backend before using V2:
Continue with V2 only if this succeeds. For an older backend, have the owner of RC_EXTENSION_ID sign in to their RingCentral app and verify the business number. That target user opens Settings → Phone → Call handling → Edit → Forward all calls → Contact or phone number, enters VF_NUMBER, saves and reads the effective setting back. An administrator managing another extension must not apply this procedure to their own signed-in phone settings. There is no public V1 equivalent of this forward-all rule; do not substitute a private endpoint. See RingCentral’s migration contract.
For V2, retain the rule and state separately:
Prepare the immediate destination from the existing terminating action, retaining its required voicemail target. Stop for administrator review if the expected action/target is absent:
Before editing the destination, disable the saved override while retaining its schedule. An already enabled Forward all calls state would otherwise apply the target change immediately. During this staging interval the user’s ordinary rules apply, so coordinate it with the administrator:
Re-read the rule and verify the selected immediate target before activation:
Activate a daily all-hours test override only after checking that destination:
Confirm the selected target is VF_NUMBER, dispatching.type is Terminate, the state’s enabled is true and its schedule covers now. The API edits user call handling, not a RingCX workflow. Call Handling Configurations owns the target requirements.
An existing RingEX SIP interconnect
Separate a provisioned enterprise interconnect from registering a SIP device.
An administrator may already operate RingEX Cloud Connector and a PBX/SBC route. Assess that provisioned route with the generic SIP setup and network requirements. RingEX SIP phone/SDK registration is a different interface; Voiceflow’s hosted endpoint does not implement SIP REGISTER. This manual’s complete route is PSTN user forwarding, and does not claim a direct RingEX SIP-device connection or RingCX IVA integration.
Inbound calls
Verify the customer reaches the intended agent through the business phone route.
Call the business entry number
Call the RingEX business entry number from a separate phone. Confirm the expected forwarding rule runs and the Voiceflow agent answers without a human acceptance prompt.
Check the conversation
Verify speech in both directions. Ask a question covered by the agent’s approved Knowledge, then one it cannot answer; check that its fallback follows the reviewed instructions.
Match the observed call
Inspect the matching Transcript and the provider’s call history using time and dialled numbers.
Keep these checks separate from the direct answering-number test: a direct call proves the agent route, while a call to the business number additionally tests RingEX forwarding. Test each schedule you enable. The Forward all calls override takes precedence over other user rules; its schedule and enabled flag must both permit the call now.
Forwarding can change the caller identity presented to the answering carrier. Record what actually arrives; a forwarded caller number or user_id is not proof of the original customer’s identity. Use an appropriate verification step before exposing account-specific data. The phone connection does not import Knowledge or customer records; configure those through their existing agent features.
Studio
In Agent studio, compare the saved number assignment with the project’s Transcripts. Publish the reviewed Environment when ready for customer calls, then deliberately set the answering number to Published and repeat a fresh call through the business number.
Code
Read the answering resource after a route change. Its voice.projectID, voice.environmentAlias and voice.version must match the intended release. Use the assignment API or the CLI’s phone-number assign operation to change that route, then read it back. Use call events when your application also needs call outcomes; the provider’s forwarding save is not an answered-call event.
The direct number works but the business line does not
Inspect the provider's effective destination, schedule and acceptance settings.
Check the exact user and public DID, external-forwarding permission, active hours and saved destination. Remove a human acceptance prompt from the selected route, and check whether another device, greeting or voicemail answers first. Keep the direct Voiceflow number test available to isolate the failing leg. For API failures, recheck the RingEX backend feature before choosing V2; a user-forwarding rule does not control calls offered by a queue.
Outbound calls
Place a customer callback through the separately configured Voiceflow caller.
An inbound forwarding rule does not supply RingEX’s number as a Voiceflow outbound caller. In this recipe, a callback originates from the selected Voiceflow-connected number and its underlying carrier. Use that number’s saved Voice agent/release, available credits and production call capacity. If using RingEX’s caller ID is essential, have the phone administrator establish a separately verified outbound interconnect before promising it to customers.
Studio
For a connected Twilio, Vonage or Telnyx number, open Phone numbers → Outbound call API → View and test a separate E.164 phone you can answer. A number provisioned through Voiceflow has no Studio Test call panel: give its answering number, agent/release and controlled recipient to your backend implementer for the request below. Use +1 206 555 0199 only as an illustrative recipient; never test against the forwarded business entry line.
Code
Use PHONE_NUMBER_ID from the answering-number lookup, VF_API_KEY from its assigned Voice project and a separate E.164 TEST_RECIPIENT. The following request disables answering-machine detection for the controlled test:
The empty 201 accepts the request; it supplies no call ID and does not establish that someone answered. The phone calling contract owns exact fields and provider-specific detection/override behavior. Keep the runtime key separate from VF_TOKEN and the RingCentral OAuth token.
Answer the recipient, check the agent’s opening and intended task, and match the outcome to its Transcript/call events. Make an outbound call supplies the shared workflow and recovery checks. Inspect an uncertain attempt before retrying; forwarding does not add an idempotency mechanism or scheduler.
Transferring callers
Send an active caller to a separate number the support team can answer.
Choose a teammate’s public RingEX number that does not forward to the AI. A bare internal extension is not a PSTN destination in this recipe. Confirm your team can answer it directly before enabling the transfer, and keep it different from both the business entry and Voiceflow answering numbers.
Studio
In the Voice agent’s Agent page, open the Call forward system tool and enable it. Choose Phone number, enter the teammate’s E.164 destination and describe when the agent should transfer. Add the same condition to the agent’s instructions. For a fixed branch, use the Workflow’s Call forward step instead.
Publish/assign the reviewed release before customer use. Transfer a phone call covers both Studio entry paths.
Code
Set SUPPORT_DESTINATION to the separate, tested E.164 teammate number. VF_TOKEN also needs agent-read, agent-update and Environment-compile access for this project/release. Retain the tool configuration and explicitly requested instructions before changing them:
Read the agent back with includeInstructions=true to verify callForwardTool and the appended transfer instruction. The PATCH replaces that tool configuration and updates the retained instruction text; keep both previous values for restoration. The Agent API and developer transfer workflow own the complete configuration/compile contract.
Place a call to the business entry number with a teammate waiting at the destination. Ask for a person, confirm the teammate receives the caller and inspect the Transcript. A prototype run or accepted transfer does not establish a human answer. The forwarding leg remains part of the call route; RingEX’s phone-to-phone transfer options do not establish a warm AI transfer or automatic context delivery.
Managing routing
Change the answering release or restore the original phone route deliberately.
Restore RingEX forwarding
Studio
Have the same target phone user return to their Settings → Phone → Call handling → Edit. Restore the recorded Forward all calls destination/state and schedule. If the override was previously off, turn it off so ordinary work/after-hours rules apply again. Call the business number and confirm the original destination answers before retiring the Voiceflow number.
Code
With the V2 route and backups from setup, temporarily disable the override, restore its original rule, then restore its original state/schedule. The rule update takes its saved dispatching object, not the entire GET response:
Re-read both resources and compare them with the backups, then test the restored business route. On an older backend use the complete local app restoration procedure above. Coordinate with the administrator before restoring a snapshot if someone has changed the user’s call handling since it was taken.
Change the answering agent or release
Keep the provider destination stable while changing the answering number’s assignment in Voiceflow. In Studio, select the intended agent/Environment/version and save; in Code, use the number-assignment operation and read the resource back. Publishing alone does not move a number pinned to Draft. Test a fresh call through the business number after the change.
Before deleting, unassigning or replacing the Voiceflow answering number, restore or replace the provider’s forwarding destination and test it. Removing an agent route leaves the provider’s saved forwarding rule in place. Keep credentials for provider call-handling APIs separate from Voiceflow management/runtime keys when rotating access.