Phones and Call Handling

When a Post Goes Viral: Handling the Phone Surge

A 72-hour phone plan for when a creator's video takes off: lines, scripts, waitlist rules, ordering limits and turning first-time callers into regulars.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing9 min read

On this page
  1. The phone rings before the line forms
  2. Hour 0 to 6: decide before you answer
  3. Hour 6 to 24: get the phone ready
  4. Scripts for the five surge questions
  5. Hour 24 to 72: protect the room and the regulars
  6. Example: the first Friday after the video
  7. Turn first-time callers into regulars
  8. After the wave: a 20-minute debrief
  9. Frequently asked questions
  10. References
Phones and Call Handling: When a Post Goes Viral: Handling the Phone Surge65%: of US adults under 30 use TikTok, the audience most likely to see a viral food video firstPHONES AND CALL HANDLINGWhen a Post Goes Viral:Handling the Phone Surge65%of US adults under 30 use TikTok, the audience most likely tosee a viral food video firstAva for RestaurantsInsightsPhones and Call Handling: When a Post Goes Viral: Handling the Phone Surge65%: of US adults under 30 use TikTok, the audience most likely to see a viral food video firstPHONES AND CALL HANDLINGWhen a Post GoesViral: Handling thePhone Surge65%of US adults under 30 use TikTok, theaudience most likely to see a viralfood video firstAva for Restaurants
Figure source: Pew Research Center, 2026[1]

Key takeaways

  • The phone surge arrives a day or two before the line at the door. Treat the first rings as the warning.
  • Decide the daily cap, booking rule, ordering limits and one message before anyone answers, so every caller hears the same facts.
  • Google's wait-time estimate is built from weeks of past visits and cannot be edited[2], so new guests call to ask.
  • The goal is not serving everyone in the first weekend; it is turning a share of first-time callers into regulars.

The phone rings before the line forms

It usually starts with a video you did not make. A local creator posts your birria tacos on a Tuesday night, and by Wednesday lunch the phone is ringing with the same five questions: are you open, do you still have the tacos, how long is the wait, can I book, do you deliver. The line at the door shows up a day or two later. The phone is the early warning, and it is also the first thing to break.

The audience is large and young. In Pew's 2026 survey, 37% of US adults said they use TikTok, including 65% of adults under 30, while Instagram reached 51% of adults and 79% of those under 30[1]. Those viewers are the most likely to see a food video first, and the least likely to already know your hours, your parking or whether you take reservations.

Who uses TikTok and Instagram, by ageShare of US adults who say they ever use each platform, 2026.
Who uses TikTok and Instagram, by ageColumn chart. 18 to 29: TikTok 65%, Instagram 79%; 30 to 49: TikTok 45%, Instagram 64%; 50 to 64: TikTok 31%, Instagram 41%; 65 and over: TikTok 11%, Instagram 21%.0%20%40%60%80%18 to 29 · TikTok: 65%65%18 to 29 · Instagram: 79%79%18 to 2930 to 49 · TikTok: 45%45%30 to 49 · Instagram: 64%64%30 to 4950 to 64 · TikTok: 31%31%50 to 64 · Instagram: 41%41%50 to 6465 and over · TikTok: 11%11%65 and over · Instagram: 21%21%65 and overWho uses TikTok and Instagram, by ageColumn chart. 18 to 29: TikTok 65%, Instagram 79%; 30 to 49: TikTok 45%, Instagram 64%; 50 to 64: TikTok 31%, Instagram 41%; 65 and over: TikTok 11%, Instagram 21%.0%20%40%60%80%18 to 29 · TikTok: 65%18 to 29 · Instagram: 79%18 to 2930 to 49 · TikTok: 45%30 to 49 · Instagram: 64%30 to 4950 to 64 · TikTok: 31%50 to 64 · Instagram: 41%50 to 6465 and over · TikTok: 11%65 and over · Instagram: 21%65 andover
  • TikTok
  • Instagram

Source: Pew Research Center, 2026[1]

Show the data
Age groupTikTokInstagram
18 to 2965%79%
30 to 4945%64%
50 to 6431%41%
65 and over11%21%

Google adds to the ringing. Its popular times graph is built from average visits over the last few months and its wait-time estimate from visits over the last several weeks, so neither shows a surge that started yesterday, and you cannot edit either one[2]. A guest who sees a quiet Wednesday on the graph and a packed room on their feed picks up the phone to ask. Google may also place automated calls to a restaurant on a searcher's behalf, including to check the current wait[3], so some of the rings are not even people.

Hour 0 to 6: decide before you answer

Before anyone picks up, the owner or general manager makes five decisions and writes them on one page. Staff can only give consistent answers to questions somebody has already decided.

  1. The daily cap on the featured item. How many can the kitchen make well alongside the regular menu? Say the number; “until they run out” is not something a caller can plan around.
  2. The booking rule. Keep taking reservations as usual, cap them at today's level, or go walk-in only for the next two weekends. Pick one and hold it.
  3. Online ordering limits. Lower the order cap per time slot, lengthen quoted times or pause the featured item on delivery apps. Throttling online orders lists the levers.
  4. Hours stay the same. Extending them on day one usually means running out of food and people by day three.
  5. One message everywhere. The pinned comment, the Google post, the website banner, the voicemail greeting and whoever answers the phone all say the same thing.

Hour 6 to 24: get the phone ready

Most restaurant phone setups were built for a normal Friday, not three of them in a row. Check yours before the evening rush.

  1. Count your lines

    Find out how many calls can ring at once before callers get a busy signal. How many phone lines a restaurant needs explains the arithmetic.

  2. Rewrite the greeting

    Put today's facts first: hours, the daily cap, walk-in or reservations, and where to order. Voicemail greeting examples has wording you can adapt.

  3. Name a phone owner

    One person per shift owns the phone and the callback list, so calls stop ringing while three people assume someone else has it.

  4. Turn on overflow forwarding

    Forward unanswered calls to an answering service or an SI Employee for the surge window, using the same one-page facts.

  5. Start a callback list

    Name, number, what they asked and the promised callback time. Clear it before close, and leave a voicemail when nobody picks up.

If you forward overflow to an SI Employee, send it the one-page decision sheet as approved information before the next shift, so every caller hears the same hours, cap and wait policy. It takes reservation requests for the host to confirm and never promises a table, texts your official ordering link to callers who agree, and passes complaints and anything off-script to the manager path you choose. Each call arrives as an emailed summary, so by the next morning you can see which question is eating the phone. You can hear how it answers a call before you need it.

During service, the usual rush rules still apply: sort each call fast, keep holds short, and promise callbacks only when someone will actually make them. Handling phone calls during the dinner rush has the routine.

Scripts for the five surge questions

Example scripts. Swap in today's decisions and keep each answer under 20 seconds.
Caller asksSayAvoid
Are you open?“Yes, until 10 tonight. We're busier than usual, so expect a wait for a table.”“We're slammed,” which sounds like a reason not to come
Do you still have the tacos?“We make 200 a day and they've been selling out around 7. Ordering ahead is the surest way.”Promising one to a guest who will arrive at 8:30
How long is the wait?“About 45 minutes right now. We can't hold spots by phone; the waitlist opens at the door.”Quoting Google's estimate or guessing low
Can I book a table?“This week we're walk-in only for parties under six. For six or more, I'll take a request and the manager will confirm.”Making exceptions for whoever pushes hardest
Do you deliver?“Yes, through our ordering link. Would you like me to text it to you?”Sending the link without the caller's yes, or naming apps you have paused

The wait-time answer matters most. Holding spots by phone for walk-ins tends to break the line at the door, because guests standing there can see the empty table you are saving. Pick a rule and keep it: no phone holds, or a fixed number of phone spots per hour. Running a waitlist and quoting wait times cover the mechanics, and telling guests about sold-out items has wording for the moment the cap runs out.

Hour 24 to 72: protect the room and the regulars

The new crowd judges you on speed. 94% of consumers say speed is critical when ordering off-premises[4], and a first-timer who waited 70 minutes for a 30-minute quote writes about the wait, not the tacos. A smaller cap delivered on time beats a bigger one delivered late. Meanwhile the regulars, who paid your rent before the video, are calling to ask whether they can still get in.

  • Recheck the daily cap every afternoon against what sold and when it ran out the day before.
  • Set aside two or three tables a night for regulars who call, and tell the host team, not the internet.
  • Add a second phone person, or keep overflow forwarding on, for the first two weekends.
  • Read reviews and comments daily and answer with facts: the cap, the hours, the ordering link. Responding to negative reviews helps when a first-timer had a rough wait.
  • Thank the creator. If you plan any paid follow-up, follow the disclosure rules in working with food creators.
Example: a 72-hour surge plan
  1. Hour 0 to 6

    Decide the daily cap, booking rule, ordering limits and one message

  2. Hour 6 to 24

    Greeting rewritten, phone owner named, overflow forwarding on

  3. Hour 24 to 48

    Scripts in use, waitlist rule held, cap checked against sales

  4. Hour 48 to 72

    Regulars looked after, reviews answered, weekend staffing set

  5. Week 2

    First-time guests invited back on quieter days

Example timeline. Most of the work happens before the busiest night, not during it.

Example: the first Friday after the video

Example. A 60-seat taqueria normally takes about 120 calls on a Friday. The Friday after the video, its phone log shows 410. With two lines and one person on the phone, about a third of the calls between 5 and 8 p.m. ring out or hit a busy signal. The owner's one-page sheet, written at noon, says: 200 birria plates a day, walk-in only for parties under six, online orders capped at 12 per 15 minutes, hours unchanged.

  • Before 5 p.m. The greeting is rewritten with the cap and the ordering link, and overflow forwarding is switched on from 4 to 9.
  • 5 to 7 p.m. Most calls are “do you still have it” and “how long is the wait.” The phone owner answers each in under 20 seconds from the script, and forwarded calls get the same facts.
  • 7:10 p.m. The cap runs out. Within ten minutes the greeting and the Google post change to “Birria is sold out for today; the rest of the menu is available.”
  • After close. The callback list has 14 names, mostly large-party requests, and the manager confirms the ones that fit the following week.
Example: one surge-night call that misses the phone owner
  • Caller
  • System
  • SI Employee
  • Your team
  1. 01Caller

    Caller asks about the tacos

    Saw the video and wants to know if they are still available tonight.

  2. 02System

    Both lines busy

    The phone owner is on another call, so overflow forwarding sends this one on.

  3. 03SI Employee

    Overflow line answers

    Gives today's cap, hours and walk-in rule from the approved one-page sheet.

  4. 04Caller

    Caller agrees to a text

    The official ordering link goes to their mobile.

  5. 05Your team

    Manager gets large parties

    Requests for six or more reach the manager, who confirms by the next morning.

Example sequence. Every route gives the caller the same facts, whoever or whatever answers.

Nothing in this example is complicated. What keeps the night manageable is that the cap and the rules were decided at noon, not argued about at 7:10 with a line out the door and the phone ringing.

Turn first-time callers into regulars

Surges fade. What lasts is the share of newcomers who come back. The phone is a good place to start, because callers are already talking to you and most of them have never ordered from you before.

  • Offer the loyalty sign-up or email list on calls and at pickup. 52% of consumers take part in a restaurant loyalty program[5], and more than 60% of takeout and delivery users say membership affects where they order[6].
  • Point new fans to quieter days. Roughly 8 in 10 off-premises customers say they would use discounts for ordering on less busy days or at less busy times[7], which spreads the surge instead of stacking it on Friday.
  • Get texting consent properly if you plan to text them later, and honor opt-outs within ten business days at most[8]. SMS marketing and TCPA consent has the wording.
  • Ask callers how they heard about you and note it, so you know whether the next wave comes from the same creator.

After the wave: a 20-minute debrief

Two or three weeks later, once calls are back near normal, sit down with the managers who worked the surge and answer five questions. Write the answers into a surge sheet you can pull out next time; a second viral post is far easier with the first one's notes.

  • Calls per day against a normal week, and how many rang out.
  • Which question dominated, from the tally sheets or the call summaries.
  • When the featured item sold out each day, and what the cap should be next time.
  • Which script lines confused callers or caused complaints.
  • How many first-time guests came back in week two or three.

For a sense of what a heavy phone night looks like hour by hour, the pizzeria Friday-rush example models a shop taking roughly 190 calls between 4 and 10 p.m. on a Friday. The content side, including what to post once the wave hits, is in TikTok for restaurants.

Frequently asked questions

How do we know a surge is starting?

The phone usually tells you first: the same few questions from callers who have never been in, often naming a video. Check your tagged posts and Google profile views the same day, and decide the cap before the evening rush.

Should we stop taking reservations during a viral surge?

Not necessarily, but decide one rule and keep it for at least two weekends. Walk-in only for small parties, with large parties taken as requests the manager confirms, is easy to explain on the phone and easy for the host to enforce.

Can we fix Google's wait-time estimate?

No. Google builds popular times and wait times from past visit data and does not let businesses edit them[2]. Post your current situation on the profile and say it in your greeting instead.

Should we extend our hours?

Usually not in the first few days. Extra hours stretch the same kitchen and team further. Hold your hours, cap the featured item, and revisit after the first weekend once you know the real demand.

How long does a viral surge last?

It varies with the post and the platform, which is why the plan focuses on the first 72 hours and a debrief afterward. Track calls per day so you know when you are back to normal.

References

  1. Pew Research Center (2026). Social Media Fact Sheet: Americans' social media use (2026 survey) (opens in a new tab) ↑

  2. Google Business Profile Help (2026). Popular times, wait times, and visit duration (opens in a new tab) ↑

  3. Google Business Profile Help (2026). About automated calls and texts from Google to your business (opens in a new tab) ↑

  4. National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑

  5. National Restaurant Association (2024). Where operators plan to invest in tech (opens in a new tab) ↑

  6. National Restaurant Association (2025). From Trend to Transformation: loyalty and off-premises ordering (opens in a new tab) ↑

  7. National Restaurant Association (2025). Report: Takeout, drive-thru, delivery are more popular than ever (opens in a new tab) ↑

  8. Legal Information Institute (Cornell Law School), eCFR text (2026). 47 CFR 64.1200 - Delivery restrictions (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo