An AI agent on Shabbat and holidays: what it says while you're closed and what happens on Saturday night

On Shabbat, the Jewish day of rest from Friday evening to Saturday night, an AI agent does exactly what you configured it to do in advance, and there are three possible behaviors: full replies like on a weekday, limited replies that confirm and collect details without closing anything, or near-total silence with one sentence that explains when you will be back. The choice is your business decision, not a software default. And what almost nobody checks in advance: a message that came in on Friday afternoon is already outside WhatsApp's 24-hour window by Saturday night, so a free-text reply to it then simply will not go out. It is a decision worth making as early as the planning stage of your AI agents for business, before the first Shabbat arrives.

The 30 hours in which the business keeps getting inquiries

Between Friday noon and Saturday night there are about 30 hours in which most businesses in Israel do not answer anyone, while inquiries keep coming in as usual: the phone rings, messages arrive on the business WhatsApp, and a live campaign keeps sending people your way even at 11 p.m. on Shabbat. Nor are they all equal. Some people are checking options for next week, some sent the same message to three vendors, and some have a leak or an event tomorrow morning. With no reply, all three get the same treatment, and on Sunday, the first workday of the Israeli week, a pile of messages is waiting, where whoever shouts loudest gets answered first.

A 10-minute count before you decide anything

An industry average will not help here, and the only number worth anything is yours: scroll back through four weekends and count how many conversations were opened between Friday noon and Saturday night, and how many of them mention a date within the coming week. If almost nothing came in, one sentence is enough. If a good share of them have a date coming up soon, the question is how much freedom to give the agent.

How does an AI agent actually behave on Shabbat?

It behaves according to a profile set in advance for those hours, not according to the policy of a Tuesday at ten in the morning. People looking for a bot that works on Shabbat usually mean one of three things, and the difference is how much freedom the agent has when there is no person behind it. That decision gets made when the AI agent is planned, not after everything is already running.

Full replies, as if it were a regular day

This suits businesses that operate on weekends anyway: event halls, tourism, e-commerce and emergency repairs. Full replies do not mean the agent decides on its own, and instead of words like "end-to-end process" you need to write down exactly what it is allowed to do:

• Put a hold on a calendar slot, not a confirmed meeting, with automatic expiry on Sunday.
• Confirm availability only against a real calendar or inventory, with read-only access.
• Offer two concrete time slots and let the customer choose, instead of asking "When works for you?"
• Send a payment link for a deposit only when the amount comes from a fixed price list, not from a quote built by hand.
• Do not price a job that requires an on-site visit, and do not commit to a technician's arrival time.

Limited replies: confirm, collect, do not close

This is the profile most businesses use. The agent replies within seconds, asks the questions that will save a round of back-and-forth on Sunday (what is needed, for which date and at what scale) and says explicitly that the business is closed until Saturday night. It does not close a deal or promise an arrival time, and you get an inquiry with the details.

Near-total silence: one sentence and nothing more

Apart from an acknowledgment, nothing happens until a person is back. What that sentence must include is when you will be back, in terms the customer understands: "We'll get back to you on Saturday night," not "We'll get back to you soon." This profile has a technical price, and that is what the next section is about.

Why does the agent's Saturday night reply sometimes not go out at all?

Because WhatsApp has a 24-hour window: from the moment a customer sends a message, a window opens in which you may reply to them in free text, and once it closes you may send only a template that Meta approved in advance. A message that came in on Friday at 2 p.m. leaves the window on Saturday at 2 p.m., before the business is even back at work, so the reply the agent writes at 8:30 on Saturday night will not reach its destination.

The limit belongs to the business API, not to the app that runs on a phone, which is why someone who replies by hand does not feel it, while every automated agent is bound by it. The window is counted from the customer's last message, so an inquiry sent at 10 p.m. on Friday night, already on Shabbat, is still inside it, and one from Friday noon no longer is.

What the template does and what it cannot do

A template is not the place to answer a question, because the wording is fixed and only a few variables can be changed. Its only job is to reopen the window: to remind the customer who wrote on Friday and invite them to reply. The moment they write back a single word, a new window opens, and from there the replies on WhatsApp and on the phone continue as a normal free-text conversation. A utility template that refers to an existing inquiry is more likely to be approved than a marketing one, and the review can also come back as a rejection, which is why you submit it at the start of the setup.

A Shabbat-observant business vs. a business that is simply closed on weekends

The difference is not in the hours but in the question of who is acting. A business that is closed on weekends just does not want anyone making promises in its name that no one is there to approve, while a Shabbat-observant business asks what the system does in its name while it is not operating itself. We do not rule on questions of Jewish law, but it is our responsibility that the setup is precise and can be verified:

• No proactive message goes out on Shabbat: no reminders, no follow-ups and no sequences that were scheduled a week earlier.
• The voice agent does not dial out and does not return a missed call.
• Alerts to you are held, do not ring, and are released at the time you set.
• The calendar does not book meetings and does not send a reminder for Sunday morning.
• A payment link is either blocked or left open, as an explicit decision of yours.
• Everything is calculated on Israel time, even when the server sits on another continent.

Who stops an agent that runs 25 hours unsupervised

Even when no proactive message goes out, the agent keeps answering customers from the moment Shabbat begins until it ends, and if it makes a mistake or gets stuck in a loop, there is no person to stop it. The brakes have to be automatic, because a brake that needs someone watching a screen does not really exist:

• A message cap per conversation: after a set number of replies with no progress, the agent switches to the one-sentence reply on its own.
• An uncertainty rule: a question that falls outside the knowledge base is flagged for a person, with no guessing.
• An outbound rate limit: going over the hourly quota shuts the agent off and sends everything to the queue.
• A circuit breaker on anomalies: the same answer repeating over and over, or a jump in inquiries that fall into the "don't know" path.
• A manual kill switch that does not depend on you: a short code, sent by someone who does not keep Shabbat, that shuts everything down.
• A change freeze on Fridays. A bug that appears at two and is discovered at six will not be fixed until Saturday night.

The queue that builds up on Shabbat and falls apart on Saturday night

The critical moment is not Shabbat itself but 8:30 on Saturday night. A naive system releases everything that piled up all at once: the customer gets a barrage of messages after a full day of silence, and the messaging platform reads a burst like that as bulk messaging. A managed queue works differently: someone who wrote four messages is one conversation with four lines, not four tasks; the agent opens by acknowledging that the message has been waiting since Friday, because acting as if it was written a minute ago loses trust in the very first line; and the clock for replying to the customer is separate from the clock for alerts to you.

How the order is set, and what happens when the classification is wrong

An inquiry with a date coming up goes first, then whoever is comparing vendors, and last whoever asked a general question. The classification relies on what the customer wrote themselves: a time expression, the name of an event and situation words from a list defined for your industry. And what if it gets it wrong, and an inquiry about an event tomorrow lands at the bottom? Any inquiry that mentions a date within 72 hours moves to the top even when confidence is low, because an error upward costs a minute and an error downward costs a deal; an inquiry that was not classified goes into a bucket that sits at the top; and every line shows the customer's original wording next to it.

Replies on holidays: holiday eves, Chol HaMoed and the Israeli calendar

Fixed weekly business hours break down in Israel within a month. Friday at two to Saturday at eight works for one week, then a holiday eve lands in the middle of the week, followed by Chol HaMoed, the intermediate days of the festival, and then a holiday that runs right into Shabbat and creates three closed days in a row.

Where the agent gets the times from

The times are not typed into a table by hand. They are pulled from a public source of Jewish times such as Hebcal, based on the business's town, and they update on their own every week and every holiday. Two decisions are made before setup: how many minutes before sunset everything closes, 18 in most of the country or 40 by the Jerusalem custom; and which end time reopens the queue, tzeit hakochavim (nightfall) or the Rabbeinu Tam method, which adds about 72 minutes, and that is the difference between a queue that opens at eight in the evening and one that opens at nine. And above all: the business clock runs ahead of the religious one, and when Shabbat begins at a quarter past four in winter, nobody has been answering since one o'clock anyway.

The failures here repeat themselves, and you can look for them in advance: a server that runs on UTC and releases the queue two hours too late; the switch to daylight saving time, which shifts everything by an hour; a holiday that begins in the middle of the week while the setup only knows about Fridays; and a template that was approved with three variables and has since had a sentence changed, so the send fails silently and returns an error code that nobody reads.

Days when tone matters more than availability

Chol HaMoed is a special case: only half the team is in the office, but customers are free and make more inquiries than usual, and many businesses switch off their replies and miss a strong week. At the other end are days when the question is how you answer: Yom HaZikaron (Israel's Memorial Day), Yom Kippur and emergency periods. That is when you should have a switch, ready in advance, that moves the agent to a quiet, factual register. It is also worth updating your special hours on your Google Business Profile, so a customer does not see "open" on the map and then get a message saying you are closed.

How do you set quiet hours without blocking an urgent case?

You set quiet hours as a policy, not as an off switch: who gets an answer, what may be said to them and what justifies waking a person up. With a good setup, most inquiries wait until morning, and the exceptional case is passed on within minutes.

The definition of urgent is a business one, not a matter of wording. Someone who writes "urgent" with three exclamation marks is usually just impatient, and the real sign is an event: a leak, the freezer stopped working, the event is tomorrow at ten, I'm locked out without a key. When you write this short list in advance, the agent recognizes the case even without the word "urgent."

Next comes the escalation ladder: the agent recognizes the case, confirms to the customer without promising that someone will come, contacts the on-call person on one channel, and after a set number of minutes moves to a second channel and then to the next person. If no one answers, the agent goes back to the customer and tells the truth: "I've passed this to the on-call person, and there's no confirmation yet." It is also worth setting a cap on waking people up, because an escalation that happens seven times in one evening stops working.

The test you run on Thursday

Before going live, you run a simulation that takes less than an hour: send a message at an hour that is supposed to be quiet and check that the configured reply went out, not an old default; call the line and listen; make sure the queue opens at the set time; send yourself the approved template and see that it goes out; and run an emergency scenario that confirms the on-call phone rings. The Shabbat layer is part of setting up a sales agent, not a separate project, and what takes time is getting the templates approved by Meta.

Frequently asked questions

How does an AI agent know exactly when Shabbat begins in our area?

It does not guess. The times are pulled from a public source of Jewish times such as Hebcal, based on the business's town, and they update on their own, holidays included. You decide how many minutes before sunset you close, 18 in most of the country or 40 by the Jerusalem custom, and which end time reopens the queue, tzeit hakochavim or Rabbeinu Tam, which adds about 72 minutes. And if you stop answering at two on Friday anyway, the business hour wins.

We already have an automatic away message on WhatsApp. What difference does an AI agent make?

An away message informs, but it collects nothing. It is the same for everyone who writes, it does not distinguish someone checking a price for next month from someone with a breakdown right now, and it leaves no information beyond the name and the time. The difference shows in the queue: with a fixed message you get empty inquiries, and with managed replies you get inquiries with details and priorities.

We do not answer at all on Shabbat. What does that mean for getting back to customers on Saturday night?

Some conversations will be outside WhatsApp's 24-hour window before you are even back, because the window is counted from the moment of the customer's last message. An inquiry from Friday noon closes during Shabbat, and all you can send it is a pre-approved template, whose job is to reopen the conversation. As soon as the customer replies to it, a new window opens and replies go back to normal.

What happens when a customer sends a time-sensitive request on Shabbat, such as a cancellation or a complaint?

The request is logged with its original timestamp: for the record, the time of the request is the moment the customer wrote, not the moment the queue opened. The agent confirms receipt, does not decide on the request itself and flags it for a person at the top of the priority list. The right approach is to define requests like these in advance as a separate category that does not get lost among the price inquiries.

How do you handle three holiday days in a row?

Three closed days are not three times one day, because the queue does not just pile up, it goes stale: someone who wrote on the first day has already asked elsewhere by the third. That is why, on long holidays, replies that confirm and collect details are better than a message announcing that you are closed. Most conversations there also fall out of the 24-hour window, so an approved template is a must for getting back to whoever wrote on the first day.

The bottom line

Shabbat, holidays and quiet hours are not a hole in the schedule but part of the business's policy, and they become a problem only when nobody defined them in advance. A properly configured agent answers exactly as much as you decided, stops on its own when something goes off track, and keeps the inquiries with their context and priority. You can book a short intro call and go over your response hours, the holidays and the escalations.