Free tool $97 value
Stop being the router.
Every message that reaches your business goes through your head first. What is it, what is missing, how urgent, who gets it. Paste ten of the messages you actually get and this builds the four tables that let an AI read them and a rule decide, so you only judge the exceptions.
- Your number. The hours and dollars the sorting costs you.
- Your pattern. What your own messages show, the moment you paste them.
- Your tables. Request types, rules, routes and a never-decide list.
- Your router. A prompt that applies them, and a five-day plan.
About 25 minutes. The first two steps need no email.
Step one of four
What being the router costs you.
Four numbers. Be honest on the last one: look at the last ten messages you handled and count the ones only you could have answered.
Email, texts, DMs, voicemail, forms. All of them.
Read it, work out what it is, forward it or reply.
What you would bill, or what you would pay someone to do your job.
A complaint, a money question, something new. The rest were routine.
Fill in all four and your number shows up here.
Step two of four
Paste ten to fifteen messages you actually got.
Three messages only describe three messages. Ten starts to show a pattern, and a pattern is what the rules get built from. Use the real ones, messy and half-finished, exactly as they arrived. Take names out if you like. Put a line of three dashes between each one.
No messages handy? Try it on made-up ones.
This fills the box below with twelve example messages, so you can see what the page does. You can replace them with your own whenever you like.
Nothing pasted yet. You need 8 at the least.
What to take from this
Five things worth knowing before you build.
- Write the rules from the messages, not from imagination.A rule invented at a desk covers the case you were already worried about. A rule written from ten real messages covers the one that actually keeps arriving. That is why this starts with your inbox and not a template.
- Start with two request types, not eight.Pick the two that eat the most of your week and make them reliable before you add a third. A router that handles two types well is worth more than one that handles eight badly.
- The AI reads. A rule decides.Let the model pull out what is being asked and what is missing. Do not let it set the priority or choose the route. A rule can be read, changed in a minute, and shown to a client. A model's mood cannot.
- Keep a never-decide list, and keep it short.Anything involving a refund, a complaint, a legal term or a person's conduct goes to a human first, every time, however sure the machine sounds. That list is what makes the rest safe to hand over.
- Shadow it before you trust it.Run it beside your own handling for a few days and count where it agreed. Trust it for the request types that match and keep reviewing the ones that do not.
Where can I help you?
You can do all of this alone with the prompts above. These are the places people usually want a second pair of hands.