The after-hours problem: who answers when your business sleeps?
Your customers do not keep your office hours. The booking enquiry arrives at 9pm from someone’s sofa; the leak gets reported at midnight; the urgent question lands on a Sunday. Whatever answers in those hours — or fails to — is speaking for your business.
Enquiries don’t keep office hours
Think about when people actually deal with their own admin: evenings, weekends, lunch breaks. The person researching a treatment at a med spa is browsing at night and will book with whoever responds first. The tenant reporting a burst pipe to a property manager cannot wait for reception to open.
By morning, the booking enquiry has often gone to a competitor and the small leak has become a large one. The cost of silence is highest precisely when nobody is watching.
What do businesses try — and where does it fall short?
Most businesses have attempted an answer to this. The common options each leave a gap:
Every option shares the same flaw: the thing answering after hours knows nothing about your actual services, prices and procedures — or knows nothing at all.
- Nothing but voicemail: cheapest, and the message received is “we’ll get to you when it suits us” — if the caller leaves a message at all.
- An answering service: a human voice, but one that can only take a note. Nothing is resolved, and the note still needs triaging in the morning.
- A generic chatbot: available around the clock, but ungrounded — it deflects with FAQs at best and invents answers at worst, with no record and no owner.
- Rotating on-call staff: workable for genuine emergencies, corrosive as a way to answer routine questions at midnight.
What changes when routine requests resolve at any hour?
The useful distinction is not day versus night — it is routine versus exceptional. Most after-hours traffic is routine: opening times, booking and rescheduling, status checks, questions your website already half-answers.
ReQuest DESK handles those from your own published knowledge base and catalog, and only from that — if the answer is not something you have published, the system does not improvise. Built-in booking means the 9pm enquiry becomes a confirmed appointment, not a note. Email, web portal, chat widget, WhatsApp and transcribed voice all feed one classifier, so it does not matter which channel the night owl picks.
Autonomy is set per step of each request type, so you decide what may resolve unattended overnight and what waits behind an approval gate — the governance controls apply at 2am exactly as they do at 2pm.
The morning after looks different
Exceptions do not disappear — they queue properly. The genuinely unusual request waits for the morning classified, summarised and logged with an owner, timestamps and a committed resolution time, so your team starts the day working a prioritised queue instead of excavating an inbox.
The midnight leak arrives triaged with the tenant’s details and history attached; the odd query sits behind the urgent one instead of beside it. Compare that with the true price of the alternative — the real cost of a missed customer request — and after-hours coverage stops looking like a luxury.
Your people still make every judgement call that needs one. They just stop paying for the night shift with their mornings.
The service layer you never had time to build — live in days.
Describe what you do — ReQuest builds the catalog, answers the routine, and routes the exceptions to your team.