Routing that learns who's best — and never breaks your rules
The right person for the work — every time. Fivexer routes each ticket to whoever's actually best for it, by skill and current load, so queues clear faster, no one drowns while others sit idle, and every decision is traceable to a name and a reason.
Free sandbox and working API key at signup · Open-source (MIT) engine you can self-host · Questions first? Talk to us
Live numbers from a simulation running on this page right now — not a screenshot.
A live routing simulation, cycling through real industries.
When the right work reaches the wrong person
Manual routing is only as good as its last re-check. The misses compound quietly.
The screen your ops lead runs the day from
Queues, wait times, and who's carrying the load — one live view. In the real console you pause a person, bump a priority, or reassign with a click; here it's running this page's simulation.
A live re-creation of the Fivexer console — every number above is computed, not drawn. Open the full simulator →
You set the rules. The engine does the assigning.
Who can handle what, what jumps the queue, and what's off-limits — written down once, enforced on every request.
Then it learns who's best — inside those rules
Real outcomes decide who gets picked next, but only among people your rules already allow. Watch it live: Alex completes, Casey escalates, and the work shifts on its own — nobody touched a config.
Casey was cut off automatically after enough poor outcomes — before it costs you.
Your first wins, in week one
No quarter-long rollout. Both land with the first routed request.
People who aren’t certified for a case are never eligible — not deprioritized. Blocked.
Ask why did this go to Sam? and get the actual answer: who was considered, who was blocked, and what decided it. This one is live — a real record from the console view above.
See it in your world
Prefer to drive it yourself? Both run this same engine, live:
Dispatch DuelRoute one 90-second shift yourself, then see how the engine routed itPlay the shift →ClinicGridMulti-office patient routing — schedule, triage, assignOpen the demo →Skip the infrastructure. Keep the engine.
Everything on this page, as a hosted API. Sign up with an email and a free sandbox with a working API key is ready instantly — your first task routed in minutes.
Runs in the EU. Your routing data — tasks, workers, and the decision trace behind every match — stays on infrastructure in Frankfurt, Germany. What we store, and what doesn't stay in the EU.
- REST API with a published contract. Every routing move is a /v1 call. OpenAPI 3.1 lives at /openapi.json.
- Typed TypeScript SDK. npm i @fivexer/sdk — tasks, workers, traces, and live stats, typed end to end.
- AI agents over MCP. One command connects Claude or Cursor to your queue — agents work it like anyone else.
- Signed webhooks. Lifecycle events pushed to your stack, verified with one SDK helper.
- A console your operators can live in. Live-ops dashboard, workflow editor, and the full decision audit trail.
- Portable by design. MIT engine underneath — self-host anytime, your rules and traces travel with you.
import { Fivexer } from '@fivexer/sdk';
const fx = new Fivexer({
// your API origin + the sk_test_… key from signup
baseUrl: process.env.FIVEXER_BASE_URL,
apiKey: process.env.FIVEXER_API_KEY,
});
await fx.workers.upsert({
id: 'agent_007',
tags: ['english', 'technical_support'],
});
await fx.tasks.create({
tags: ['english', 'technical_support'],
priority: 5,
});
// the engine matches it — your webhook fires,
// and the decision trace is recordedRather have an agent write the integration? One command hands Claude 14 tools over the same API:
claude mcp add fivexer -e FIVEXER_API_KEY=sk_test_... \ -e FIVEXER_BASE_URL=<api origin> -- npx -y @fivexer/mcp
Works with the tools you already build with
Anything that can call an API can route. Shown for compatibility; no affiliation implied.
For the engineer you'll hand this to
Zero-weight rules are absolute — the learning layer can never assign around a veto.
Show the code
await assignmentMatcher.addUser({
id: 'agent_1',
tags: [],
routingWeights: {
'support:*': 100, // eligible
'lang:*': 0, // hard veto for all language-tagged assignments
default: 0, // hard veto for default matching fallback
},
});- Match decisions compute in under a millisecond — measured live by the simulation running on this page.
- Redis sorted sets and per-tag indexes — no message broker to run alongside it.
- A drop-in npm library against the Redis you likely already run — nothing new to provision to try it.
Why teams pick Fivexer — and what it costs
The differences that actually decide it, then published list prices against your own numbers. Fivexer Cloud is free during launch — sandbox included, no card, no Redis to run.
Managed EU cloud, self-host the open-source (MIT) engine, or bring your own Redis. The locked-in platforms are hosted-only, at any price.
A zero-weight veto is absolute — the learning layer cannot override it. Elsewhere that guarantee is workflow config you write and maintain yourself.
Every match records who was considered, who was blocked, and why. Most routing is a black box with a log of what happened, not why.
Tickets, cases, field jobs, AI agents as workers — with built-in fairness modes so no one drowns while someone else idles.
Need voice, SMS, or a full helpdesk built in? That's Twilio's and Zendesk's home turf — Fivexer is the routing engine only, by design. Feature-by-feature tables: Twilio TaskRouter, Zendesk, Genesys / NICE / Five9.
Free up to 10,000 assignments/mo while we launch — paid tiers land later.
100 free + 49,900 × $0.06 per month
25 agents × $115/agent/mo on annual billing — buys the whole helpdesk, not just routing
$2,875/moback in your budget at these numbers — the cheapest alternative shown bills that much every month, and Fivexer Cloud is free during launch.
List prices as of July 2026: Twilio TaskRouter published rate ($0.06/task after the first 100 free); Zendesk Suite Professional, the entry plan with skills-based routing. Excludes negotiated discounts, HA replicas, and egress. The products overlap, not match — TaskRouter is the closest comparison; Zendesk bundles a full helpdesk. Fivexer Cloud is a launch offer, not a sourced vendor price. Free during launch up to 10,000 assignments/mo. Paid tiers land later.
What happens when launch pricing ends
- 60 days' notice by email before anything changes.
- 6 months of grandfathering — workspaces created during launch keep the launch allowance after that notice takes effect.
- Export is always free, on every plan, whether or not you're leaving.
- The engine is MIT — if the price never works for you, run it on your own Redis.
In writing: launch terms · where your data runs