What does Dr. Jonah Tebaa's Calendar Grid for Lebanese Teams Serving Several Markets mean in practice?
Dr. Jonah Tebaa's Calendar Grid is a working table for Lebanese firms serving multiple markets, recording each customer group's local working week, equivalent Lebanese hours, staffed overlap, coverage share, and a single decision. In his hypothetical example, an overall average of answering 107 of 160 weekly hours hides zero coverage for Montreal alongside 80 percent in Saudi Arabia. To address uncovered dark hours, owners select one of three choices per market: Cover, Promise, or Limit.
The finished grid, and what Dr. Jonah Tebaa reads in it
Dr. Jonah Tebaa starts from a table, not a story. It has one row per customer group, and each row carries the same five facts: the customer's working week in its own local time, the same hours on the Lebanese team's clock, the hours the team is at work during them, the resulting share, and one decision. He calls it the Calendar Grid. It is his working method for small firms that serve Lebanon, the Gulf and the diaspora, and he does not present it as research.
His point about the table is that its total misleads. In his hypothetical, a supplier answers 107 of 160 customer working hours a week, about 66.9 percent. That sounds acceptable. The rows say otherwise: one Lebanese group is at 100 percent, a Saudi group at 80, a Dubai group at 87.5, and a client in Montreal at zero. An average response record hides a market with no coverage at all, and that is the market where an owner's promise is weakest.
Why he counts in the customer's hours
Dr. Tebaa observes that "we reply within one working day" is written in the owner's calendar. The customer reads it in theirs. A buyer who writes on a Sunday morning to a team that rests on Sundays waits through hours that are, for the buyer, working time. In his hypothetical that wait is 23 hours, seven of them inside the buyer's own day. He asks owners to measure that gap before they quote a reply time, and to take the customer's week from the customer, not from assumptions about a country.
The same logic applies to an AI first responder. Because it answers instantly at any hour, a customer may assume that a person is awake. Dr. Tebaa wants the responder to carry one fact: when a human will next be working, stated in the customer's own time. He applies the same rule to a sale, where an Offer Sheet for the customer-facing AI states when the offer ends in the customer's clock.
Three choices for a market the team cannot cover
For each row with dark hours, he offers an owner three choices, and he wants one chosen per market.
- Cover. Move a start time or add a Sunday rota. In his hypothetical, one late seat adds 10 hours and one Sunday rota adds 8, which takes the supplier to 125 of 160, with 35 hours still dark. An AI responder can gather the details so that the person starting the shift has a case ready, but he does not count it as cover.
- Promise. Write reply windows in the customer's clock and let whoever answers first quote them. For Montreal he suggests a plain sentence: a message sent in the client's working day is answered by 09:00 Montreal time the next working day.
- Limit. State in the offer the days and hours the firm serves in that market, and have the automated reply say the same.
He draws one boundary around the responder. When the question needs a human decision, such as a changed delivery date or a complaint, the automated reply may name when a person will look at it. It should not imply the matter is already in hand.
What he asks owners to remember about the clock
Dr. Tebaa tells owners to count twice, once with the winter clocks and once with the summer clocks. In his hypothetical, the Saudi group's overlap falls from 32 hours to 28 in summer, because Beirut and Riyadh then share the same clock and the team's open window sits differently against the buyer's day. He does not extend that to the other groups, and he tells owners to re-run each one rather than guess.
The numbers in his example are invented to show the method. Real customers rarely keep neat eight-hour days, so he asks owners to confirm each client's week and holidays, and to consult their staff and check employment terms before changing anyone's schedule.
Dr. Tebaa sets out the full first-person version, with the five steps, the table and the Monday action, on his own site. In his own words: Count the Customer Hours Your Beirut Team Cannot Answer.