Restaurant tech support: why it can't wait 48 hours

There's a huge difference between a problem in an office and a problem in a restaurant. In an office, if the system fails, people wait. In a restaurant, if the system fails, there are thirty people eating, eight waiting for a table and a kitchen that can't stop.

Office-hours support doesn't apply here

Restaurants work exactly when offices are closed: Friday nights, Saturdays, Sundays, holidays. Which is to say, exactly when most tech support doesn't answer.

A problem in the middle of service can't wait 48 hours.

What actually happens when you open a ticket

You log into the portal, describe the problem, attach a screenshot if it lets you, and get a case number and an automated email. Meanwhile table 9 is still waiting for the check and the new server has no idea what to do.

The case number helps nobody on the floor. What helps is someone answering.

What should get solved without you doing it

• Changing the price of an item.
• Adding a dish or a promotion.
• Adding the server who started this week.
• Checking why the kitchen printer isn't printing.
• Setting up a new station at the bar or on the patio.
• Training someone who joined midweek.

None of that should cost you the shift. And none of it should require you to learn how to configure a system.

Three questions for the vendor

• What hours do you actually answer, not what the contract says?
• Can I send a photo or a video of the problem?
• Do you make the change, or do you explain how I should do it?

If all three answers put you at ease, you found more than software. You found a team.