Salesforce
Hubspot
slack
Shopify
Google Workspace
Microsoft Teams
Twilio
zapierConnect a number or existing phone infrastructure, assign the right agent and validate the route before handling customer traffic.
Talk to salesProvision a local or toll-free number. Give callers a route to the agent. Assign the intended agent and verify the inbound routing configuration.
For a new phone experience.
Connect existing phone infrastructure. Keep established numbers and routing. Connect the trunk to the intended agent and review number and transfer destinations.
For teams with an existing telephony setup.
Use agent logic across supported channels. Keep the experience connected. Adapt instructions and actions for voice timing, text responses, and available channel features.
For phone, web chat and SMS journeys.
Connect calls and outcomes programmatically. Fit the agent into an existing application. Provide the required agent, destination, and task context using the documented fields.
For application-triggered calls and data flows.
Give a dedicated number to the agent.
Connect the agent through the established phone setup.
Initiate supported operations from your own software.
Decide between a new number and existing infrastructure. Verify the requirements for your setup.
Deploy / ConfigurationPREVIEWConnect the tested experience and configure the channel-specific behavior.
Test the full route in a controlled call. Confirm audio, tools and transfers before increasing traffic.
Deploy / ReviewPREVIEWReview your current carrier, number ownership, and routing requirements with the team. The supported connection or migration path depends on your telephony setup; confirm it before planning a cutover.
Start with a limited number, queue, time window, or workflow agreed with operations. Document the fallback destination and test it before sending more traffic to the agent.
Define a fallback such as a staff queue or callback request. Test failures in telephony, authentication, and business APIs separately, including cases where a transfer destination does not answer.
Share expected concurrency, call length, regions, and peak periods. Validate the proposed capacity and any plan or provider limits with the team, then test the expected load before launch.
Assign an operational owner for routing, a technical owner for integrations, and a reviewer for conversation quality. Record how to pause traffic, restore the previous workflow, and communicate incidents.
