Skip to main content

Routing & telephony

Bring your owncarrier.

Don't want to switch telephony providers? Wire Finn into your existing Twilio, Plivo, or any SIP trunk. Same observability, same workflow.

Book a demo

30-minute free trial. No card. No procurement.

Twilio + PlivoFirst-class
Any SIP trunkGeneric support
Same dashboardBYOC + native
No lock-inSwitch anytime

How it works

Wire once.Use everywhere.

Drag, wire, deploy. Each step is reversible — every save creates a versioned snapshot.

01 / 03

Connect your provider

Twilio, Plivo — paste credentials, point your numbers at Finn's SIP endpoint. ~10 minutes setup.

SettingsIntegrations
Browse all

Connected

6

Available

100+

Salesforce logo
Salesforcelinked
HubSpot logo
HubSpotlinked
Zendesk logo
Zendesklinked
Twilio logo
Twiliolinked
Razorpay logo
Razorpaylinked
Calendly logo
Calendlylinked
Slack logo
Slack
Shopify logo
Shopify
Plivo logo
Plivo
Zoho logo
Zoho
Notion logo
Notion
Intercom logo
Intercom
02 / 03

Map numbers to workflows

Per-number routing to a Finn workflow. Mix BYOC numbers + Finn-provided numbers in the same account.

Healthcare ReceptionistWorkflow editorDraft
Deploy
Greet callersay
Capture intentcapture
Booking branchbranch
Calendar.book()function
Transfer to agenttransfer
5 nodes · 4 connections · 2 variables↓ saved 12s ago
03 / 03

Same observability

Dashboard treats BYOC + Finn numbers identically. Same call logs, transcripts, PCA, costs, audits.

DashboardLive
Export

Calls today

12,840

+8.1%

Pickup rate

94.2%

+1.4%

Avg sentiment

+0.71

+0.08

Talk minutes

48,212

+12.0%

Call volume · last 30 days

Completed Missed
Apr 23May 7May 22

Open by design

No carrier lock-in.Ever.

No bolt-ons. No second platform. Every primitive ships with the editor.

Major providers first-class

Twilio, Plivo have one-click setup + full feature parity (DTMF, SMS, MMS, transfers).

Generic SIP trunk fallback

Any SIP-compatible provider works. Your enterprise PBX, your in-house Asterisk, your weird legacy stack — all supported.

Per-number routing

Mix BYOC and Finn-provided numbers in one account. Route each number to a different workflow.

Unified billing observability

Finn platform fees billed by us. Carrier minutes billed by your carrier. Cost dashboard shows both.

Shipped in production

Real teams, real outcomes.

Call abandonment down to 5% from ~30%. 75-80% of inbound calls fully handled by Finn. 24/7 AI coverage replaced 80+ offshore agents.
Shikha Chouksey

Shikha Chouksey

COO & Cofounder, Orbit Wallet · Orbit Wallet

Trust + ecosystem

Plugs in. Audits clean.

Wires into your existing stack via 100+ connectors. Compliant from day one across the workloads that demand it.

Twilio logoTwilioPlivo logoPlivoSalesforce logoSalesforceHubSpot logoHubSpotSlack logoSlack

Don't see yours? Finn plugs into any system via REST + webhooks.

AuditedSOC 2 Type IIHIPAA BAAGDPRISO 27001DPDPNIST CSF

FAQ

Questions and answers.

Which carriers does BYOC support?+

Twilio, Plivo as first-class (one-click setup, full feature parity). Any SIP-compatible carrier via generic SIP trunk integration.

Do I need to port my numbers?+

No. Your numbers stay with your carrier. We just point your SIP routing at Finn's endpoint for inbound calls + handle outbound through your carrier's API.

Are SMS / MMS supported under BYOC?+

Yes — first-class for Twilio, Plivo. Generic SIP carriers depend on what they support; usually voice-only.

How is billing split?+

Finn platform fees billed by us. Carrier voice minutes + SMS billed directly by your carrier on your existing contract. No double-charging.

Can I mix BYOC + Finn-provided numbers?+

Yes. Common pattern: BYOC for established main numbers (preserve reputation + branded ID); Finn-provided for new outbound campaigns + experimental flows.

Your carrier, your contract

Keep your numbers.Keep your rates.

Bring-your-own-carrier (BYOC) gets you Finn's intelligence on top of telephony you already trust. No number porting, no contract change.

Book a demo30-min trial · No card