Key takeaways<\/h2>\n\n\n\n\n- Silence is a choice, and it is the only option with no upside.<\/strong> Stated hours cost nothing and are experienced as service.<\/li>\n\n\n
- Four honest models: stated hours, AI answering from your docs, an on-call rota, or follow-the-sun.<\/li>\n\n\n
- Most overnight volume is order status, shipping and stock – all answerable without a person.<\/li>\n\n\n
- The holding message must contain a time, not a \u201csoon\u201d.<\/li>\n\n\n
- Queue what cannot be answered, with a named owner for the morning, not a shared pile.<\/li>\n\n\n
- Refunds and complaints should wait for a person rather than get an automated attempt.<\/li>\n\n<\/ul>\n\n<\/div>\n\n\n\n
What Arrives After Dark<\/h2>\n\n\n\n
Worth looking before deciding, because the mix is friendlier than people assume.<\/p>\n\n\n\n
Mostly Questions With Answers<\/h3>\n\n\n\n
Pull a month of overnight messages and sort them. In most businesses the top three are order status, shipping questions and stock or sizing – all of which have factual answers sitting in systems you already own.<\/p>\n\n\n\n
That is the useful discovery here: the overnight inbox is disproportionately the automatable part. The judgement-heavy conversations tend to arrive in working hours when people are at their desks.<\/p>\n\n\n\n
A Small, Genuinely Urgent Slice<\/h3>\n\n\n\n
Change or cancel an order before dispatch, a delivery arriving tomorrow, something going wrong with an event. Small in volume and real in consequence.<\/p>\n\n\n\n
This is the slice that justifies an on-call arrangement if you have one, and the slice that most needs an honest cut-off stated rather than a hopeful silence.<\/p>\n\n\n\n
And the Ones to Leave Alone<\/h3>\n\n\n\n
Refunds, damage, complaints. An automated attempt at these overnight is worse than an honest wait, because the customer is already unhappy and a bot reply reads as being fobbed off at the worst moment.<\/p>\n\n\n\n
Queue them to a named person for the morning. The rules for which these are belong in the escalation rules themselves<\/a>.<\/p>\n\n\n\n![\"The](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/after-hours-dm-support-night.jpg\")
Mostly questions with answers, which is why overnight automates well.<\/figcaption><\/figure>\n\n\n\nThe Four Models<\/h2>\n\n\n\n
In increasing order of cost. Most businesses should be on the first or second and are accidentally on none of them.<\/p>\n\n\n\n
Stated Hours, Honoured<\/h3>\n\n\n\n
Publish your hours, repeat them in the automatic holding message, and reply first thing. This is free, it is honest, and it is reliably experienced as better service than vague availability.<\/p>\n\n\n\n
The only requirement is meaning it. Stated hours you miss are worse than no stated hours, because you have now set and broken an expectation.<\/p>\n\n\n\n
AI Answering From Your Own Material<\/h3>\n\n\n\n
Overnight the automation answers from your documentation and catalogue, and queues anything it should not decide, so the morning starts with a list instead of a mess. This covers the majority of what arrives.<\/p>\n\n\n\n
Costs per message rather than per hour, which makes it cheap at small volume. Note it is not available on the WhatsApp channel – there the overnight layer is keyword-driven, which handles order status and shipping perfectly well.<\/p>\n\n\n\n
An On-Call Rota<\/h3>\n\n\n\n
A named person carries the phone for genuine emergencies, with a narrow written definition of emergency. Real cost, and not only in money – on-call wears people down and should be rotated and compensated.<\/p>\n\n\n\n
Worth it when overnight failures are expensive: events, perishables, travel, anything time-critical.<\/p>\n\n\n\n
Follow-the-Sun<\/h3>\n\n\n\n
A second team in a timezone where the sun is up. It works completely and it is a hiring project rather than a configuration change, so it belongs to a different conversation about scale.<\/p>\n\n\n\n
If you are considering it mainly for coverage rather than volume, the first two options will usually get you most of the benefit for none of the cost.<\/p>\n\n\n\n![\"Four](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/after-hours-dm-support-models.jpg\")
Plus the fifth one everybody actually does, which is the worst.<\/figcaption><\/figure>\n\n\n\nWriting the Holding Message<\/h2>\n\n\n\n
The highest-leverage sentence in this entire subject, and it is usually written badly.<\/p>\n\n\n\n
It Must Contain a Time<\/h3>\n\n\n\n
\u201cWe will get back to you soon\u201d tells the customer nothing and invites them to ask again somewhere else. \u201cWe are closed now and will reply before 10am\u201d is a different message entirely, and it costs the same.<\/p>\n\n\n\n
If you genuinely do not know, say the worst case. An honest \u201cwithin one working day\u201d beats an optimistic \u201cshortly\u201d because it can be met.<\/p>\n\n\n\n
It Should Say What It Can Do Now<\/h3>\n\n\n\n
Before the apology, offer the thing that is available: tracking, the returns process, the shipping page. A good share of overnight messages end there and never need the morning at all.<\/p>\n\n\n\n
On the free app layer the away message is one unconditional text for everyone, which is why pairing it with keyword answers matters – the distinction is in WhatsApp Business auto reply<\/a>.<\/p>\n\n\n\nIt Should Not Pretend<\/h3>\n\n\n\n
Nothing erodes trust faster than an overnight message written as though a person sent it, followed by nine hours of nothing. Be plainly automatic and plainly honest; people are entirely comfortable with that.<\/p>\n\n\n\n
Choosing Between Them<\/h2>\n\n\n\n
By what your business actually is, rather than by what sounds thorough.<\/p>\n\n\n\n
What Arrives After Dark<\/h2>\n\n\n\n
Worth looking before deciding, because the mix is friendlier than people assume.<\/p>\n\n\n\n
Mostly Questions With Answers<\/h3>\n\n\n\n
Pull a month of overnight messages and sort them. In most businesses the top three are order status, shipping questions and stock or sizing – all of which have factual answers sitting in systems you already own.<\/p>\n\n\n\n
That is the useful discovery here: the overnight inbox is disproportionately the automatable part. The judgement-heavy conversations tend to arrive in working hours when people are at their desks.<\/p>\n\n\n\n
A Small, Genuinely Urgent Slice<\/h3>\n\n\n\n
Change or cancel an order before dispatch, a delivery arriving tomorrow, something going wrong with an event. Small in volume and real in consequence.<\/p>\n\n\n\n
This is the slice that justifies an on-call arrangement if you have one, and the slice that most needs an honest cut-off stated rather than a hopeful silence.<\/p>\n\n\n\n
And the Ones to Leave Alone<\/h3>\n\n\n\n
Refunds, damage, complaints. An automated attempt at these overnight is worse than an honest wait, because the customer is already unhappy and a bot reply reads as being fobbed off at the worst moment.<\/p>\n\n\n\n
Queue them to a named person for the morning. The rules for which these are belong in the escalation rules themselves<\/a>.<\/p>\n\n\n\n In increasing order of cost. Most businesses should be on the first or second and are accidentally on none of them.<\/p>\n\n\n\n Publish your hours, repeat them in the automatic holding message, and reply first thing. This is free, it is honest, and it is reliably experienced as better service than vague availability.<\/p>\n\n\n\n The only requirement is meaning it. Stated hours you miss are worse than no stated hours, because you have now set and broken an expectation.<\/p>\n\n\n\n Overnight the automation answers from your documentation and catalogue, and queues anything it should not decide, so the morning starts with a list instead of a mess. This covers the majority of what arrives.<\/p>\n\n\n\n Costs per message rather than per hour, which makes it cheap at small volume. Note it is not available on the WhatsApp channel – there the overnight layer is keyword-driven, which handles order status and shipping perfectly well.<\/p>\n\n\n\n A named person carries the phone for genuine emergencies, with a narrow written definition of emergency. Real cost, and not only in money – on-call wears people down and should be rotated and compensated.<\/p>\n\n\n\n Worth it when overnight failures are expensive: events, perishables, travel, anything time-critical.<\/p>\n\n\n\n A second team in a timezone where the sun is up. It works completely and it is a hiring project rather than a configuration change, so it belongs to a different conversation about scale.<\/p>\n\n\n\n If you are considering it mainly for coverage rather than volume, the first two options will usually get you most of the benefit for none of the cost.<\/p>\n\n\n\n The highest-leverage sentence in this entire subject, and it is usually written badly.<\/p>\n\n\n\n \u201cWe will get back to you soon\u201d tells the customer nothing and invites them to ask again somewhere else. \u201cWe are closed now and will reply before 10am\u201d is a different message entirely, and it costs the same.<\/p>\n\n\n\n If you genuinely do not know, say the worst case. An honest \u201cwithin one working day\u201d beats an optimistic \u201cshortly\u201d because it can be met.<\/p>\n\n\n\n Before the apology, offer the thing that is available: tracking, the returns process, the shipping page. A good share of overnight messages end there and never need the morning at all.<\/p>\n\n\n\n On the free app layer the away message is one unconditional text for everyone, which is why pairing it with keyword answers matters – the distinction is in WhatsApp Business auto reply<\/a>.<\/p>\n\n\n\n Nothing erodes trust faster than an overnight message written as though a person sent it, followed by nine hours of nothing. Be plainly automatic and plainly honest; people are entirely comfortable with that.<\/p>\n\n\n\n By what your business actually is, rather than by what sounds thorough.<\/p>\n\n\n\nThe Four Models<\/h2>\n\n\n\n
Stated Hours, Honoured<\/h3>\n\n\n\n
AI Answering From Your Own Material<\/h3>\n\n\n\n
An On-Call Rota<\/h3>\n\n\n\n
Follow-the-Sun<\/h3>\n\n\n\n
Writing the Holding Message<\/h2>\n\n\n\n
It Must Contain a Time<\/h3>\n\n\n\n
It Should Say What It Can Do Now<\/h3>\n\n\n\n
It Should Not Pretend<\/h3>\n\n\n\n
Choosing Between Them<\/h2>\n\n\n\n