The enquiry is in the inbox. Behind forty other emails.
A shared inbox where real enquiries sit behind supplier notifications, spam and internal traffic is not an admin problem — it is a lead-loss problem in an admin costume. Triage sorts and routes before a human reads, so the enquiry that matters surfaces in minutes rather than after close of business.
What triage actually does
Sorts by what the message is, routes it to whoever handles that, and flags the ones that look time-sensitive. It does not reply, and we would push back on building one that does.
This is one of the genuine AI cases: the input is unstructured, the volume is high, the judgement is shallow, and a mistake is cheap and visible. That combination is rarer than the market suggests, and it is exactly the test on the AI tools page.
- KNDR·01ClassifyNew enquiry, existing job, supplier, invoice query, noise. Five buckets covers most inboxes.
- KNDR·02RouteTo the person who handles that category, rather than to everyone or to whoever looks first.
- KNDR·03Flag urgencyA burst pipe reads differently from a quote request. The distinction is learnable and worth learning.
- KNDR·04Escalate silenceAn enquiry with no response after a set time comes back louder. This catches the ones that fall through.
Why it should not reply
An auto-reply to a genuine enquiry is worse than a slow human reply, because it tells the customer they have reached a machine and their actual question is still queued.
The value is in the sorting and the speed to a human, not in removing the human. If a customer would be annoyed to learn a machine handled it, that is your answer — and for a first enquiry, most would be.
What it will not fix
An inbox nobody is accountable for. If four people can see it and none of them owns it, triage produces beautifully sorted mail that still nobody answers.
It also will not fix volume caused by a broken process upstream. Twenty emails a week asking "where is my job up to" is a status-visibility problem, not an inbox problem, and fixing it upstream removes the messages entirely rather than sorting them faster.
Where this does not pay
Under about thirty messages a day, a person skimming is genuinely faster and cheaper than anything we would build. The threshold is volume, not frustration — and frustration arrives well before the volume justifies a build.
It also does not pay when the inbox is one person’s and they are good at it. You are automating a solved problem, and the money belongs somewhere else — count the alternatives first.
There is a cheaper first move worth trying before any of this: separate the addresses. Suppliers to one, enquiries to another, accounts to a third. It costs nothing, takes an afternoon, and resolves a surprising share of what looks like a triage problem. We would rather you did that and did not need us.
If it does not resolve it, the volume is real and worth costing. Structured intake pairs naturally with triage, because an enquiry that arrives complete is also easier to route.
What we have not measured, and what we would measure for you
There is no reliable published Australian figure for how long inbox sorting and enquiry routing takes in a small business, and we are not going to borrow one from a vendor whitepaper to make this page more persuasive. Most numbers you will see quoted for this were produced by companies selling the fix.
What we would do instead is count it on one of your jobs. Follow a single job end to end, note every time a human touches this step, and multiply by what that person costs loaded. That is a real number about your business and it takes an afternoon.
You can run the arithmetic yourself first — the leak calculator uses ABS, Average Weekly Earnings, Australia, May 2026 for the wage default and ATO, Super guarantee, current rate for super, and returns a range rather than a single confident figure. If the range comes back under our minimum engagement, that is a real answer and you should stop there.
The questions people actually ask.
01Can it just answer the simple ones?
It can, and we will argue against it for first enquiries. For an existing customer asking a factual question about a job, that is different and worth building. The line is whether the person is deciding whether to trust you.
02Where are your case studies?
Not published, because we do not have measured before-and-after numbers we can stand behind yet, and a case study without them is a story. Kindra AI was founded in 2025. When the measurements exist they will appear here with the sample size attached.
Stop bending.
Start shipping.
Bring the one flow that keeps costing you a Tuesday afternoon. We map it live and tell you what we'd build, what we wouldn't, and what it costs.