AI chat outside business hours: the night shift is a different job

Your shop is closed for most of the hours in a week. The assistant should not say the same things in both halves, and the difference is mostly about what it promises.

A shop that opens at 9 and closes at 6, five days a week, is open for 45 of the 168 hours in a week. For the other 123 the door is shut, and whatever your assistant says during those hours it is saying alone. If you have never written a separate set of instructions for those 123 hours, the assistant is running the daytime script at 2am: written during the working day, tested during the working day, and wrong in the one way that matters. The night shift is a different job. After hours the assistant cannot hand anything to a person, because there is no person. It has two goals: finish the order if the conversation can end in one, and leave you a specific morning list if it cannot. Everything in between that sounds like "a person will be right with you" turns into a lie the moment the clock says 11pm.

Two shifts, one configuration

During opening hours the assistant's job is straightforward. Answer what it can from your catalog and your own written answers, and when it cannot, get a human involved quickly. That second half works because the human is sitting there. The whole design of daytime chat assumes a short gap between the assistant giving up and someone taking over.

At night that gap is nine or twelve hours long, and every daytime instruction that assumed otherwise is now wrong. What it produces is a closed-hours reply that promises a person who will not exist until morning. That is worse than saying nothing, because the customer stops looking for the answer themselves and waits. They find out at breakfast that nobody came. The fix is not clever, but it has to be deliberate: write the closed-hours behavior separately from the open-hours one, and read it back at the hour it will actually be sent.

Set real hours, in your own timezone

This is the step that sounds too obvious to bother with and is skipped more than any other. An assistant that does not know when you are open cannot know when to stop promising people. Fill in the actual hours, not the ones on your About page from three years ago. Include the half-days. If you close at 2pm on Fridays, the assistant needs to know that at 2:01pm, not at 6pm.

Then check the timezone, and check what a weekend means in the markets you sell to. In Israel the working week runs Sunday to Thursday and Friday afternoon is already closed; in much of the Gulf the weekend is Friday and Saturday. If you sell into more than one of these, "closed" does not mean the same thing to you and to the person typing. Set the hours to the week your own team actually works, in your own timezone, and let the reply state the reopening time rather than assuming the customer can work it out. A German customer browsing at 9pm on a Sunday does not know that Sunday is a workday in Tel Aviv, or that it ended three hours ago.

Public holidays are the part nobody maintains, and they are hard for a structural reason: a weekly schedule repeats, and a holiday does not. The closures most likely to embarrass you are the ones a recurring set of hours cannot express. So treat them as a calendar task rather than a settings task. Write out next year's closures in one sitting, add any week you shut for stocktaking or a trade show, and put a reminder two days before each one to change your hours and your away line by hand. Then change them back on the morning you reopen. An away message that says "back at 9 tomorrow" on the first day of a three-day closure is worse than one that says nothing, because it was specific and it was wrong.

Say when, not whether

"Someone will reply when we open at 9" is a good answer at 2am. "Let me get someone for you" is a broken promise that arrives seven hours later. The difference between the two is that one of them contains a time. Write the closed-hours reply so that it always names an hour, and where it matters, a day: "We are closed now. We open at 9am on Sunday and someone will read this then."

Nobody is annoyed by a wait they were told about in advance. People are annoyed by a wait they were talked out of expecting. That also rules out the softer version of the same mistake, the vague reassurance with no number in it: "shortly", "as soon as possible", "in just a moment". Said at midnight, all three mean nine hours, and the customer reads them as five minutes. If you write only one closed-hours line, make it the one with a clock time in it.

The hour before you close, and the first hour after you open

Two boundaries do more damage than the whole of the night, because at 3am everybody knows where they stand. The first is the last hour you are open. A customer who writes at 5:40 when you close at 6 gets told, correctly, that somebody will pick this up, and then nobody does, because the person who would have picked it up went home twenty minutes later. Decide what happens in that hour and say it out loud. Either your team clears the queue before leaving, or the assistant starts naming tomorrow's hour from a stated point in the afternoon. Both are defensible. Quietly implying same-day attention at 5:55 is not, and it produces the angriest message you will read the next morning.

The second boundary is the reopening. At 9:01 your away message has stopped being true for the person writing now and is still governing everyone who wrote overnight, and both groups are sitting in the same place. Nothing is misconfigured; the hours flip on their own. It is a writing problem. A closed-hours line that promises a reply "when we open" is read at 9:15 as a promise already broken, while one that promises a reply "in the morning" survives contact with a queue. It is a small difference in wording and a large difference in how many people write a second time to ask whether you saw the first one.

Closed does not mean the catalog is closed

The reason to run an assistant overnight at all is that most of what customers ask is answerable from your catalog and the answers you wrote down. The handoff page keeps the list of categories that should be answered rather than escalated; the point here is narrower, which is that not one item on it needs a person awake. These are as answerable at 2am as at 2pm:

The overnight conversation should still end in an order wherever it can. Every mechanism that closes a sale during the day is still running at three in the morning: the catalog the answers come from, the discount codes it is allowed to name because they are genuinely live in your store, the cart it can fill on the storefront. None of that needs anybody awake. A shop that switches its assistant off at closing time is turning off the half of it that still works, and keeping the half that was never going to run.

There is a test for whether your configuration is doing this. Read ten overnight transcripts and sort them into three piles: finished without a person, genuinely needed a person, and could have been finished if someone had written the missing answer down. The third pile is the work. Every answer you add to it moves a conversation out of the second pile and into the first, permanently, for every night after. Run the same exercise with ten fresh transcripts a month later and the third pile should be shorter.

The away message is a piece of writing

Treat the away message as copy you edit, not a field you fill. It has three jobs. Name the reopening time. Say what will actually happen next. Use the same wording on every channel you answer on.

The second job is where most away messages quietly lie. "We will get back to you" is only true if a person does. The assistant is not going to reach out to that customer later, and it should not write a sentence implying it will. Overnight follow-up happens for exactly one reason: a human reads the morning list at 9 and emails the people on it. So the away message should say that in plain words, and then somebody has to do it.

The third job is the cheapest to get right and the most commonly broken. If the widget says "back at 9" and WhatsApp says "someone will be with you shortly", one of them is lying, and it is often the same customer reading both. Write the wording once and copy it to every channel, then re-copy it whenever your hours change.

Overnight expectations differ by channel

Someone typing into a chat widget on a website at 1am assumes nobody is there. Someone messaging your WhatsApp number at 1am often does not. A phone number reads as a person, and the reply comes back into the same thread as messages from their friends. The expectation attached to the channel is different even though the question is identical.

The practical consequence is that your WhatsApp closed-hours line should be more explicit than your widget one. On the widget, a short line naming the reopening hour is enough. On WhatsApp, say the hour and the day out loud, near the top of the reply, before the answer to whatever they asked. Say the wait time on the channel where people expect not to have one.

The morning list is the point

The measure of overnight chat is not how many conversations happened. It is what is sitting in front of you at 9am. What you want is a short list of named people with specific questions: a customer who asked whether the 60cm shelf holds a 40kg load and left an email address, another who wanted to know if you can ship to an address the checkout rejected. That means the assistant should collect a name and one question when it cannot finish the job. Two fields, emailed to whoever opens the shop, and deliberately no more than two: how many fields to ask for, what to say while asking, and where the record should land are decisions with a page of their own, and the night shift needs only the smallest version of any of them.

Then build a routine around it. Work the overnight list before you open the rest of your inbox, not after. Those are the people who were told a time, and at 9:01 they are the ones checking. The value of the reply decays through the day: an answer at 9:10 lands while they still remember what they wanted, an answer at 4pm competes with everything that has happened to them since. Fifteen minutes at the start of the day, before anything else. If nobody owns that fifteen minutes, overnight capture is a folder of questions nobody answered, and you would have been better off saying you were closed and leaving it there.

If the list is empty two weeks running, that is information too. Your problem is not the configuration. Read the next section.

The shops that should set hours and stop there

If you get three conversations a week after hours, this is not the problem to solve. Set your hours so that nothing gets promised, write one honest away line, and go and spend the afternoon on something with more traffic behind it. A clearly worded contact form with a stated response time costs nothing and does the same job at that volume. Nobody should build a night shift for a handful of messages.

The second case is order chasing. If the bulk of the night's traffic is people asking where their parcel is, the assistant's honest answer to nearly all of it is that somebody will check in the morning, which is a politeness layer rather than a night shift. There is nothing wrong with a politeness layer. It is simply not a reason to spend an afternoon on hours, holidays, away wording and a morning routine, and the larger question of whether that inbound shape should stop you buying at all is settled on the readiness page rather than this one.

Which shops actually benefit

Three patterns make the night shift worth configuring properly. The first is evening-heavy traffic, where the peak is after dinner rather than at lunchtime. Look at the hour-of-day distribution of your sessions, not the day-of-week one; they tell different stories, and shops that sell to people with day jobs are usually busiest at an hour when nobody is at the desk. The second is customers in another timezone, where a real share of the people buying from you are awake while you are asleep. The third is weekend browsing, where people research on Saturday and Sunday and you are closed on both.

If two of those three describe your shop, treat out-of-hours as its own configuration and give it an afternoon: real hours in the right timezone, a calendar reminder for the closures a weekly schedule cannot hold, one away message copied to every channel, a closed-hours reply that names an hour, name-and-question capture emailed to whoever opens up, and a re-read of ten overnight transcripts a month later to see what the assistant should have known. If none of the three describe you, correct hours and one honest sentence is the entire job.

Common questions

Should I turn the chatbot off outside business hours?

No, but you should change what it says. Most of what customers ask overnight needs no human at all: sizing, materials, shipping cost, the return window, which discount codes are live. Those conversations can still end in an order. What you turn off is anything that promises a person. Set your real business hours so the assistant knows when you are shut, and replace "let me get someone for you" with a line that names the hour you reopen.

What should an out-of-hours away message say?

Three things. The time you reopen, stated as an hour and where relevant a day. What will actually happen next, phrased honestly: a person reads the messages in the morning and emails back. And the same wording on every channel you answer on, so the website widget and WhatsApp do not give two different answers. Avoid "shortly" and "as soon as possible". At midnight both mean nine hours, and customers read them as five minutes.

Will the assistant follow up with the customer in the morning?

No. The assistant replies inside a conversation the customer started; it does not send messages later, and it cannot notify anyone when something is back in stock. Overnight follow-up happens because a human works the list at 9am. That is why the out-of-hours setup should end with a name and a question captured and emailed to whoever opens the shop, and why the away message should never imply an automatic callback.

How do I handle public holidays and half-days?

Half-days repeat every week, so they belong in the hours themselves: if you close at 2pm on Friday, the schedule has to say 2pm, not 6pm. Holidays do not repeat, so a weekly schedule cannot carry them and they stay a manual job. Write out next year's closures in one sitting, set a reminder two days before each to change the hours and the away line, and change them back when you reopen. Holidays are the most common cause of a confidently wrong away message, because "back at 9 tomorrow" is specific and specifically incorrect on the first day of a three-day closure. The same care applies to markets whose weekend is not Saturday and Sunday: a working week that runs Sunday to Thursday needs the hours set that way, not translated in your head.

Is out-of-hours chat worth it for a small shop?

Often not. If you get three conversations a week after hours, a contact form with a stated response time does the same job for free, and the honest move is to set your hours correctly and stop there. It is worth configuring properly when one of three things is true: your traffic peaks in the evening, a real share of your customers are in another timezone, or people browse across the weekend while you are closed.