Scenario profile
- Business
- Example: Quillan Street Pizza (one shop, 22 staff)
- Industry
- Independent pizzeria: takeout, own-driver delivery and a short counter
- Size
- Owner-operator, two shift managers and about 19 part-time counter, kitchen and driver staff at one location
- Setting
- Corner storefront in a dense neighborhood, with its own drivers, its own ordering link and listings on two delivery apps
- Call volume
- About 700 calls a week, roughly 190 of them between 4 pm and 10 pm on Friday
Key takeaways
- In this example about one Friday-night call in four goes unanswered, and close to half of the calls that do get through are not orders at all.
- The modelled setup picks up when both counter lines are busy or nobody answers within about three rings, and every call after closing, working from a one-page house sheet the owner approves.
- It never takes the order, guesses about an allergen or quotes a party price: it texts the shop's own ordering link, hands allergy calls to a person and logs large-order requests for a callback.
- Every figure here is modelled from the sources listed or invented for the example, not measured at a real pizzeria.
The shop in this example
Quillan Street Pizza is a fictional shop built to show how the setup and the numbers would work. It is one corner storefront with a twelve-stool counter, two deck ovens, four of its own drivers on a Friday and listings on two delivery apps. The owner still stretches dough on Friday nights. Two shift managers and about nineteen part-timers cover the rest of the schedule.
Nearly 75% of US restaurant traffic now happens off-premises, and in the same 2025 National Restaurant Association report 94% of consumers said speed is critical[1]. At a shop like this one, off-premises is nearly all of it, and on a Friday a lot of it still starts with a phone call.
In this example the shop takes about 700 calls a week. About 190 of them land between 4 pm and 10 pm on Friday, and roughly 85 arrive between 6 and 8, close to one every 85 seconds. Two lines ring at the counter. A third caller, or anyone the counter cannot get to in time, ends up in a voicemail box that nobody plays before Saturday afternoon.
What Friday nights looked like before
In this example the owner pulls four Fridays from the carrier's call log and has the counter keep a tally sheet by the phone for two of them. On an average Friday the log shows about 52 of the 190 calls going unanswered, a little more than one in four, nearly all between 5:30 and 8:30. The tally sheet shows what was tying up the lines:
| Why they called | Share of answered calls | What it looks like at the counter |
|---|---|---|
| Placing an order | About 55% | Two to three minutes each, often with a walk-in waiting to pay |
| “Where's my order?” | About 20% | Most after 6:30, once the quote has slipped |
| Hours, delivery zone and menu | About 12% | Do you deliver to Linden Avenue, slices after nine, gluten-free crust |
| Large orders and parties | About 4% | Team parties, office lunches, birthday trays |
| Allergy questions | About 4% | Sesame, tree nuts, dairy-free cheese |
| Everything else | About 5% | Delivery-app problems, vendors, wrong numbers |
The status calls did the most damage. By seven the delivery quote had drifted from 45 minutes to 75, and almost every customer whose first quote had passed picked up the phone. Each call meant a hold, a look at the ticket screen and a shout to the oven, while line two rang and a walk-in waited to pay. Nobody checked the bag that went out next.
Allergy calls went to whoever was nearest the phone. Sesame is one of the nine major food allergens, alongside milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat and soybeans[2], and a sixteen-year-old in his third week cannot know what the supplier puts on the garlic knots. Turnover keeps it that way. From January to September 2026 the monthly quits rate in accommodation and food services ran between 3.6% and 5.0%, against 2.1% to 2.3% across private industry; the September figures are preliminary[3][4]. In this example the phone rules live in the owner's head, and the people answering change every few months.
Large orders were the most valuable calls and the worst handled. A parent wanting twenty pies for a Sunday team party heard “the owner does those, call back tomorrow”, or had the details written on a ticket stub that was gone by morning. Saturday brought the last clue: a run of Friday-peak orders from the shop's own zip codes on the delivery-app tablet, placed by people the owner suspects could not get through.
How the SI Employee would be set up
In the modelled setup an SI Employee answers in the shop's name, with a greeting the owner approves. The carrier forwards a call to it when both counter lines are busy or when nobody picks up within about three rings, the setting most carriers sell as forward when busy or no answer. After closing nobody is at the counter, so every call goes the same way. The counter's rule changes with it: answer when you are free; if you are mid-bag or ringing up a walk-in, let it ring.
Before anything goes live, the owner writes a one-page house sheet, and every answer a caller hears comes from it:
- Hours, kitchen close and holiday closures.
- The delivery zone by street and zip code, and the delivery minimum.
- Menu basics: sizes, slices until nine, a gluten-free crust on the menu, with no safety claim attached to it.
- The Friday quote: delivery 50 to 70 minutes from the order time, pickup 25 to 35.
- The large-order rule: ten pies or more needs a day's notice and a callback from the owner.
- Allergy, cross-contact and complaint calls always go to a person.
Order callers are the biggest group, and this setup takes no orders or payments. It offers to text the shop's own ordering link, which needs a registered SMS sender and the caller's yes. Callers who would rather order by voice are transferred to the shift manager's cordless at the oven. If that rings out, it takes a name and number and the call summary says the caller wants to order, so the counter rings those back first when the board eases.
Status calls get the Friday window, because this example assumes no connection to the ticket screen or the drivers. Inside the window, the caller hears the range and the call is logged. Past it, the call goes down the manager path: a transfer to the shift manager, and if nobody picks up, the caller's name, address and order time are taken and the manager is notified. For delivery-app orders the owner's wording sends driver and refund questions to the app's support and a wrong or missing item to the manager.
- System
- Caller
- SI Employee
- Your team
01System
Both lines busy at 7:12
The carrier forwards the third call and the SI Employee answers in the shop's name.
02Caller
Asks about 18 pies
A parent wants pies for a Sunday team party and asks if the crust has sesame.
03SI Employee
Takes the party details
Date, pickup time, pie count, toppings, name and callback. No price or slot promised.
04SI Employee
Hands off the sesame part
Says plainly the shop will confirm, not guess, and asks for the best callback time.
05System
Logged with a summary
Summary and transcript land in the inbox; the owner is notified of the request.
06Your team
Owner calls back at 10 am
Checks the supplier's spec sheet, then confirms the pies, the price and pickup.
Example: fictional shop and rules. A real setup follows the house sheet the owner approves.
The large-order questions follow the owner's large to-go order rule: date, time, pickup or delivery, address, pie count, rough toppings and a callback number. Each one is marked as a request. Price and the oven slot stay with the owner, who calls back the next morning with both.
Friday night, before and after
| Friday-night call | Before (two lines at the counter) | After (modelled setup) |
|---|---|---|
| Third caller at 6:40 pm, both lines busy | Rings, then lands in a voicemail box nobody plays before Saturday | Forwarded on busy and answered in the shop's name |
| Caller ready to order | Put on hold while the counter rings up a walk-in; some hang up | Offered the ordering link by text, or transferred to the manager's cordless |
| “Where's my order?” at 65 minutes | Hold, a look at the ticket screen, a shout to the oven | Given the Friday window; past it, transferred to the shift manager, or details taken and the manager notified |
| “Do you deliver to Linden Avenue?” | Counter stops bagging to find the zone map | Answered from the approved street and zip code list |
| “Is there sesame in the crust?” | Answered by whoever picked up, sometimes from a guess | Never guessed; sent to the manager with a callback request |
| Twenty pies for a Sunday team party | Written on a ticket stub, sometimes lost by morning | Captured as a request; owner notified and calls back with the price |
| Saturday, 10 am | Owner plays voicemails and hunts for ticket stubs | Owner reads Friday's summaries; large orders and callbacks already listed |
In this example the Friday volume does not change and neither does the kitchen. What changes is that the counter stops being the only door. The guidance on handling calls during the dinner rush still applies to the calls staff answer; the overflow catches the ones they cannot.
What the numbers would look like
The worked example models the phone work in calls that roll over and finish without anyone at the counter. It is priced at what accommodation and food services employers spent per hour worked in June 2026, wages and benefits together[5].
| Input | Example |
|---|---|
| Calls a day, averaged across the week | 100 |
| Counter minutes per call, holds included | 3 |
| Share finished without the counter | 25% |
| Employer cost per hour worked | $20.03 |
| Calls a month | 2,170 |
| Staff hours on these calls | 109 |
| Hours handed off | 27 |
| Monthly value of that staff time | $543 |
How it is worked out: Calls a day × 21.7 working days × minutes per call ÷ 60 × share handled = hours; hours × hourly cost.
Assumptions
- Hourly cost of $20.03: the average employer cost of wages and benefits per hour worked in accommodation and food services, June 2026.[5]
- Nearly 75% of US restaurant traffic happens off-premises; at a takeout and delivery shop like this one, almost every order is to go.[1]
- 100 calls a day (700 a week spread over seven days), three counter minutes per call and a 25% share finished without the counter are invented for this example.
Example only: modelled, not measured. The calculator counts 21.7 working days a month; this shop opens every day, so the modelled hours are on the low side.
In this example that comes to about 27 hours a month of phone work, worth roughly $540 at that rate. Read it as workload moved off the counter, not wages saved: nobody's shift gets shorter. Friday carries the largest single share. About 60 calls would roll over on a Friday night and about 45 would finish without the counter, around two and a quarter hours of phone work in the six busiest hours of the week. Some of those callers used to get voicemail; the rest used to pull someone off the bagging station. That time would go into checking bags against tickets and getting pickup times right, which is where wrong orders and angry callbacks start.
The other cost sits in the calls nobody answered. Suppose ten of the 52 Friday callers who got no answer ordered the same food through a delivery app instead. At an example ticket of $40, that is $400 of sales, and the shop would hand roughly $60 to $120 of it to the platform: two in three restaurants that use those platforms put their average fee between 15% and 29.9%[6]. In the same May 2026 survey, 43% of limited-service operators said they make no profit on third-party delivery orders[6]. A text with the shop's own ordering link would keep some of those orders direct. The method for putting a figure on the rest is in what a missed call costs a restaurant.
The first 30 days in this example
Day 1
Owner writes the house sheet: hours, delivery zone, Friday quote times and the large-order rule.
Day 3
Test calls: a sesame question, a 25-pie order, a late delivery and a caller who refuses the text.
Day 4
The carrier switches on forward when busy or no answer, set to about three rings.
Day 5
First live Friday. The counter answers when free and lets the rest roll over; after closing, every call does.
Day 13
After two Fridays, the owner reads every summary and tightens the zone and status wording.
Day 30
Owner compares unanswered Friday calls and app orders from the shop's own zip codes with the month before.
Example timeline; a real rollout follows the owner's own schedule.
In this example the owner keeps two lists through the month: rolled-over calls that should have reached a person faster, and calls the counter took that never needed one. The first list matters more. A late-delivery caller left waiting twenty minutes for a manager is a one-star review in the making. A zone question the counter never heard is the setup doing its job.
Lessons from the scenario
- Write the Friday quote down. A caller told “delivery is running 50 to 70 minutes tonight” is calmer than one put on hold for a guess.
- Give the counter permission to let it ring. Overflow does nothing if staff still sprint for every call.
- Name the person who takes allergy calls on a Friday, and a backup, before the first rush. The routine for those calls is in allergy questions over the phone.
- Set the large-order rule before routing large orders anywhere: how many pies, how much notice, who calls back.
- Judge the month by Friday calls that reached nobody and by app orders from your own zip codes, not by how many calls were answered.
The shop keeps its number, its counter, its drivers and its ordering link. What changes is who picks up the third call. For what an SI Employee handles on a live call today, see what it does.
Frequently asked questions
Is Quillan Street Pizza a real customer?
No. It is a fictional shop used to show the method, and every figure is modelled from the sources listed or invented for the example.
Can the SI Employee take the pizza order itself?
No. Taking orders and card payments is not part of this setup. In this example it offers to text the shop's own ordering link when the caller agrees, which needs a registered SMS sender, and transfers callers who want to order by voice to the shift manager.
Can it tell a caller where their delivery is?
Not in this example. No connection to the ticket screen or the drivers is assumed, so it gives the Friday window the owner approved. Past that window the call is transferred to the shift manager; if nobody picks up, it takes the caller's name, address and order time and the manager is notified.
What happens to allergy questions?
They always go to a person. It can say a gluten-free crust is on the menu if the owner approves that line, but it never says a pizza is safe for an allergy. See allergy questions over the phone.
Do regulars have to talk to it?
Only when both counter lines are busy, nobody picks up within about three rings, or the shop is closed. During service any caller can ask for a person and is transferred to the shift manager.
References
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
U.S. Food and Drug Administration (2026). Food Allergies (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Job Openings and Labor Turnover Survey: quits rate, accommodation and food services (series JTS720000000000000QUR) (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Job Openings and Labor Turnover Survey: quits rate, total private (series JTS100000000000000QUR) (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: Private industry workers by occupational and industry group (June 2026) (opens in a new tab) ↑
National Restaurant Association (2026). Comments to the FTC on the Food Delivery Fees ANPRM (Project No. P267101) (opens in a new tab) ↑