Routing & telephony
1,000 calls
at once. Same finn.
Elastic concurrency per Finn — scales to your plan. No queues, no busy signals, no 'all our agents are helping other customers.'
30-minute free trial. No card. No procurement.
How it works
Scale up.
Scale down. Auto.
Drag, wire, deploy. Each step is reversible — every save creates a versioned snapshot.
Account-level concurrency cap
Set or buy concurrency per plan. Cap shared across all finns OR partitioned per finn — your call.
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
Live throttle controls
Mid-campaign throttle — limit outbound concurrency to keep your downstream CRM, support team, or compliance window stable.
Per-second billing
Pay only for active call seconds. Idle concurrency capacity = free. Spike days don't bankrupt you.
Outcome
Booked
Sentiment
+0.71
Duration
2:14
▸ captured · intent: booking
▸ captured · slot: Tue 14:00
Built for spikes
No queues.
No busy signals.
No bolt-ons. No second platform. Every primitive ships with the editor.
Unlimited per-finn concurrency
One finn can answer 10 calls or 10,000 simultaneously. No per-agent provisioning.
Live throttle
Cap outbound concurrency to protect downstream systems. Adjustable mid-campaign.
Per-second billing
Idle capacity = free. Only active call seconds billed. Spike days stay affordable.
Cross-region capacity
Capacity allocated dynamically across regions for lowest-latency routing.
Shipped in production
Real teams, real outcomes.
“TOFA launched a national campaign with Finn — 10K+ calls daily and seamless human escalations.”
Alice Smith
Senior Engineer, Gofts · TOFA
Trust + ecosystem
Plugs in. Audits clean.
Wires into your existing stack via 100+ connectors. Compliant from day one across the workloads that demand it.
Don't see yours? Finn plugs into any system via REST + webhooks.
FAQ
Questions and answers.
Is there a hard cap on concurrent calls?+
Per-plan caps that scale on demand. Most starter accounts come with 25 concurrent; enterprise customers run thousands. Burstable on request.
How is concurrency billed?+
Per-second active call time. Idle concurrency capacity is free — you pay only when calls are actually live.
Can I cap concurrency per finn?+
Yes — partition account-level capacity across finns, or share a single pool. Useful for protecting downstream systems (CRM rate limits, support team capacity).
What happens when the cap is hit?+
Configurable per workflow: queue + retry, drop with callback offer, divert to voicemail, throttle outbound rate. No silent dropped calls.
How does Finn handle regional latency at scale?+
Capacity allocated dynamically across regions so calls route to the lowest-latency edge. Sub-second voice loop maintained globally.
Capacity without queues
Stop saying
'we're experiencing high volume.'
Finn scales to whatever you throw at it. Spike day, holiday rush, ad-driven surge — same response time, same quality, no queue.