stepbase
← Blog

Process design

Stop Forwarding Every Request by Hand: Let AI Sort Them, and Pass the Unclear Ones to a Person

If your first hour goes on reading and forwarding requests from every branch, here is how to route them automatically, with a person still in charge.

stepbase Team·November 8, 2026
AI triageRequest routingMulti-branch teamsWorkflows

It's 8:15 and there are 31 new requests from the branches. A leaking tap at the north site. A till that won't print receipts. Someone asking whether they can carry over leave. A complaint about a supplier. A "quick question" that's actually three questions.

You read every one and decide who should deal with it: facilities, IT, HR, the area manager. You forward it, sometimes with a note. By the time you've worked through them it's 9:30, and you haven't done any of your own work yet.

Sorting isn't hard. It just never stops, and nothing moves until you've done it. On the days you're off, it doesn't get done.

Why it breaks once there's more than one branch

With one branch, the person who sorts requests knows everyone and everything. With five or ten, sorting becomes a bottleneck with a name: yours.

The usual fixes don't last long:

  • A drop-down that asks people to pick a category. People pick the first option, or "Other", or the wrong one because they're guessing what you call things. You end up reading every request anyway to check.
  • A separate form for each team. Now the branches have to know which of six forms to use. The leaking tap lands on the IT form, because the tap is in the server room.
  • A shared inbox that everyone watches. Everyone assumes someone else has taken it. Two people answer one request, and nobody answers the next.
  • Email rules. They match words, not meaning. "The card machine is broken" and "can we order a new card machine" go to the same place, though one is a fault and the other is a purchase.

The real issue is that sorting takes judgement. That's why it falls to the one person who has it, and why it doesn't scale.

What good looks like

Whatever tools you use, a good setup for incoming requests has five parts:

  1. One way in. Every branch uses the same form, whatever the request is about. Nobody has to know your org chart to ask for help.
  2. Sorting by meaning, not keywords. Someone (or something) reads what the person actually wrote and decides where it goes.
  3. A named person for the unclear ones. Some requests really are ambiguous. They should go to someone who decides, not get guessed at.
  4. A record of every decision. When a request ends up in the wrong place, you can see who sent it there and why, and fix the rule rather than blame the branch.
  5. The requester isn't left wondering. They know it arrived and who has it.

You could do some of this with a rota: whoever's on sorting duty this week. That spreads the load but not the judgement. The tool-neutral lesson is to separate receiving from sorting, so the second can be shared, written down and, for the easy cases, automated.

How AI sorting works, honestly

This is the part AI is good at. It reads a short piece of text, compares it with descriptions you give it, and picks the closest match. "The till won't print receipts" is a hardware fault. "Can I carry over five days" is an HR question. It's the same judgement you make at 8:15, applied to the wording rather than to keywords.

It's also the part where you shouldn't trust AI blindly. So the useful version isn't "AI decides". It's AI first, person if unsure: the AI rates how confident it is in its own choice. Above a level you set, it files the request. Below that level, or if anything goes wrong, the request goes to a person you named, as an ordinary Task.

Two things to know before you rely on it:

  • It reads the text people type, the fields you let it see. It doesn't open attachments, so a photo of the leaking tap is just a filename to it. Ask for a short description in the form, and the AI has something to read.
  • Its confidence is its own estimate. Start with a cautious threshold and lower it once you've watched it for a few weeks.

How to build it in stepbase

The quickest start is the Categorize Feedback template. It sorts feedback into four categories with an AI Step and passes unclear ones to a Support team. You'll change the categories to your own, but the setup is the same. You can also describe your process in a sentence on the stepbase home page and let it draft the app.

Either way, here is what you end up with:

  1. Make one Form for every branch. Keep it short: which branch, a one-line summary, the details, and an optional photo. Share it as a link, or put the QR code on the staffroom wall.
  2. Add a Step that sorts. In the Form's Workflow, add a review Step and give it one Action per category: Facilities, IT, HR, Area manager. Those Actions are the choices the AI picks from.
  3. Assign the Step to AI. Set the assignment to AI and choose the mode AI first, person if unsure.
  4. Write the instructions the way you'd brief a new colleague. One line per category: "Facilities: anything about the building, plumbing, heating, doors or cleaning." "IT: tills, card machines, laptops, Wi-Fi, logins." Say what to do with edge cases: "A broken card machine is IT; a request to buy a new one goes to the area manager."
  5. Choose what it may read. Under Readable context, add only the summary and details. The branch name and contact email don't help it sort.
  6. Set the threshold and the hand-off. Hand off below confidence starts at 0.7 (70%). Under Hand off to, pick the person or team who takes the unclear ones. That's probably you at first. Don't leave it empty: with nobody to hand off to, an unclear request waits instead of moving on.
  7. Connect each Action to where the work goes next. Draw each Action to the next Step: Facilities to a Step assigned to the facilities team, IT to the IT team, and so on. Each team then sees its own requests in My Work, already sorted.
  8. Test it before you share the link. Send last week's requests through it yourself, including the awkward ones, and see where they land before the branches start using it.

From then on, every AI decision goes in the request's history with the category it chose, its confidence and its reasoning. When something lands in the wrong place, read the reasoning, add a line to the instructions, and publish again.

AI Steps depend on your plan. On a plan without them, the Step goes straight to the person you named under Hand off to, so the Form and its Workflow still work while you decide.

Getting the other branches on board

Don't announce a new system to every branch on Monday. Start where you already are:

  • Run it on your own inbox first. For two weeks, send requests through the Form yourself and keep Hand off to pointing at you. You'll see every unclear case, which is exactly how you learn what to add to the instructions.
  • Bring in one or two branches. Pick the ones that send the most requests. When they stop chasing you for updates, the others will notice.
  • Show the teams their own list. Facilities and IT will care more about getting only their requests, already sorted, than about AI. Lead with that.

Once it's working, the threshold is something you can tune. Lower it as your instructions improve and fewer requests come to you unsorted.

The hour you get back

The sorting doesn't go away, but most of it stops needing you, and the unclear cases still come to you. Start with the Categorize Feedback template, or describe your process at stepbase and build it from your own wording.

Ready to build your first app?

stepbase gives you a visual designer, conditional routing, and a full audit trail. No code required.