IllustrativeFivexer → Anna7am
Forklift relief, Dock 3. You hold the licence and have the lightest load.
Clarity
Everyone knows what is theirs.
Each job goes to one person, with the reason on record.
Make your work predictable.
Assign every job. To an agent or a person.
Free for 15 people. No credit card. No trial countdown.
You talk to the person who built it. Viljar, founder. A person replies within 1 working day. support@fivexer.com
- 13
- country rule packs to start from
- €0.50
- a person a month, after 15 free
- EU
- hosted in Frankfurt, data stays here
- MIT
- open-source engine, no lock-in
Clear jobs, no clashes, fair shifts.
Illustrative
Illustrative · the sample rotaNo clashes
Clashes are caught before anyone turns up.
Double bookings, too little rest and missing skills show up while you plan.
8 ha week back for each person who hands out the work
Time and money
Sunday night is yours again.
Autopilot plans next week on time. You check it and publish it, or let it go out on its own.
Nights, weekends and holidays shared evenly
Fair shifts
Fair rotas are the ones people stay for.
Nights and weekends are shared evenly, and wishes count in every plan.
The whole product in under two minutes.
02Your rules
You make the rules. It works the board.
Skills, capacity, priority, rest and fairness are figures you set once. Every job after that goes out without anyone reading the queue.
Every job makes the next one easier. That is the flywheel.
Routing, escalation, the record, learning and the rota feed each other. The more work goes through, the less anyone has to manage it.
01 / 05Route
- Step 1 · RouteIllustrative · the worker app
The next free person who qualifies gets it.
Nobody cherry-picks from a shared queue. The highest-priority job goes to the best-fit person who is free, within the workload limit you set.
FivexernowSkill Site Restlightest loadNew job: floor scrubber fault, Northgate
AcceptNot now
- Right first timeOnly people with the exact skill, language or ticket get the job, so it isn’t passed around.
- Context decidesFields you send with the job, from your helpdesk or CRM, set its skills and priority. Urgent work skips the line.
- Rules, not codeOperations change the rules in the console. Nothing to redeploy, no ticket for engineering.
- No routing engine to buildReal-time state, races and retries are handled. Hosted in the EU, or run the open-source engine yourself.
0 apps to install.
Manager in the console, worker on the phone they have.
03See it work
Everyone knows their job. But what happens when someone calls in sick?
6am. Ida is out sick.
The Wed · Harbour · night shift opens. Nothing else on the rota moves.
IdaOut sick · 6am
NoorOn the rota
FrejaOn the rota
SamOn the rota
ElifOn the rota
JonasOn the rota
MateoOn the rotaThis rota’s rules11 h rest between shifts48 h in any seven daysThe skill the post needsCleared for the site
Wed · Harbour · night shiftMonAs publishedTueAs publishedWedOpenThuAs publishedFriAs publishedSatAs publishedSunAs publishedEvery other day stays as published.
One absence. One shift reopened.
4 ruled out, one offer sent, and the rest of the week exactly as published.
See it work. Recorded in the console.
04Get started
You’ve seen how it decides. Now start with your team.
Routing real work by this afternoon.
You can be routing your own work the same afternoon. Nothing below needs a rollout plan.
Same afternoon
from an empty workspace to the first routed queue.
1
Add your team
Names, skills and sites, by hand or from a CSV. No developer, and no data migration.
Minutes
2
Try one workflow
One queue, or one week’s roster, in shadow beside how you decide today. Read the decisions before anyone’s work depends on them.
An afternoon
3
Point your agent at it
A webhook in, a decision out, on every ticket or job — over the API, the SDK, or an AI assistant that speaks MCP.
When you choose
Works with the assistants your team already uses
- Claude
- ChatGPT
- Cursor
- and any other MCP client
- Lovable
- Bolt
- v0
- the prompt that builds the app →
Anything that speaks MCP can drive a workspace, and any builder that can call an API can put a screen on one. Shown for compatibility; no affiliation implied.
https://api.5xer.com/mcpAdd it as a connector — OAuth, no key to paste and nothing to install. How to set it up →
Where it stops
Fivexer sits beside your helpdesk, field app, payroll and HR system — it replaces none of them. There is no one-click connector yet, and we would rather say so here than on the second call. The docs and the agent interface are how a developer wires it up; moving from Twilio TaskRouter has a written migration guide.
05About & pricing
A small EU vendor. Every claim links to its proof.
You are going to ask procurement to approve us. These are the facts they check first — and the page that proves each one, including the certifications we do not hold.
Where it runsFrankfurt, Germany — routing data never leaves the EUSee the hosting account →PaperworkArticle 28 DPA published — read it without emailing usOpen the DPA →Who else sees itEvery subprocessor named, with what actually reaches themSee all 5 →If you leaveThe engine is MIT — run it on your own Redis, keep your rules and tracesRead the source →
What the product gives you
Every decision comes with its reason.Who was considered, who was ruled out, and the rule that did it. Reassign in one click and the record keeps both decisions.
Your rules, not a vendor's opinion.Skills, capacity, priority, fairness, rest and hours are figures you approve. Country packs for 13 jurisdictions are editable starting points, not rules applied automatically, and a rule you did not configure cannot be broken. See the packs, each with the statute it was read from.
Your people need nothing from an app store.The worker portal opens on the phone they already have, with a PIN rather than a password, in the language they read, with your name on it.
Work is spread fairly, not dumped on the fastest hand.Backlog caps and fairness modes keep one person from drowning while others idle — tickets, cases, field jobs and AI agents alike.
Ranking never profiles anyone.Qualifications, permissions, rest, travel and real hours. No acceptance history, no no-show prediction, no learned behaviour.
What we commit to
Routing data stays in the EU.One region — DigitalOcean Frankfurt, Germany. Not a "primarily EU" arrangement. Every subprocessor is named on /security, with what reaches each one.
A published Article 28 DPA (v1.1, in force since 27 July 2026).Already binding via the terms, and all 5 subprocessors are listed in it. Read it before you talk to us — /dpa.
A person answers within 1 working day.Support and procurement alike. Not an availability percentage; a commitment about how fast you reach someone who can act. A security report is acknowledged within 3 days, and deletion reaches storage within 30 days.
Prices in public, with notice periods.60 days' written notice before published prices change, and 6 months' grandfathering for launch workspaces.
“I wrote the routing engine, I run the infrastructure, and I answer this mailbox. If you are weighing up whether a small EU vendor is a safe bet for something as load-bearing as who gets your work — write to me directly and ask the hard version of the question.”
Viljar Võidula · viljar@fivexer.com · the engine on GitHub
Testreel OÜ, registered in Estonia (reg. 12592678). The full security account — including the certifications we do not hold and every subprocessor outside the EEA.
Free for 15 people. Then €0.50 each.
UK rota apps list £2 to £6.88 a person a month. Rota, cover, time tracking, leave and the worker app are all in ours. See the sourced comparison.
15 people
€0 a month
25 people
€5 a month
60 people
€22.50 a month
120 people
€52.50 a month
Free€0.50 a monthEach dot is 5 people. On Pay as you go, which has no monthly fee.
Handing out tasks too?
10,000 assignments a month are free. Past it, pay €4 per 1,000, or move to a plan from €99 a month. Matching pauses at the monthly allowance.
- Routing and roster tools, in one console.
- Hosted worker portal and installable mobile web app.
- Workers share availability, request time off and update jobs.
- A record explaining who gets each job—and why.
What you win, in your own numbers
Five sliders. The answer updates as you move them.
Two of these are our estimate, from your volume and team size. Drag either to replace it with your own.
An hour of their time is salary plus everything you pay on top of it. Ask one of them; it is usually more than you think.
Spent deciding who takes what
$55,328a year
0.7 of a full-time job.
Fivexer plan for this volume$21.60 / mo
Expected capacity handed back (70% planning case)$38,730 / year
Net annual capacity after the plan$38,470 / year
Benefit for each euro of subscription149.4×
It pays for itself the moment it hands back <1% of those hours.
The 70% case is an educated planning estimate, not a measured Fivexer result. It keeps 30% for exceptions, rule maintenance and oversight. A published ticket-routing example reduced assignment from two hours to immediate; broader research estimates 49% of managerial work is technically automatable. Neither source proves your result. Routing example · Management research
Need voice, SMS, or a full helpdesk built in? That's Twilio's and Zendesk's home turf — Fivexer is the routing and rostering engine only, by design. Priced side by side, with sources and dates: Twilio TaskRouter, Zendesk, Genesys / NICE / Five9.
Fivexer Cloud prices are published EUR list prices as of August 2026, excluding negotiated discounts, HA replicas and egress. Free tier up to 10,000 assignments/mo. Paid billing starts when checkout launches; launch price locked for 12 months from first invoice. See /pricing → · What happens when launch pricing ends
Leaving Twilio TaskRouter? Same routing job. Not metered per task.
TaskRouter routes tasks to workers by skill and priority and charges $0.06 for each one, forever. Fivexer does the same job on a flat plan, keeps routing data in the EU, and writes down why each worker was chosen.
$2,994 a month
€99/ month
At 50,000 assignments a month. Their published list price, then ours.
Assignments a month10,000a small desk
Twilio TaskRouter$0.06 per task
$594 / month100 free + 9,900 × $0.06Fivexera plan, volume included
€0 / monthFree — inside the 10,000 allowanceAssignments a month50,000a busy operation
Twilio TaskRouter$0.06 per task
$2,994 / month100 free + 49,900 × $0.06Fivexera plan, volume included
€99 / monthPro — 50,000 includedAssignments a month250,000several sites
Twilio TaskRouter$0.06 per task
$14,994 / month100 free + 249,900 × $0.06Fivexera plan, volume included
€399 / monthPro — then 200,000 over the included volumeBars compare the printed figures at face value. €1 ≈ $1.08 changes nothing you can see.
What changes
Fivexer
TaskRouter
Where the data goes
Yes: Routing data stays in Frankfurt, DE. Every subprocessor named.
No: Tasks and worker data are processed in Twilio’s US cloud.
What the bill does at volume
Yes: A plan with the volume included. Public prices, 60 days’ notice.
No: Metered per task, every month, with no published volume discount.
Why this worker
Yes: Every decision records who was considered, who was ruled out, and the rule that did it.
Partly: Lifecycle events say what happened, not why a worker was chosen.
Spreading the work
Yes: Backlog caps and fairness modes built in — best-match, balanced, spread-work.
Partly: Longest-idle within a queue. Anything beyond it, you build.
Beyond the contact centre
Yes: Tickets, field jobs, shifts, AI agents as workers. Tags are generic.
Partly: Shaped for Twilio Flex. Other domains fight the grain.
Voice, SMS, chat
No: Not here, by design. A routing engine, not a telephony platform.
Yes: Native, with Twilio’s platform SLA. If you are on Flex, this is the better fit.
Moving over is a webhook in and a decision out. The migration guide maps workspaces, task queues and worker attributes to their Fivexer equivalents, and the full Twilio TaskRouter alternative comparison runs eleven rows, both ways.
Route one queue beside TaskRouter, freeAlso comparedZendeskGenesysDeputyPlandayConnecteam
Twilio’s figures are its published list price (twilio.com/en-us/pricing) as of August 2026, in USD as published. Ours are in EUR, as published on /pricing. TaskRouter is excellent at what it is built for; this is about fit as a routing engine, not overall product quality.
06Start free
The nine questions you would ask anyway.
Every evaluation reaches them within ten minutes. Answered here in writing, so the first call can start at question ten.
Do we need a developer to start?
No. Add your people and their skills in the console, then create work there or import a backlog from a CSV, and build the first roster in the same place. A developer connects your helpdesk or field app later, over the API — in an afternoon, not a quarter.
How long until it is routing our real work?
Run it in shadow first: let the engine decide alongside whoever decides today and compare the two. Most teams read a week of decisions, or a solved rota beside their existing one, before anyone’s work depends on it. There is a shadow-mode checklist for exactly that.
What happens when it gets one wrong?
Reassign in one click, and the record keeps both decisions. A rule you did not write cannot be broken, and a veto you did write cannot be learned around — the learning layer only re-ranks candidates who already passed every hard rule.
Can an AI agent drive this?
Yes, and it takes about a minute rather than a project: point Claude, ChatGPT, Cursor or anything that speaks MCP at api.5xer.com/mcp, sign in, and it can create work, read the queue, solve a roster and ask why a decision went the way it did. OAuth, so there is no key to paste and nothing to install, and you grant read or read-and-write. The deciding stays deterministic: an agent asks the engine to decide, never instead of it, so every rule and every trace still holds.
Does it work with Zendesk, Jira or our field app?
It sits beside them rather than replacing them: a webhook in, a decision out, on every ticket or job. There is no one-click connector yet, and we would rather say so here than on the second call. Moving from Twilio TaskRouter has a written migration guide.
Whose working-time rules does the roster enforce?
Only the ones you configure. Start from a published country pack or enter the figures yourself — minimum rest, hours in a rolling window, night limits. Packs are editable starting points, not rules Fivexer applies automatically. A blank rule is not checked; a configured rule is enforced and explained in plain language.
Does it replace our payroll or HR system?
No. Fivexer builds and covers the roster and routes the work; payroll, accounting and HR stay where they are. Planned and worked hours, including premiums, export as a record payroll can read.
Do our people need an app from the app store?
No. The worker portal opens on the phone they already have, with a PIN rather than a password, in the language they read, with your name on it — for today’s jobs and this week’s shifts alike.
What if you disappear?
Export is free on every plan, and the matching engine is open source under the MIT licence — so you can run your own rules and traces on your own Redis the same day. Routing data is held in one EU region, and every subprocessor is named on the security page.
Build next week’s rota for free.
Create your free workspace, add your team and review your first decisions. No credit card. No trial countdown.
Evaluate one workflow with us
Bring one queue or roster and the rules your team follows. We’ll discuss the setup, how to review the decisions, and what it would take to run it in production.
Discuss my workflow →We’ll agree the scope and any cost before work starts. A person replies within 1 working day.
