Answering Customers Over the Holidays: The Real Cost

Every small business in Israel has a holiday policy, even if nobody wrote it down: on the eve of a chag we answer until midday, on the chag we do not, and once it is out somebody will go through the messages. It sounds reasonable, and it is probably the only operational decision in the business that has never been costed. Nobody checked how many enquiries arrive across the three weeks of Tishrei, or how many did not wait at all.

Demand does not stop for a chag, only the answering stops

Here is what most owners miss: over the holidays the customer has more free time, not less. Someone who spent six months putting off a dental check-up, an air-conditioner replacement or an insurance policy reaches it on exactly these days, the ones with slack enough to sit down with a phone. The enquiry does not wait for the chag to end. It gets sent, and unanswered it moves to the next business on the results page.

The Israeli calendar concentrates the problem. A holiday eve is half a working day, chol hamoed runs on a partial team, and when a chag falls next to Shabbat you get three closed days in a row with a full inbox that the customer knows nothing about.

Then comes the second kind of damage, the one that happens after the chag. The inbox holds dozens of messages, and the team works through them in the order they appear on screen, newest first. The enquiry that waited longest, the coldest and least patient one, is answered last. The same response-time logic decides outcomes on ordinary days, and we covered it in our guide to 24/7 customer service with AI.

The arithmetic: how many answering days vanish in a year

This is calendar arithmetic, not a statistic, and you can run it yourself. A business working Sunday to Thursday is not really reachable from Friday midday to Sunday morning: a day and a half a week, about 75 days a year. Add the holidays. The Tishrei cluster, Pesach, Shavuot and the memorial and independence days come to some 20-25 non-working days, plus ten holiday eves that are half days. The total passes 100 days a year on which an incoming message just lies there.

Now the other side, with example figures to swap for your own. A business taking 60 enquiries a month gets about three per working day, so a three-week window around the Tishrei cluster holds roughly 45. If a third land on a day nobody answers, 15 wait one to three days. At an average deal of 1,800 shekels and a 25 percent close rate, each enquiry is worth about 450 shekels in expectation. If half of the 15 go cold or move to a competitor, that is around 3,400 shekels per holiday period, twice a year.

Two numbers worth putting side by side: one holiday period here costs more than a monthly agent subscription, and the agent covers the other 75 weekend days too.

Four ways through a chag, and what each costs

The on-duty option looks the most responsible and is the least stable: one person, in practice with their family, with no access to the calendar or the price list.

The automatic reply that does more harm than silence

"We are on holiday break and will get back to you shortly" is the most common message in the industry, and it answers a question nobody asked. The customer asked whether you do the thing they need, what it costs and when there is an opening. They got your hours, no date they can act on, and no sign the enquiry was recorded. From where they sit, the sensible next step is the next business.

A good closed-state message does four things instead of one: a real answer from material the business approved; a return date given as a business day rather than "shortly"; a genuine free calendar slot so progress happens now; and a CRM card with a summary, so whoever opens the screen after the chag sees a customer and not a message. That is the job of an AI agent instead of a receptionist, and the difference is not politeness but what is left in the system.

What the agent closes over a chag, and what it never decides

Precision matters here, because a promise of "no humans at all" breaks on day one. The agent closes most of the traffic alone: recurring questions about services, timing, areas and what is included; price ranges inside a pre-approved frame; booking from the open calendar; collecting details in order; filtering out whoever is not relevant. What it does not do: approve a refund or an unusual discount, commit to a slot that is not in the calendar, give medical or legal advice, or invent opening hours. Those move to a human with full context, and the customer is told when a person will reply.

Two things to define before the chag. First, the escalation route: which signals mark an enquiry urgent, who receives it, and what the customer hears if nobody is on duty. Second, the sending window. Incoming messages were sent by the customer and the agent only replies, but outbound messages go out on your rules, so a business that observes Shabbat defines that nothing leaves from the start of Shabbat until the chag is out. Follow-ups and workflows are unlimited with no trigger meters, so the catch-up sequence afterwards is not priced separately. And with several channels at once, none of it works unless they land in one inbox, which we detailed in our omnichannel inbox guide.

Reserve duty, illness and a flight: the same problem with no calendar date

A chag is at least a period you can plan for. The harder version is the days on no calendar: a reserve duty order, a flu that takes down whoever answers the phone, a week abroad. In a business of two to ten people one person almost always holds the answering, and if they vanish for two days the enquiry channel vanishes too.

The fix is not another person, it is getting two things out of that person's head. The knowledge first: prices, hours, what is included, the recurring answers and the cancellation policy, in a knowledge base the agent answers from instead of one memory. Then the history: every conversation on a CRM card rather than a personal phone, so whoever steps in sees what was said and promised. The same principle covers support enquiries arriving when the office is empty, which an AI agent for support and service is for.

Checklist: what to prepare the week before a chag

• A real return date. Not "after the chag" but a business day, in the knowledge base before the holiday eve.
• Real hours for the holiday eve and chol hamoed, per branch.
• The price ranges the agent may give. Undefined, every pricing question waits for a human, which over a chag means a week.
• A written escalation route. What counts as urgent, where it goes, what the customer hears with nobody on duty.
• A sending window for outbound messages, so nothing goes out on Shabbat or the chag.
• A working order for the morning after. By urgency and enquiry age, not by what sits on top.

Which plan this lands in

If leads arrive on WhatsApp and you need booking, the entry point is Standard at 490 shekels a month plus a one-time 1,990 shekels setup: WhatsApp through the official Meta API, calendar booking, images and documents, 2,000 AI messages a month, and the WhaleBiz CRM with analytics and Excel export, setup up to 14 business days. Traffic arriving only at a website widget or Telegram can start on Start at 190 shekels a month plus 990 shekels setup, but know what is missing: no WhatsApp, no calendar booking. Several branches or calendars, Instagram, or payment in the chat require Business at 990 shekels a month plus 2,990 shekels setup, up to 21 business days.

Prices exclude VAT, the setup fee is paid in one payment before work starts, and the subscription begins on go-live day, not the day you pay. One point matters for holiday planning: setup business days count from the moment all materials arrive, and holidays are not business days, so anyone wanting a working agent during Tishrei should hand over materials a month ahead. Full details on the pricing page.

Frequently asked questions

We really are closed. Is it not simpler to say we will get back after the chag? That answers a question nobody asked. An agent states the same hours and, in the same message, answers from approved material, gives a return date as a business day, offers a free calendar slot and logs the enquiry on a CRM card.

We observe Shabbat and do not want the business sending messages then. Is that possible? Yes. Incoming messages were sent by the customer; the agent only replies. Business-initiated follow-ups go out on the sending window defined at setup, so nothing leaves from the start of Shabbat until the chag is out. Changing that rule later is covered by your monthly change allowance.

Something urgent arrives during a chag and nobody is at the business. Then what? The escalation route is defined at setup by the business. The agent matches your signals, marks the enquiry urgent and passes it to whoever is on duty. With nobody on duty, it states when a human will reply and gives the emergency route you wrote.

Message volume rises around the holidays. Will we blow through the quota? Agent replies are counted, not incoming messages, and a reply to a voice message, image or file counts as two. Standard includes 2,000 a month, overage 0.30 shekels; Business 5,000, overage 0.25. Follow-ups and workflows are unlimited with no trigger meters.

What does it cost, and is there time to launch before the holidays? For WhatsApp with booking, Standard: 490 shekels a month plus 1,990 shekels setup, up to 14 business days. A website widget or Telegram only starts on Start, 190 plus 990 setup. Business is 990 a month plus 2,990 setup. Prices exclude VAT, the subscription begins on go-live day, and setup days count from receipt of your materials.