Playbook

Sorting the urgent job from the tyre kicker before you pick up the phone

By David Saleh · Silas Main · 17 July 2026

A tradie's office manager opens the inbox on a Monday morning. Every enquiry looks the same at first glance: a subject line that says "QUOTE REQUEST", a sender address that says "noreply@" something, no name attached anywhere in the list view.

One of those emails is a burst pipe flooding someone's kitchen. Another is a homeowner three months out from a renovation, gathering quotes to compare. From the inbox list, they are identical. You only find out which is which by opening every single one, in order, and reading it properly.

That's not an inbox problem. That's a triage problem. And it's the same problem whether the enquiries land by phone, form, or email.

The real cost isn't the volume

Most small business owners think the fix for a full inbox is "answer faster" or "hire someone to answer it." Neither is quite right.

The actual cost is decision fatigue applied to the wrong thing. Every enquiry demands the same amount of attention to sort as it does to answer, because you can't tell what it is until you've read it. So the emergency sits in the queue behind four requests for a quote on a job that might happen next year. Nobody chose that order. It's just the order things arrived.

A plumbing business we worked with had exactly this shape of problem. Every job enquiry, real emergency or idle curiosity, arrived looking the same: same generic sender, same generic subject line, buried among supplier invoices and platform notifications. The person answering the phone and the inbox was doing triage in her head, all day, on top of everything else her job actually was.

The fix wasn't a bigger team. It was a sort, done before a human ever opens the message.

Six buckets, not one inbox

The system we built reads every new email and drops it into one of six buckets before anyone sees it:

Emergency. Burst pipe, no hot water, flooding, anything where the job can't wait. These get flagged the moment they land.

New job. A new customer describing work they want done, no history with the business.

Existing customer. Someone referencing a past job, an invoice, or a name the team already knows.

Out of scope. Real enquiries, just not work this business does.

Supplier or admin. Invoices, platform notifications, anything that isn't a customer.

Spam or FYI. Cold pitches, newsletters, noise.

Nothing here is complicated. It's the same sort an experienced office manager already does in her head, every time she opens the inbox. The difference is it happens automatically, on every single message, the second it arrives, not squeezed in between everything else on her plate.

The rule that makes this safe to run

Here's the part that matters more than the sorting: nothing gets sent to a customer without a human reading it first.

The system drafts a suggested reply. It never sends one. A person still checks every flagged message, still writes the actual words a customer receives, still makes the call on price and timing. The sort just means she's reading the right message first, not whichever one happened to land at the top of the pile.

There's a second layer under that, and it's the one most triage builds skip: before drafting anything, check whether a human has already answered. If someone in the business has replied to that thread, or marked it handled, the system leaves it alone. No draft, no flag, no noise. Nothing is more useless than a tool that talks over the top of a reply that's already gone out.

That single check is why this holds up in a live business instead of just looking good in a demo. A tool that drafts a reply to an enquiry someone already answered isn't saving time. It's creating a second job: checking whether the tool's version needs deleting.

What actually changes

The inbox stops being one undifferentiated wall of messages. It becomes a short list, already sorted, with the one thing that can't wait sitting at the top where it belongs.

The system rereads the inbox every fifteen minutes. That's frequent enough that an emergency doesn't sit unseen for an hour, and infrequent enough that it isn't hammering the mailbox for no reason. Fifteen minutes is a number you can set for your own business, faster if you're in a trade where an hour matters, slower if it doesn't.

None of this replaces judgment. It replaces the part of the job that isn't judgment: reading forty identical-looking subject lines to find the one that's actually on fire.

What this pack gives you

Below is the actual prompt, written to run over any inbox, any AI tool that can read text. It's built to be specific to your business before you run it: your emergency triggers, your scope, your response window. Fill those in once. Then paste an email in and get back a bucket, a reason, and a safe first line, never a full reply, never a price you didn't confirm, never a promise the tool made up on your behalf.

There's also a one-page worksheet, because the prompt is only as good as the answers you give it about your own business. Fill it out before the first run.

None of it needs new software to start. Copy the prompt into whatever AI tool you already have open, paste an email in, read the answer. If it's useful after the first ten emails, then talk to us about wiring it to run itself every fifteen minutes without you touching it.

The prompts

You are the first read on the inbox for [BUSINESS NAME], a [TRADE OR INDUSTRY] business in [SUBURB OR CITY]. You are not replying to anyone yet. Your only job is to sort.

Read the email below and sort it into exactly one of these six buckets:

1. EMERGENCY: anything matching: [LIST YOUR EMERGENCY TRIGGERS, e.g. "burst pipe", "no power", "flooding", "gas smell", "can't get in the house"]. Words like "urgent" or "ASAP" only count here if they're attached to a real problem, not a sales pitch.
2. NEW JOB: a new customer describing work they want done, with no sign they've dealt with you before.
3. EXISTING CUSTOMER: anyone referencing a job number, a previous visit, an invoice, or a name your team would recognise.
4. OUT OF SCOPE: real enquiries for work you don't do. What you do is: [LIST YOUR SERVICES]. Anything clearly outside that.
5. SUPPLIER OR ADMIN: invoices, supplier updates, platform notifications, anything not from a customer.
6. SPAM OR FYI: marketing, cold pitches, newsletters.

For the email below, output exactly this:

BUCKET: [one of the six]
WHY: one plain sentence, no jargon
SUGGESTED FIRST LINE: only for buckets 1 to 4. A short, human opening reply. Not a full reply. Do not state a price, a callout fee, or an appointment time unless I've told you what those are below. If you don't have enough to answer, the line asks a clarifying question or says someone will call back within [YOUR RESPONSE WINDOW, e.g. "2 business hours"].
FLAG FOR HUMAN: yes or no. Always yes for EMERGENCY.

If the email doesn't say enough to sort with confidence, pick the closest bucket and say so plainly in WHY. Do not guess at facts that aren't in the email.

Here is the email:
[PASTE EMAIL HERE]

Questions

Adelaide · ACST · ABN 17 626 827 646