Why “always online” beats “always staffed” for customer support

Extending your hours is a rota problem with a salary attached. Being answerable at 11pm is a different problem with a different solution.

Every growing business eventually has the same meeting. Messages are arriving in the evening, at weekends, from customers in another timezone. Somebody proposes extending the hours.

It is the obvious answer and usually the wrong one, because it treats availability as a staffing problem. It is not. They are two different problems that happen to share a symptom.

The arithmetic of a rota

Covering evenings and weekends properly means people working them. Not one person on call — a rota, with cover for illness and holiday, which in practice means two or three.

Then look at what those hours actually contain. In most consumer businesses the out-of-hours queue is dominated by the same handful of questions: are you open, do you have it, how much is it, where is my order, do you do X.

You are now paying a salary premium for unsocial hours so that a person can type an answer that has not changed in six months.

That is the real objection to “always staffed”. Not that it is expensive — that it is expensive and it spends the expensive resource on the cheap work.

The two things that are actually being asked for

Unpick “we need to be available” and there are two separate requests hiding in it.

Availability is: a customer who writes at 11pm gets a useful answer at 11pm. Most of the time this is a fact they need — a fact you already know and have written down somewhere.

Coverage is: a customer with a real problem at 11pm reaches a person who can solve it. A complaint, a booking going wrong, something outside policy.

These have different volumes, different costs, and different right answers. Conflating them is what makes the meeting go in circles.

Availability is a software problem

If the question is a fact you maintain — hours, price, availability, order status, whether you do the thing — then answering it instantly at any hour is something software does correctly and cheaply.

The thing to insist on, and the reason this ever goes wrong, is that the answer must come from your real information. Your actual calendar, your actual price list, your actual policy. An agent that improvises at 11pm creates a problem your team discovers at 9am, and one of those costs more than the rota would have.

The correct behaviour at the edge of what it knows is to say so and take a message, not to guess. “Always online” does not mean “always answers” — it means never leaving someone in silence.

Coverage is a staffing problem — a much smaller one

Once availability is handled, look at what is actually left overnight. It is usually a very short list, and it is almost always things where a person genuinely changes the outcome.

That is a rota you can afford, because it is scoped to the exceptions rather than the volume. And it is a better job: nobody is being paid a night premium to paste an opening-hours reply.

How to tell which one you have

Take a month of out-of-hours messages and sort them into three piles:

  1. A fact you already have written down. This is usually the large majority, and all of it is availability.
  2. Something a person must decide. Complaints, exceptions, anything touching money or a promise. This is your coverage, and its size is the real input to the staffing question.
  3. Things nobody can answer at any hour. Worth noticing separately — these are process gaps that daylight hours hide.

Most teams are surprised by how lopsided the first pile is, and by how small the second one is once it is separated out.

What this changes about the decision

The meeting usually frames it as “can we afford to extend hours?” The better question is “how much of the out-of-hours queue actually needs a human, and are we willing to pay for that much cover?”

Answered that way, most businesses find they need availability immediately and coverage rarely — and that they were about to buy the expensive one to solve the cheap one.

The thing worth protecting

Being answerable at any hour is not only a cost question. A customer deciding between you and someone else at 9pm on a Sunday does not wait until Monday to decide. They ask both, and they buy from whoever answered.

That is the argument for availability, and it does not require anyone to work a Sunday.


Fellix answers the repetitive half at any hour from your own information, and escalates the rest to a person with the whole conversation attached. See what that is worth on your numbers.