The same message at eleven at night, and five different right answers

Out of hours handling gets designed once, from the point of view of the business writing it, and it usually reflects that business's most common evening message. Everything else gets the same treatment because there is only one treatment.

The useful exercise is to hold the software constant and vary the business. Same widget, same form, same confirmation email, same reply in the morning. Then ask, in five different trades, what genuinely needed to happen between eleven at night and eleven the next morning. The answers have almost nothing in common, and the differences are not about how warm the wording is.

What follows is five concrete cases. None of them is unusual. All of them arrive at eleven at night regularly, and in most of these businesses nobody has ever written down which is which.

A tenant messages to say water is coming through the ceiling of the flat below. What the next twelve hours need is not an appointment. It is containment: stopping the water, keeping people away from anything electrical underneath it, and getting somebody out before the ceiling comes down.

There is a real distinction in this trade between a repair request and a habitability event, and in most places it carries duties rather than just expectations. A blocked gutter can wait until Monday. Water entering a property, no heating in winter, a failed lock on a front door, a suspected gas smell: these are a different category, and the category is defined by law and by the tenancy agreement rather than by how upset the person sounds.

So the right handling has two parts. Name the out of hours contractor route, if there is one, in the first line, so the tenant does not read a paragraph before finding it. And give the immediate instruction, which the business already has written down somewhere: stop the water at the stopcock, do not use the lights in that room. That instruction is published material. It can be given without anybody assessing anything, and it is the part that reduces the damage before anyone arrives.

An owner messages describing what their dog has eaten, or how it is breathing, or that it has not moved for an hour. Here the twelve hours are the entire question, because some presentations are hours critical and the owner has no way to tell which.

The practice cannot triage from a message and, more importantly, must not appear to be triaging. The correct output is the emergency route, first, before anything else in the message, with a refusal to assess and a plain statement that the assessment has to be done by a person on the phone or in the room.

Two specific dangers here, both of which come from trying to be helpful. Reassurance is the first: anything resembling most cases like that are fine will be read as clinical advice, by somebody who very much wants it to be, and it may keep them at home for the hours that mattered. The second is asking for more detail. A follow up question about symptoms implies that the answer will be used to assess, and it costs minutes at eleven at night. Do not ask. Route.

Somebody messages at eleven at night asking whether the date is still free, what is included, or whether the numbers can change later. Operationally nothing has to happen in the next twelve hours at all. Nothing gets worse overnight. By the ordinary definition of urgency this is the lowest priority message of the five.

It is also, in commercial terms, the most valuable, and it is the one most likely to be handled badly, because the out of hours design was built around emergencies and this is not one. The couple are making a large, infrequent, anxious decision and they are doing it in the evening because that is when they have time. They are almost certainly messaging several venues in the same hour.

The right handling is to answer the answerable part immediately from published material, because most of what they asked is on the site somewhere: capacity, what the fee includes, how dates are held, when a deposit is due. Then give a named person and a specific time for the part that needs a person. What loses this enquiry is not a slow reply, it is a contentless one, because the venue that answered three of their four questions at eleven at night is the one they think about in the morning.

A message says half the house has no power and a switch keeps tripping. The fork here is between safety and scheduling, and it is a genuine fork rather than a matter of degree.

A burning smell, scorch marks, water anywhere near the board, exposed conductors, or anybody having had a shock is not a job booking. It has its own route, and in many places part of that route is a national or network operator number rather than the electrician's. That number belongs in the published wording, checked, because the customer will not find it themselves at eleven at night.

Everything else is a first thing tomorrow slot, and what the twelve hours need is a time window and an honest one. A sole trader or a small firm has a real capacity and a real first appointment, and saying we will fit you in tomorrow when tomorrow is genuinely full converts a manageable inconvenience into a complaint. One more constraint worth designing for: this customer is holding a torch and typing on a phone with one hand. Whatever the message says has to work in two lines.

Somebody messages at eleven at night to ask where their order is. Nothing has to happen before morning. The parcel is where it is. A form, an honest reply time and a link to the tracking is entirely sufficient, and this is the case where over engineering the out of hours handling is the actual mistake. Most evening messages in most retail businesses are this one.

But there is a variant hidden inside it that is genuinely time bound, and it is easy to miss because it arrives looking identical. The customer who wants to change or cancel before dispatch. That has a deadline, and the deadline is whenever the warehouse or the person with the parcels starts picking in the morning, which is usually before anybody reads the inbox.

So the shop has one real out of hours design problem, and it is small and specific. Either publish the cutoff and what to do before it, or make sure the messages are checked before the pick rather than after. A cancellation request that arrives at eleven and is read at ten is a refund, a return label, and a customer who told you in good time and was ignored.

Urgency is not a property of the message. It is a property of what will have changed by morning, and that is a fact about the business rather than about the person typing.

Three questions define it, and they can be answered for any trade in about ten minutes. What gets materially worse if nobody acts before morning. What becomes impossible after a particular hour tomorrow. And what is simply uncomfortable to wait for. Only the first two justify a route out of hours. The third needs a time and nothing else, and giving it a route wastes the route.

Notice that the five cases distribute across all three. The letting agent and the vet are in the first bucket. The shop's cancellation and the electrician's booking are in the second, with a specific hour attached. The venue and the shop's ordinary tracking question are in the third. A single out of hours design cannot serve all three, which is why so many of them serve one and fail the other two silently.

Take a month of messages that arrived outside your working hours. Not a sample, the whole month, because the point is the distribution. Sort each one into the three buckets: gets worse overnight, has a deadline tomorrow, merely waits.

Most businesses find one bucket they have never designed for. Frequently it is the second, because deadlines are invisible from inside the business. Everybody knows the picking starts at eight, or that the court list is set at nine, or that the delivery run is planned the night before, and nobody has ever written it down for a customer.

Then write the route for the buckets that need one, or write the sentence that admits there is not one. Both are legitimate. What is not legitimate is a form that implies somebody is watching, sent to a person in the first bucket, who then waits.