Probably not a team. Almost certainly the coverage.
Those are different things, and conflating them is why this question usually gets answered with either an expensive night shift or nothing at all.
Check before you decide
Most operators guess at their out-of-hours volume. You do not have to.
Pull last month's inbound across every channel and count what arrived outside your staffed hours. In consumer-facing businesses it is routinely a third or more, concentrated in evenings and Sunday afternoons.
That is not a small tail. It is a meaningful proportion of your customer contact, and right now it hits a closed door.
Why it costs more than it looks
The response-time data is unambiguous, and it is worse than most people expect.
Around 89% of customers expect a response within an hour. One analysis found sub-one-hour response achieved 71% retention against 48% for a 24-hour response, which is a 23-point gap created by speed alone. Satisfaction tracks the same curve, from roughly 92% at sub-five-minute response down to about 51% at a day.
Now apply that to an enquiry arriving at 9pm on a Sunday. By the time anyone reads it on Monday morning, you are already at the wrong end of every one of those curves.
On the acquisition side it is starker still. Leads contacted within five minutes are far more likely to qualify than leads contacted after thirty, and roughly 35 to 50% of sales go to whoever responds first. The Sunday-evening prospect comparing three providers has signed with one of them by Tuesday.
The thing people miss
The alternative to an agent handling the 9pm question is not a slower human.
It is nobody, until tomorrow.
That is what makes out-of-hours the strongest single case for automation in most operations. During working hours an agent competes with your team and has to be better than them at something. Outside them it competes with silence.
Where a night shift is still right
Where the contact genuinely needs judgment.
Emergency faults with a safety dimension. Anything involving vulnerability or a duty of care. Regulated situations with a response obligation. Sectors where an out-of-hours call is by definition serious rather than routine.
The mistake is staffing overnight to answer questions with a single correct answer. That is an expensive way to do something a system does better, and the people doing it get bored and leave.
What good coverage actually looks like
Answer what can be answered, properly, with real data rather than a holding line.
Be straight about what cannot wait and what can. "This needs someone from the faults team and they start at eight, I have logged everything and they will have it first thing" is a genuine service. An auto-reply promising contact within one working day is not, and customers read it as a queue.
And make sure the morning team inherits something useful. The value of overnight coverage is not only the customers you resolved. It is that your team starts the day with context instead of a wall of unread messages.
