Workforce management, done by your rules.
Stop rebuilding the rota every Sunday night.
- Set it up once. The rota plans itself.
- Assign every job.
- Keep the reason for each choice.
For people and AI agents alike.
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
Still running the rota from a spreadsheet?
- Sun 9pm
Rebuilding next week by hand.Autopilot already planned it. - 5am
Ringing round because someone called in sick.Autopilot offers it to people your rules allow. - Mid-shift
Finding out nobody trained is on the line.Shifts are only filled by people who hold the skill.
Answer three questions. Autopilot does the rest.
Every rota after that is planned on time. It goes out when you say, or on its own.
The screens in it are the real console. How automatic scheduling works.
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.
0
apps to install.Manager in the console, worker on the phone they have.
Plan shiftsConsole
The week, filled for you.
A week’s roster, built under the rest and hours limits you configure. A sick call reopens one shift, not the week.
One shift reopened not the whole week re-planned
Cover a gapConsole
Someone is off? One shift reopens.
Fivexer lists who can legally take it, and why everyone else cannot. Every other shift stays as published.
Assign workConsole
Every job to the right person.
A ticket or job arrives. It goes to the right person, by your rules for skills, capacity and priority.
8 h a week back per person doing the routing
Keep workers informedWorker portal
On their phone, not the noticeboard.
Today’s jobs and this week’s shifts, in the language they read. They share availability and update jobs back.
No app store a PIN, not a password
HoursConsole
Hours ready for payroll.
Planned against worked, with premiums counted. Export when the month closes.
Screenshots, not mock-ups. See every screen.
See who it went to, and who it didn’t.
Pick the situation your team meets most. The outcome comes first; the rules that produced it are underneath.
Ida calls in sick at 6am. Noor is offered the shift. Nothing else on the rota moves.
The engine ruled out 4 of the team, and the record says why for each — so the manager sends one offer instead of ringing round.
| Post | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Northgate · day shift | Sam | Sam | Sam | Elif | Elif | Mateo | Mateo |
| Northgate · night shift | Jonas | Jonas | Elif | Jonas | Jonas | Jonas | |
| Harbour · day shift | Noor | Freja | Mateo | Freja | Ida | Ida | |
| Harbour · night shift | Ida | Ida | Unfilled | Noor | Noor | Sam | Sam |
Open after the sick call — the only cell that moved.
Can take it2
Ruled out4
Behind: a real solve, filmed at three times the speed. In front: this week's cover, computed here.
Why this outcome
Rules are sentences with your figures in them
yours, not ours“At least 11 h between shifts.” “No more than 48 h in any seven days.” Country packs are editable starting points, not rules Fivexer applies automatically — a configured rule is enforced and explained; a blank one is not checked.
The previous week is part of the answer
historyRest and rolling hours are measured across the boundary. Without last week’s shifts, no limit can be checked on a Monday.
Cover ranking is profiling-free
by designQualifications, permissions, rest, travel and real hours. No acceptance history, no no-show prediction, no learned behaviour.
The week is a sample; the ranking beside it is computed in this tab from that week and those rules.
Run the 6am call-inRouting 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.
Add your team
Names, skills and sites, by hand or from a CSV. No developer, and no data migration.
Minutes
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
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
- 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 →
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.
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.
What the product gives you
What we commit to
“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.
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.
Bars compare the printed figures at face value. €1 ≈ $1.08 changes nothing you can see.
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.
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.
