Nights and weekends are not an edge case for a company with customers in more than one country — they are most of the clock. The question is not whether to cover them, but whether covering them has to mean paying people to be awake.
The workable answer is a split: documented questions answered immediately at any hour, judgement calls queued for the morning with everything the team needs to pick them up.
Most of Your Inbox Arrives When Nobody Is Working
Support volume follows your customers' working day, not yours. For a business selling into more than one region, the majority of questions land outside a single nine-to-eighteen window — and those customers wait the longest for the least complicated answers.
Illustrative distribution for a business selling into several regions, not a measurement of a specific account.
What AI Should Answer at 03:00, and What Should Wait
The split is not about difficulty. It is about whether the answer is already written down and whether being wrong costs money.
Answer immediately
- How-to questions covered by the documentation
- Plan limits, pricing and feature availability
- Order status, delivery windows, return eligibility
- Setup, integration and API key troubleshooting
Acknowledge and queue
- Billing disputes and anything about a charge
- Refund exceptions and goodwill decisions
- Account security, access recovery, suspected compromise
- Anything a customer has already escalated once
Handing the Night to the Morning Shift
The value of after-hours coverage is destroyed if the team arrives to an undifferentiated pile. The queue needs to be sorted before anyone reads it.
- Acknowledge with a real expectation — “A human will pick this up when the team starts at 09:00 CET” beats silence and beats a fake promise of an immediate reply.
- Keep the full transcript with the handoff — The morning agent should never have to ask the customer to repeat themselves.
- Tag by topic and urgency at capture time — Billing, security and outage-shaped reports should sort to the top automatically.
- Start the SLA clock at the customer's message — Not at the moment a human opened it, or the metric flatters you and the customer knows better.
Coverage Without a Rota
Prerequisites for unattended hours
- Top after-hours questions tested against the live assistant
- Explicit refusal behaviour on money, security and account access
- Acknowledgement copy that names a real start time
- Escalation queue tagged and prioritised at capture
- On-call path for genuine incidents, separate from support
- Weekly review of what the assistant could not answer
- Timezone-correct working hours published on the contact page