Calendar & booking
Right slot.
Right rep. Every time.
Conditional booking logic — match the caller to the right calendar based on intent, geography, account tier, product, or any captured field.
30-minute free trial. No card. No procurement.
How it works
Detect.
Branch. Book.
Drag, wire, deploy. Each step is reversible — every save creates a versioned snapshot.
Capture decision signals
Intent, geography, account tier, product interest, language — captured fields drive the routing decision.
Outcome
Booked
Sentiment
+0.71
Duration
2:14
▸ captured · intent: booking
▸ captured · slot: Tue 14:00
Branch to the right calendar
Enterprise lead → senior rep calendar. SMB lead → SDR calendar. Spanish speaker → Spanish-speaking rep.
Book with fallback ladder
No exact match available in the window? Falls back to next-best calendar per configurable ladder.
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"
}Booking logic that thinks
Targeted.
Not generic.
No bolt-ons. No second platform. Every primitive ships with the editor.
Multi-signal routing
Match on intent, tier, geography, product, language — any captured field.
Per-workflow rules
Sales has one rule set. Support has another. Different finns, different logic.
Fallback ladders
No exact match? Ladder gracefully down to next-best. Never strands a caller without a slot.
Live A/B test
Test 'route by tier' vs 'route by intent' — measure conversion per branch in PCA.
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.
Google Calendar
Cal.com
Calendly
Salesforce
HubSpot
SlackDon't see yours? Finn plugs into any system via REST + webhooks.
FAQ
Questions and answers.
What signals can drive booking decisions?+
Intent (from voice analysis), geography (area code or stated location), account tier (CRM lookup), product interest (captured field), language detected, custom workflow flags.
How is fallback handled?+
Configurable per workflow. Default: prefer exact match → next-best tier → any available with 24h. Can be tightened (no fallback, callback offer) or loosened per business rule.
Can I A/B test routing rules?+
Yes — split traffic across branches + measure conversion + show-rate in PCA. Useful for tuning round-robin pools or testing new routing signals.
Are rules editable mid-campaign?+
Yes — live edit from the dashboard. Changes apply to in-flight calls within seconds. No re-deploy.
Can I see which rule fired for a given booking?+
Yes — every booking logs the decision path (which signals were captured, which branch fired, what the fallback was). Audit-ready.
Smarter than round-robin
Stop sending
everyone to the same calendar.
Conditional slot logic books the right caller with the right rep on the first try. Higher conversion, fewer rescheduled handoffs.