AI for routing: tomorrow’s routes, built in ServiceMinder
People search for AI for routing when someone in the office loses a big part of every day to building tomorrow’s routes. Alvin does that job inside the ServiceMinder account you already use: it reads the queue and the notes on each visit, gives every stop to a tech, builds one route per tech, and emails the office what to look into. There’s no new routing software to move to.
On this page
Why routing takes so long by hand
ServiceMinder’s optimizer puts a route in order in seconds. The time goes on everything around that button:
- Who gets which stop. Each tech has a side of town, a place they start from and a normal day’s work. That’s rarely written down.
- Rules in the notes. “Send this tech”, “mornings only” and “first on route” are typed into each visit. The optimizer doesn’t read them, so someone has to.
- One tech at a time, every day. Pick the stops, optimize, check, commit, then start on the next tech. Then it all comes back tomorrow.
What Alvin does each day
- Signs in as your office. The ServiceMinder login stays in Alvin’s vault. Your team never sees it, and it never appears in a chat or an email.
- Reads the day. The next day’s queued appointments and their notes, the techs, and the last few weeks of routes.
- Turns the notes into rules. Each instruction becomes a rule tied to its stop, as the table below shows.
- Learns each tech’s area. From your own past routes: their usual side of town, where they start and how much they normally do.
- Plans one route per tech, by code. The same day and the same notes give the same plan. No AI model picks the stops.
- Builds and checks each route. In ServiceMinder’s Route Builder, with its own optimizer. Alvin then reads the route back and checks it against the notes and ServiceMinder’s own drive times, and moves any stop the order put against a note.
- Leaves drafts or commits. Your company’s choice. Drafts wait for someone to press Commit. If you choose commit, your office fine-tunes on the calendar instead, and a route Alvin couldn’t check is never committed.
- Emails the office. What to look into, with a link to each appointment, and each route’s stops, driving and finish time.
What Alvin does with a note
The notes below are made-up examples, in the style offices type them.
| The note says | What Alvin does |
|---|---|
SEND DARNELL | Gives the stop to that tech. If that tech is off, the stop stays in the queue for the office. |
DO NOT SEND WES | Keeps the stop off that tech’s route. |
TIME: MORNING | Starts the stop before noon. |
FIRST ON ROUTE | Puts the stop first on its route, and checks that it’s still first after the optimizer runs. |
KEEP ON 11/17 | Tells the office if the stop is queued on any other day. |
SCHEDULE WITH 14 ELM ST | Gives both houses to one tech, one after the other. If the other house isn’t in the queue, Alvin says so. |
12 GALLONS | Over the amount your office sets, tells you the stop needs a second tech, so you can add one. |
LAST ON ROUTE | Alvin’s reader doesn’t know this one, so it quotes the note to the office rather than guess. |
If a note names a tech Alvin can’t match, that stop stays in the queue and the office is told. Add the nickname to your same-people list once and Alvin knows it from then on.
What the office gets
What stays with your office
- Customers. Alvin doesn’t send customer messages. Your notifications go out the way they do today.
- The day itself. Call-outs, rain and anything your team knows that isn’t in the notes. Your office can still drag stops, or uncommit a route in ServiceMinder.
- Late changes. Alvin routes from what’s in ServiceMinder when it runs, so a stop removed afterward stays on its route until someone takes it off. So pick a daily cutoff for changes.
- Work you’ve already done. A tech your office has routed keeps that route. A rerun replaces only Alvin’s own uncommitted drafts.
Test it on days you’ve already run
Before Alvin routes a real day, it can plan past days as if they were still queued, using only the routes from before each day, and set its plan beside the routes you ran. Nothing is built in ServiceMinder. We don’t promise a number of hours or miles. Your own days are the fair test, and our guide on how to automate ServiceMinder routing explains how to compare two plans honestly.
Frequently asked questions
Which routing software does Alvin work with?
ServiceMinder only, today. If your routes live in another app, Alvin can’t route them yet.
Can we turn this on ourselves?
Not yet. We turn it on for one company at a time and set it up with your office. Join the waitlist or use the pilot form, and tell us you’re on ServiceMinder.
Does Alvin replace ServiceMinder’s optimizer?
No. Alvin decides which tech gets which stop and reads the notes, then uses ServiceMinder’s own optimizer to order each route. Alvin changes that order only to keep a note, or when its own order drives less.
Will Alvin commit routes without asking?
Only if your company chooses that. Otherwise Alvin builds drafts, and nothing reaches the calendar until someone in your office commits them.
Does Alvin text or email our customers?
No. The only email Alvin sends from this job goes to the office. Check whether committing a route triggers anything in your own ServiceMinder setup before you let Alvin commit.
What does it cost?
Alvin’s plans are on the pricing page. Because routing is set up with each company, we’ll go over what it costs for your office before anything is turned on.
Get tomorrow’s routes off your office’s plate.
Routing is turned on one company at a time, for offices on ServiceMinder. Join the waitlist, or tell us about your routes.