After-Hours Enquiry Coverage: Who Answers Your 9pm WhatsApp?

If a quote request lands in your WhatsApp at 9pm on a Saturday, the honest answer for most Singapore SMEs is that nothing happens until Monday morning — roughly 60 hours later. Proper after-hours enquiry handling does not mean paying someone to sit and watch the inbox all weekend. It means three things you can put in place this month: an automated acknowledgement that states a specific, keepable response time; a self-service layer that answers the four or five questions which make up most out-of-hours messages; and one narrow escalation rule that pulls genuinely urgent enquiries to a named mobile before the customer gives up and messages the next supplier on their list.

How much of the week is your inbox actually unattended?

Do the arithmetic before you argue about the solution. A business open 9am to 6pm, Monday to Friday, is attended for 45 hours out of the 168 hours in a week. That is 27% coverage — and 73% of the week with nobody reading anything.

The real figure is worse. Subtract lunch, site visits, meetings, annual leave and public holidays, and the window in which someone is genuinely watching an enquiry channel and able to reply within minutes is usually closer to 30 hours. Call it 18% of the week. Then add Q4: Deepavali, the December school holidays, year-end shutdowns and the staff who take their remaining leave in the last three weeks of the year. Coverage gets thinner in exactly the quarter when buyers are trying to close orders before their own financial year ends.

What actually happens to an enquiry that arrives on a Saturday night?

Two things, and neither is in your favour.

First, the buyer is almost never contacting only you. Someone sourcing a supplier on a weekend is working through a shortlist, and the first substantive reply anchors the conversation — it sets the specification, the comparison price and the perceived responsiveness of everyone who replies afterwards. Arriving third on Monday afternoon means responding to a frame someone else built.

Second, silence is read as an answer. A customer who hears nothing for two days does not conclude that you are closed. They conclude that you are busy, disorganised, or uninterested in a job their size. You will never see this in your data, because the enquiry that quietly goes elsewhere leaves no record in your system.

What can you automate tonight without pretending to be human?

The lowest-effort, highest-return change is an acknowledgement that contains information rather than reassurance. Most auto-replies say some version of "thank you for your message, we will get back to you soon." That sentence is worthless — it makes no commitment and answers no question.

A useful after-hours auto-reply does four jobs in under 60 words:

• States the actual response time. "Our team replies by 10am on the next working day" is better than "soon", provided you can keep it. Never publish a response time you miss more than one week in four.
• Says plainly that it is automated. Label it. A bot that impersonates a staff member converts a minor delay into a trust problem when the customer realises.
• Offers self-service for the predictable questions. Order status, delivery lead time, price list, opening hours, payment details and location cover the large majority of out-of-hours messages for most SMEs. A link or a numbered menu resolves these with no human involved.
• Gives one urgent path. A single line stating what counts as urgent and the number to call. Be specific, or everything becomes urgent.

One cost note if you run on the WhatsApp Business API: under Meta's per-message pricing, business-initiated template messages are chargeable while replies you send inside the 24-hour customer service window opened by an inbound message are not. An automated reply to a customer who just messaged you therefore costs nothing, whereas chasing that same person with a template on Monday costs money. Check the current rate card, but the structural incentive is clear — answer while the window is open.

Which enquiries deserve to interrupt someone's weekend?

Very few, and you should name them in writing rather than leave it to judgement. For most SMEs the list runs to two categories: a fault or breakdown affecting an existing customer's operations, and a delivery or installation scheduled for the next working day. Everything else waits.

Assign that duty to one named person per weekend on a published rota, compensate it properly, and route to a single mobile number rather than a group chat where responsibility evaporates. A rota of four people means one weekend a month each — manageable. An unwritten expectation that everyone stays reachable means nobody does.

How do you stop Monday becoming a pile-up?

Coverage without routing just moves the bottleneck. Tag each enquiry as it arrives — new enquiry, existing order, support, admin — and give each tag a single owner and a stated turnaround. On Monday, new enquiries and quote requests are worked before internal admin, because those are the only messages with revenue still attached to them. A shared inbox where four people can see everything and nobody owns anything reliably produces the twelve-hour reply.

How do you know whether it is working?

Five numbers, reviewed monthly:

• After-hours first-response time, measured separately for the automated acknowledgement and the first human reply.
• Deflection rate — the share of after-hours enquiries fully resolved by self-service with no human involvement.
• Weekend-origin conversion versus weekday-origin conversion. If weekend enquiries convert materially worse, your handover is leaking.
• Monday clearance time — how long until the weekend backlog is empty.
• Escalations per weekend. More than two or three suggests your urgency definition is too loose.

What should a 10-30 person SME do before December?

Four weeks is enough. Week one: pull the last 90 days of enquiries and count how many arrived outside office hours, and what they asked. Week two: write the auto-reply, the self-service answers for the top five questions, and the one-paragraph urgency definition. Week three: publish the rota, agree the compensation, and test the escalation path end to end with a real message. Week four: turn on measurement and set a monthly review.

That gets you to Q4 with the 73% covered — not perfectly, but visibly, and with a commitment you can keep.

Frequently asked questions

Is an automated reply really better than no reply at all?

Yes, provided it carries information and is honest about being automated. An acknowledgement that names a specific response time and resolves common questions holds the conversation open. An empty "we'll get back to you soon" adds nothing and is close to neutral — the harm comes from auto-replies that promise a two-hour turnaround you do not deliver.

Do we need the WhatsApp Business API, or is the free Business app enough?

The free app handles away messages, greeting messages and quick replies, which covers a single-inbox business adequately. You need the API when several staff must work the same number with proper assignment and audit history, when you want enquiries flowing into a CRM or order system, or when volume makes manual handling unworkable. Start with the free app and move when the constraint is real, not anticipated.

Is there any legal requirement to respond within a set time?

There is no general Singapore law setting commercial response times. There are specific obligations worth knowing: under the PDPA, an access or correction request must be answered as soon as reasonably possible, and if you cannot do so within 30 days you must tell the individual when you will. Treat enquiry response time as a commercial commitment you choose and publish — then hold yourself to it.