Back to Blog

Count the Customer Hours Your Beirut Team Cannot Answer

A hypothetical Beirut supplier answers 107 of 160 customer hours across four markets. Count the dark hours, then cover, promise or limit.

Four identical plain wall clocks in a row on a deep blue plaster wall, each set to a different hour. Warm morning light through an arched window falls across the first three; the fourth hangs alone in shadow. Headline: Whose calendar is the promise in? Credit: Dr. Jonah Tebaa.
Direct answer

How do you count the customer hours your Beirut team cannot answer?

To count unanswered customer hours, Dr. Jonah Tebaa introduces the Calendar Grid method. Teams record each client group's exact working schedule, convert those hours into Beirut's winter and summer clocks, and calculate the simultaneous working overlap. In a hypothetical illustration of a forty-hour Beirut team serving four markets across 160 total customer hours, the team answers 107 hours while 53 remain dark. Businesses then address dark stretches by choosing to cover hours with rotas, promise response times in client clocks, or limit service schedules.

On a Sunday at 10:00, a procurement officer in Riyadh sent a one-line question to a Beirut supplier. The supplier's team was not careless. They were at home, as their week said they should be. The answer arrived on Monday at 09:00 Riyadh time, twenty-three hours later, and seven of those hours were the buyer's own working day.

This is a hypothetical illustration with invented numbers, not a client story. The supplier, the buyer and every figure below are made up to show a method. The method is mine, and it matters more when an AI first responder answers at once: the customer reads speed as a team that is awake.

One team, several working weeks

A small Lebanese team that serves Lebanon, the Gulf and the diaspora does not have one working week. It has several. Many Gulf firms work Sunday to Thursday, others Monday to Friday. Many Lebanese firms work Monday to Friday. A client in Canada or France sits on a different clock altogether. I cite no national rule here, and you should not assume one: the week that counts is the one your own client tells you.

Beirut also changes its clock twice a year, so the overlap with each market moves.

Now a sentence many owners write in an offer: "we reply within one working day." It is written in the owner's calendar. In the customer's calendar it may mean a Sunday morning of silence. An AI first responder does not fix that. It only makes the silence polite.

The Calendar Grid in five steps

The Calendar Grid is my working method, not research. It needs a spreadsheet and one email to your clients.

  1. Write each customer group's working days and hours in its own local time. Ask. Do not infer it from the country.
  2. Convert each group to your team's clock, with the winter clocks and then the summer clocks, because the overlap changes when Beirut changes its clock.
  3. Count, per group, the customer working hours your team is also at work, and the longest stretch nobody on your side answers.
  4. For each group choose one: cover, promise or limit. Cover means move a start time or add a Sunday rota. Promise means write reply windows in the customer's clock, quoted by whoever answers first, human or AI. Limit means state in your offer the schedule you serve.
  5. Write the chosen promise in one sentence per market, and re-run the grid whenever a clock changes or a market is added.

A worked example: four markets, 160 customer hours

Every figure in this section is a hypothetical number for illustration. The schedules and clocks are assumptions, not research, and real customers will not work neat eight-hour days.

The supplier's team works Monday to Friday, 08:00 to 16:00 on the Beirut winter clock: 8 x 5 = 40 hours. Assume each of four customer groups also works 8 hours a day for 5 days: 40 customer hours each, and 4 x 40 = 160 in all.

Group (hypothetical)Customer week, local timeSame hours on our winter clockHours we answerShareIllustrative decision
A. LebanonMon-Fri 08:00-16:0008:00-16:0040 of 40100%None needed
B. Saudi buyerSun-Thu 09:00-17:0008:00-16:00 (Riyadh 1 hour ahead)32 of 4080%Cover Sunday with a rota
C. UAE buyerMon-Fri 09:00-17:0007:00-15:00 (Dubai 2 hours ahead)35 of 4087.5%Promise in Dubai time
D. Montreal clientMon-Fri 09:00-17:0016:00-00:00 (Montreal 7 hours behind)0 of 400%Promise in Montreal time

Group B: the team is open Monday to Thursday only, so 8 x 4 = 32 hours, and the Sunday's 40 - 32 = 8 hours are dark. Group C: the overlap runs from 08:00 to 15:00, which is 15:00 - 08:00 = 7 hours a day, so 7 x 5 = 35, and 35 / 40 = 0.875, or 87.5%. Group D: the team stops at 16:00, just as the client's day begins, so the overlap is 0.

Total answered: 40 + 32 + 35 + 0 = 107 of 160, and 107 / 160 = 0.66875, about 66.9%. Total dark: 160 - 107 = 53 customer hours a week. Check: 0 + 8 + 5 + 40 = 53.

Two thirds covered sounds like a decent week. But one market is dark for all 40 of its hours, and the average hides it.

The grid changes with the clocks. In summer, Beirut and Riyadh both sit on UTC+3, so a Riyadh 09:00 to 17:00 day is 09:00 to 17:00 in Beirut. Against the 08:00 to 16:00 team, the overlap is 7 hours for four days: 7 x 4 = 28, not 32. I do not generalise the other groups; re-run each one.

Two schedule moves, with no added paid hours (hypothetical):

  • A late seat. One person works 10:00 to 18:00 Beirut, Monday to Friday. Montreal overlap becomes 16:00 to 18:00, so 2 x 5 = 10. New total: 40 + 32 + 35 + 10 = 117 of 160, and 117 / 160 = 0.73125, about 73.1%.
  • A Sunday rota. One person works Sunday 08:00 to 16:00 Beirut in turn, taking a quiet weekday off. Group B reaches 40 of 40. New total: 107 + 8 = 115 of 160, and 115 / 160 = 0.71875, about 71.9%.
  • Both. 107 + 10 + 8 = 125 of 160, and 125 / 160 = 0.78125, about 78.1%. Dark hours: 160 - 125 = 35.

The decision is per market, not per hour. For Montreal, the question is whether you can write a promise the client can rely on, and one can be kept even at zero overlap: "A message sent in your working day is answered by 09:00 Montreal time the next working day." Your team's day runs from 01:00 to 09:00 Montreal time, so the answer is waiting before the client sits down.

Three honest answers for each dark stretch, and where the AI responder fits

Cover it. Stagger a shift or run a rota. This is the only answer that puts a person at work in the customer's hours. An AI first responder does not cover a stretch. It can acknowledge the message and collect the details, so the person starting the shift has a case ready. The customer is still waiting.

Promise in the customer's clock. Here the AI first responder earns its place, because it is the one voice awake in every dark stretch. The one line it must carry is the next human working moment, in the customer's own time: "A person on our team will reply by 09:00 Riyadh time on Monday." Never "shortly." Never "within the hour" when nobody on your side will work for a day or more.

Limit it. If a market is worth less than the cost of the schedule, say so in the offer: which days and hours you serve, and that other messages wait for the next opening. The AI responder should say the same sentence, so the website and the first reply never disagree.

There is one place the AI responder cannot stand in. If the question needs a human decision, such as a changed delivery date, a price exception or a complaint, an automated reply can name when a person will look at it and nothing more. Do not let it suggest the matter is already handled.

Before changing anyone's working hours, talk to the people affected and check your employment terms. A rota is a request to your team, not a line in a spreadsheet.

What to do on Monday

Before you promise the next client a reply time, put their working week next to yours and count the hours you actually answer.

  1. Email each customer group for its working days, hours and main holidays.
  2. Build the grid in a spreadsheet, winter and summer.
  3. Take the market with the largest dark share and choose cover, promise or limit.
  4. Check that your automated first reply says what you chose, in that market's clock.

If you want a second pair of eyes on your grid, write to me.

Frequently asked questions

Do I need staff in every time zone to serve clients abroad?

No. Cover only the markets where the grid shows the dark hours are worth a schedule change. For the rest, a reply window written in the client's own clock often costs nothing, because it only asks you to say when a person will answer. Choose per market: cover it, promise around it, or state the schedule you serve.

How do I find a client's real working week?

Ask, in one short email: which days, which hours in their local time, and which holidays matter to them. Do not infer it from the country, because firms in the same market keep different weeks. Keep the answers in your grid and confirm them once a year, since a client's schedule can change without notice to you.

What should an automated first reply say when nobody is working?

One sentence naming the next human working moment in the customer's own time, for example: a person will reply by 09:00 Riyadh time on Monday. Never write "shortly" or "within the hour" in a dark stretch. If the question needs a human decision, the reply should say who will look at it and when, and nothing more.

How often should I re-run the Calendar Grid?

At least twice a year, when Beirut changes its clock, because the overlap with each market moves. Re-run it also whenever you add a market or a large client, and when a client tells you its week has changed. It is a spreadsheet and takes an hour once the first version exists.

Written by Brian, Dr. Jonah Tebaa's AI partner, on his behalf.