It rarely starts with a decision. Someone on the team replies to a customer at 9.40pm because they happened to see the notification. The customer is delighted. The next week, two more people do the same. Within a few months there is an unspoken rule that somebody always answers, and nobody can quite say who agreed to it.
That is how 24/7 availability burnout usually arrives in small businesses: not as a policy, but as a habit that nobody switched off. The customer experience looks great from the outside. Inside, the office manager is checking her phone during her daughter's swimming lesson, and the junior who does not reply at night is quietly seen as less committed.
Customers do value fast responses at any hour. The mistake is assuming that means a person must provide them.
What always-on actually costs the people doing it
The obvious cost is hours. The less obvious costs are the ones that make good staff leave.
- No real evenings. Even when no message arrives, the possibility of one keeps people half at work. A quiet night spent checking is not a night off.
- Unfair distribution. It is almost always the most conscientious people who pick up the slack, which means you slowly burn out your best staff first.
- Worse replies. A message typed on a phone at 10pm, without the customer record in front of you, is more likely to promise the wrong thing.
- Resentment that nobody voices. Unpaid, unacknowledged evening work is a common reason people describe a job as draining, even when the daytime work is fine.
None of this shows up in a customer satisfaction score until someone hands in their notice.
Separate the response from the responder
The useful distinction is between a customer getting a response and a person responding. Most of what customers need at 11pm is the first: confirmation the message landed, an answer to a factual question, and a clear idea of what happens next.
Here is a working split for a typical service business. Adjust the lines for yours.
| Task | Software, any hour | A person, set hours |
|---|---|---|
| Acknowledge a new enquiry | Yes, instantly | No need |
| Answer prices, hours, areas, process | Yes, from your content | Only for exceptions |
| Capture name, contact and job details | Yes | Reviews in the morning |
| Open a support ticket for a problem | Yes, numbered and logged | Resolves it |
| Agree a discount or exception | No | Yes |
| Handle a distressed or angry customer | Acknowledge and log only | Yes |
| Genuine emergency | Give the emergency route immediately | On-call person, if you run one |
| Confirm a booking or arrival time | No, request only | Yes |
A website assistant such as SpideyChat covers the left column: it answers from your content, captures leads, opens numbered tickets and records the questions it could not answer. It does not make judgement calls, and it should not be set up to try. For a fuller comparison of cheaper options, the cheapest way to cover after-hours enquiries lays them out.
Write the availability policy nobody wrote
Most after-hours messaging continues because the expectation was never written down. A short policy, one page at most, ends the guessing. Here is how to put one together.
- State the hours a person responds. For example, weekdays 8am to 6pm and Saturday mornings. Outside those, replies wait unless something is on the emergency list.
- Define the emergency list. Specific situations only, such as a safety risk on a job you completed or a system outage for a contracted client. "The customer seemed keen" is not on it.
- Decide whether anyone is on call. If yes, it rotates, it is paid or given back as time off, and it has an end time. If no, say so, and say that nobody is expected to check.
- Tell customers the same thing. Your website, auto replies and assistant should all state when a person will pick up messages. Setting reply-time expectations covers the wording.
- Remove the social pressure. Managers go first. If the owner replies to the team chat at 11pm, everyone else learns that is the real rule, whatever the policy says.
- Review after a month. Look at what arrived overnight and what, if anything, genuinely could not wait. Tighten or loosen the emergency list based on that, not on anxiety.
Make the morning handover do the heavy lifting
The reason people reply at night is often fear of the morning pile. If Tuesday starts with forty unread messages in four places, answering a few on Monday evening feels like self-defence.
Fix the morning and the evenings take care of themselves. Overnight enquiries should arrive in one inbox, already sorted into leads and tickets, each with the conversation attached so nobody has to ask the customer to repeat themselves. Unanswered questions should be listed so someone can add the missing content once rather than answering the same thing ten times.
Give one person the first 30 minutes of the day to work that queue, and protect that time. Clearing the Monday backlog has a routine for the heaviest morning of the week.
When a person really should be on call
Some businesses cannot avoid it: emergency trades, property managers with tenants, IT support with contracted response times. Software does not change that, but it can shrink what reaches the on-call phone.
In that case, let the assistant give the emergency route and handle everything routine, so the on-call person is woken for burst pipes and server outages, not for someone asking about next month's prices. The difference between being on call for everything and being on call for real emergencies is the difference between a tolerable rota and one people dread.
A first step you can take on Monday
Ask your team, privately, how often they check work messages outside hours and whether they feel they have to. The answers will tell you how big the problem is better than any policy template.
Then draft the one-page availability policy above, with the emergency list, and agree it together. Once the human hours are clear, look at what could answer customers instantly in the gaps: a better FAQ, a free AI FAQ generator to get it started, or a website assistant trained on that content.