Skip to main content

Routing & telephony

9-5 in Mumbai.9-5 in Manhattan.

Route inbound calls by time of day + caller timezone. Business hours go to humans, after-hours to Finn, holidays to a custom message. All in one config.

Book a demo

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

Per-regionHours config
Holiday-awareCountry calendars
OverflowFallback to Finn
Editable liveNo re-deploy

How it works

Detect.Route. Cover.

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

01 / 03

Define your schedule

Per-region business hours, holiday calendar, lunch breaks if you want. Multiple schedules per finn.

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
02 / 03

Detect caller timezone

Inbound caller area code + locale data → timezone. Inbound from a Mumbai number routes against IST hours.

WorkflowFunction call · check_inventory()200 OK

Latency

384ms

Status

200

Retries

0

Request

POST /api/inventory/check
{
  "sku": "NAVY-HOODIE-M",
  "region": "IN-MH"
}

Response

{
  "in_stock": true,
  "count": 124,
  "next_restock": "2026-06-04"
}
03 / 03

Route the call

In hours → human queue. Out of hours → Finn handles it. Holiday → custom message + callback offer.

OrchestrationMulti-agent flowLive
T
01

Triage

Inbound router

DONE
B
02

Booking

Scheduling specialist

ACTIVE
C
03

Confirm

SMS follow-up

QUEUED

Shared context · call IN-44219

caller.name      = "Aarav Singh"
caller.intent    = "follow-up booking"
captured.slot    = "Tue 14:00"
captured.doctor  = "DR. Patel"
captured.insurer = "BCBS"

Coverage that thinks

Right call.Right time.

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

Multiple schedules per finn

Sales hours, support hours, escalation hours — different rules, same workflow.

Country holiday calendars

Built-in calendars for US, UK, EU, India, Australia, more. Manual overrides for company-specific dates.

Overflow handling

When the queue fills during business hours, Finn picks up the overflow instead of letting calls drop.

Live-editable

Update hours mid-week — applies to in-flight calls within seconds. No re-deploy.

Shipped in production

Real teams, real outcomes.

TOFA launched a national campaign with Finn — 10K+ calls daily and seamless human escalations.
Alice Smith

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.

Twilio logoTwilioPlivo logoPlivoSalesforce logoSalesforceHubSpot logoHubSpotZendesk logoZendesk

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

AuditedSOC 2 Type IIHIPAA BAAGDPRISO 27001DPDPNIST CSF

FAQ

Questions and answers.

How is caller timezone detected?+

Area code mapping for US/Canada (~95% accurate). International caller ID + country code for global. Override via CRM lookup when caller is known.

Can I configure different schedules per workflow?+

Yes. Sales workflow uses sales hours. Support workflow uses support hours. Different finns can share or split schedules.

How are holidays handled?+

Built-in country holiday calendars (US, UK, EU, India, Australia, more). Override any date for company-specific closures (e.g. company offsites).

What happens during overflow?+

When the human queue fills past your threshold, Finn picks up the overflow + handles or schedules callback. No dropped calls.

Can I switch routing mid-shift?+

Yes — manual override from the dashboard. Useful for emergencies, all-hands meetings, weather closures.

Coverage without burnout

Finn covers nights.Humans cover days.

Smart business-hours routing keeps reps focused during their shift + lets Finn handle everything else — overflow, after-hours, holidays.

Book a demo30-min trial · No card