Enquiry Triage and Routing: Stop Losing Leads in a Shared Inbox

If enquiries keep slipping through your company, the fix is not a bigger inbox or a louder reminder culture. It is triage: every incoming message gets classified, assigned to one named owner, and given a response deadline within minutes of arrival. Routing is the mechanical half of that. Most Singapore SMEs already have the channels — sales@, a WhatsApp Business number, a website form, the boss's personal handphone — but no rule that decides who owns what. Without that rule, ownership defaults to whoever happens to be looking, which means nobody.

Why does a shared inbox stop working at around ten people?

A shared inbox works when two people can see each other and say "you take that one." Past roughly ten staff, or past two channels, the informal handshake breaks in a specific way: everyone assumes someone else has replied. Psychologists call it diffusion of responsibility; in practice it looks like a quote request sitting unread for two days with three people having opened it.

The other failure is invisible. A shared inbox records that a message arrived and, sometimes, that someone replied. It does not record who was supposed to reply, by when, or whether the enquiry was even a sales enquiry. So when the month closes and enquiries are flat while marketing spend is up, there is no data to argue with — only recollection.

Where do enquiries actually go missing in a small company?

In our work with Singapore SMEs, leaked enquiries cluster in four places, and they are worth auditing before buying any software:

• The personal handphone. A long-standing customer WhatsApps the sales manager directly. It never touches a company system, so if that manager is on site, on leave, or has left the company, the enquiry and the relationship go with them.
• The ambiguous message. "Do you supply this?" is neither clearly a quote request nor clearly a support question, so it gets deferred, then forgotten. Ambiguity is the single largest category of dead enquiries we see.
• The handover gap. Admin receives the enquiry, forwards it to sales, and considers it done. Sales never confirms receipt. Nobody owns it during the gap.
• The after-the-first-reply silence. A quote goes out and then nothing. The enquiry is marked as handled because a reply was sent, but no follow-up was scheduled. Most lost revenue lives here, not in the first response.

What does a working triage rule set look like?

Keep it small enough to fit on one page. A workable set for a 12-person company has four categories and one rule each:

• New quote request — owner is the duty salesperson for that day, acknowledge within 15 minutes during business hours, substantive quote within one working day.
• Existing order status — owner is operations, acknowledge within 30 minutes, ideally deflected to a self-service link.
• Complaint or defect — owner is the manager on duty, acknowledge within 15 minutes regardless of channel, logged even if resolved verbally.
• Everything else — goes to a named person, not a queue. Someone must be accountable for deciding what unclear messages are.

Two structural rules matter more than the categories. First, a duty roster: one person is the default owner each day, published in advance, so the answer to "who takes this?" is never a discussion. Second, acknowledgement is a distinct step from resolution. Telling a customer "received, quoting you by tomorrow noon" takes twenty seconds and removes the pressure that makes staff avoid opening hard enquiries at all.

Should a person or a system do the routing?

Start with a person and a written rule, then automate the parts that have proven stable. The common mistake is the reverse — buying a CRM with routing rules before anyone has agreed what the categories are, then configuring the vendor's assumptions into your business.

Once the rules are stable for a month, automation earns its place in three specific spots: capturing every channel into one system so the personal handphone stops being a black hole; auto-assigning by rule so no human decides routine ownership; and escalating on a timer so an unacknowledged enquiry surfaces to a manager rather than aging silently. Those three are worth paying for. Sentiment scoring, lead grading and AI summarisation are not, until the basics hold.

One compliance note: the moment you consolidate enquiries into a system, you are holding customer personal data in a new place. Confirm where it is stored, who can export it, and how long it is retained — your data protection officer obligations under the PDPA do not pause because the tool is cheap.

How do you know the triage is working?

Two numbers, reviewed weekly. Unowned enquiry count: how many enquiries in the last seven days had no assigned owner within 15 minutes. The target is zero, and in a functioning system it genuinely reaches zero. Acknowledgement rate within your stated window: the percentage of enquiries that got a human acknowledgement inside the promised time. Most SMEs discover their real rate is between 50 and 70 percent when they first measure it, which is precisely why revenue feels random.

Resist tracking ten metrics. If those two improve, conversion improves; if they do not, no dashboard will save you.

What should you change this quarter?

Before December volume arrives, do three things. Route the personal handphone traffic into a company number, even if the transition takes a month of telling regular customers. Publish a duty roster through year-end, including the Deepavali and Christmas gaps. Then count, by hand for one week, how many enquiries went unacknowledged past your target window. That manual count is the business case — it usually costs less than an hour and reliably changes the owner's mind about whether this is a real problem.

Frequently asked questions

Do we need a CRM to do enquiry triage properly?

No. A duty roster, four written categories and a shared log will fix most of the leakage in a company under thirty people. A CRM becomes worthwhile when volume makes manual assignment a bottleneck, or when you need the audit trail. Buy it after the rules work, not to create them.

How do we handle enquiries that arrive on a staff member's personal WhatsApp?

Treat it as a migration, not a ban. Set up a company WhatsApp Business number, have staff reply from the personal number once with the new contact, and forward the existing thread into the company system. Expect two to three months for regular customers to switch, and accept that a handful never will — those relationships need a named backup owner instead.

What is a realistic acknowledgement window for a small team?

Fifteen minutes during business hours is achievable for a team of ten or more with a duty roster, because acknowledgement is not the same as answering. For teams under five, thirty minutes is honest. The important thing is publishing a window you actually meet — a promised four hours that you hit consistently beats a promised fifteen minutes that you miss half the time.