Visual routing logic that
ships in seconds.
Build buyer hierarchies, day-parting rules, geo and vertical caps, fail-overs and overflow — all on a drag-and-drop canvas. A/B test new routing plans against live traffic in minutes.
Routing plan · auto_fl_v4 · 14 rules
LiveFrom caller to closed-loop in milliseconds.
Open the canvas
Each routing plan is a tree of conditions, branches, buyer buckets and fail-overs.
Drop in rules
Geo, day-part, intent, tier, caller history, custom attributes — combine with AND/OR/ELSE.
A/B against live
Ship the new plan as a 10/90 or 50/50 split against the current production plan.
Promote to 100%
Promote the winning plan with one click — no code deploy, no downtime.
Every moving part.
Drag-and-drop canvas
Build complex multi-level routing trees without writing a line of code.
Day-parting
Hour-of-day, day-of-week, holiday and timezone-aware rules.
Geo & vertical caps
State, area-code, vertical-level caps with hourly, daily and weekly windows.
A/B testing
Split-test routing plans against live traffic with statistical-significance dashboards.
Fail-over chains
Automatic cascades when primary buyers are capped, unhealthy or below-floor.
Versioning & rollback
Every plan change is versioned. One-click rollback to any prior plan.
The teams that live by inbound calls.
Multi-state networks
Insurance and legal networks with state-by-state routing rules.
Multi-location ops
Home-services franchises routing by geography to nearest qualified pro.
Tiered buyer pools
Tier-1, Tier-2, Tier-3 buyer pools with fail-over cascades.
24×7 ops
Day-shift, night-shift and weekend buyer rotation with timezone awareness.
What teams always ask.
Plans propagate to all routing nodes in <6 seconds globally. There is no deploy, no downtime, no rebuild.
Yes. The canvas supports nested boolean logic, custom attributes, computed fields and external API lookups (with caching) inside rule conditions.
Pick two plans, set a traffic split (10/90, 50/50, etc.), and the system randomly buckets calls. The dashboard shows statistical-significance on fill rate, clearing price and downstream conversion.
Yes — Pulse supports YAML import for routing plans, plus a programmatic API. Many teams ship the first plan from a YAML file then iterate visually.
Per-plan ACLs control who can edit, who can ship and who can promote A/B tests. All edits are audit-logged.
Related Pulse capabilities.
Your next revenue conversation
is already ringing.
Spin up tracking, telephony and AI in a single platform — the way modern US revenue teams do it.
7-day free trial · No credit card · Cancel any time