Forty portions. That's what you're making Saturday, and they'll be gone by 1:30. Between now and then your phone will ring with three questions, over and over: where are you this week, do you still have any, and can I reserve some.
None of those questions require judgment. All of them arrive while you're prepping or serving, and every one you don't answer is either a sale that goes elsewhere or a person who shows up at 2:15 to find you packed up.
A pop-up's phone problem is a broadcast problem
Restaurants with a fixed address have a phone that mostly takes orders. A pop-up has a phone that mostly repeats facts, and the facts change weekly.
Location. Hours. What's on the menu this time. Whether the preorder window is still open. Whether you sold out. You post all of it, and a meaningful share of your customers don't see the post, or see last week's, and call instead.
That's the real shape of it. You aren't understaffed on order-taking, you're understaffed on saying the same five things all day while doing something else with your hands. Food trucks have the identical problem for the identical reason, covered in voice AI for food trucks.
Your phone number is the only fixed thing you have
Everything about a pop-up moves. The venue, the hours, sometimes the concept. The number shouldn't.
If you're currently using a host venue's line, or a personal cell that changes when you switch carriers, fix that first. One number you own, on every post, every sign, and every listing. That's the address customers actually have for you, and it's the prerequisite for anything else. Moving a number cleanly is covered in phone number porting.
This matters more for a pop-up than for anyone else, because you have no storefront for people to walk past.
It also protects you against the venue relationship ending. If your regulars have the host bar's number saved and you move across town, you've handed your customer list to a landlord. Operators discover this at the worst possible moment, usually the week they're trying to announce a new location.
A second, smaller point: whatever number you use can get flagged by carriers if it starts making outbound calls in bursts, which matters if you confirm preorders by phone. Check how your number displays on an unfamiliar handset before you rely on it.
Weekly updates are the entire maintenance burden
No system knows where you're setting up Saturday. You have to enter it, the same as you enter it into a social post.
The habit that works is a single weekly block, ten minutes, where you update:
- The location and address for the upcoming service, including where to park
- Start time, and the honest time you expect to sell out
- The preorder cutoff and how pickup works this week
- Anything on the menu that's different from last time
- What the agent should say once you've sold out
Do all five at once or you'll do two of them and the agent will confidently give out a stale address. A wrong location answer is the single worst failure available to you, because it sends a customer to an empty lot and they don't call back. The general version of managing changing hours is in holiday hours and overrides.
Preorder windows are where the revenue is
If you take preorders, the phone is a real order channel and the arithmetic changes.
A configured agent can take preorders against a fixed count, close the window at your cutoff, and tell later callers plainly that preorders are closed and there may be walk-up portions. That's a flow worth having, and it's the same scheduling logic as order-ahead scheduling.
Two things to decide before you turn it on. What your hard count is, and whether you hold portions without payment. Holding without payment is how pop-ups end up with eight unclaimed portions at 2 p.m. If you take payment at preorder, read collecting payment over the phone safely first, because that's a different compliance surface than taking a name.
Sellouts have to live in the POS
Here's the constraint nobody mentions in a sales call. The agent reads availability from your POS. If your sellout tracking is a number in your head, or a tally on a whiteboard, the agent will keep selling portion forty-seven.
Pop-ups tend to run lean systems, which is reasonable, and this is the place where lean costs you. Either the count goes into the POS as you sell, or you accept that you'll be marking sold out manually and there will be a lag. Pick one deliberately, because the default is the version where nobody marks anything and the agent sells past your count.
Manual marking is fine if someone actually does it. Assign it to a person, not to "whoever notices."
The related decision is what the agent says on the way down. Telling callers you have "a few portions left" at 1:15 is more useful than a binary available-or-not, and it converts the person who was deciding whether to drive over. That's a message you have to write in advance, though, because nobody is composing it mid-service.
When a pop-up should not buy this
Be honest about your volume. If you run one service a week and take fifteen calls, a monthly subscription is not a good use of your money. Plans start at $250 a month, listed on the pricing page, and fifteen calls a week doesn't get you there.
The operators where it works are running several services a week, taking preorders, and getting enough inbound that someone is answering the phone during prep. If that's not you yet, put the number on everything, keep a clear voicemail greeting with the current location and hours, and revisit when the volume shows up.
There's also a middle case worth naming. If your pop-up is a step toward a permanent room or a ghost kitchen, the phone setup you build now carries over, and so does the number your regulars already have.
The measurement that decides it
For the next three services, keep a tally on your phone. Every incoming call: answered or missed, and one word for the topic.
Three services is enough. If you're missing a third of your calls and half of the topics are "where are you" and "do you have any left," you're losing sales you can count and you have a case. If the tally is thin, you've spent nothing to learn that the phone isn't your constraint, and your constraint is probably distribution instead. Fix that first.