Policy engine
Rules that follow the call. Across every PBX.
The policy engine evaluates every originate against eleven policy types. Same rules, same evaluator, same audit trail — regardless of which vendor handles the underlying call.
Do-Not-Call list enforcement, jurisdiction-aware
Restrict calls by country, region, or specific number prefixes
Maximum calls per time window, per number / per campaign
Time-of-day routing — open, closed, holiday
Block specific numbers or patterns
Allow-list overrides for VIPs and known partners
Role-based call permissions (e.g. who can dial international)
Prevent conflicting concurrent calls (same agent, same customer)
Regulatory checks (TCPA, GDPR consent, recording disclosure)
Minimum gap between calls to the same number
LLM-evaluated dynamic rules for content, tone, or context
Three-tier editor
Pick your altitude.
Quick rules
Flat sentence rows. "Block calls if number is on DNC list." Built for ops people who just want to add a rule.
Visual builder
Nested AND / OR groups, action chains, generated CEL preview. For analysts who think in conditions.
Code editor
Raw Common Expression Language with schema-aware autocomplete and AI-assisted authoring. For engineers.
Impact preview
Before saving a policy, run it against the last 7 / 30 / 90 days of CDR. See exactly which calls would have been blocked, allowed, or rerouted. No surprise rollouts.
Conflict detection & audit log
Auto-warns when a new policy conflicts with existing ones. Every evaluation — input context, policy version, verdict — is recorded in the policy evaluation log. Tamper-evident on Enterprise.
Get started
One API for every PBX. Wire it up in an afternoon.
Free under 25 extensions, forever. No credit card. No sales gate. Production use OK.