Getting help

If something isn't working the way you expect and the common fixes didn't cover it, reach out — we'd rather hear from you mid-shift than have you lose covers over it.

How to reach us

Contact your TableStack point of contact, or use the support channel included with your plan. If you're not sure which that is, whoever set up your account can point you to it.

For anything urgent during service — a floor that's stuck, bookings that won't save — flag it as time-sensitive so it's picked up quickly rather than sitting in a general queue.

What to include

The more of this you can give us up front, the faster we can help. You don't need all of it, but a good report usually has:

• Your venue name (and organization, if you run more than one) — so we're looking at the right account.
• What you expected to happen versus what actually happened — the single most useful thing you can tell us.
• Where you were — the floor, the reservation book, the booking page, a guest profile — and what you tapped just before it went wrong.
• Steps to reproduce it, if you can — "book a party of 6 for Friday, then try to change it to 8" is worth more than "bookings are broken."
• Roughly when it happened — a date and approximate time helps us find it in the record.
• Which device and screen — host-stand tablet, phone, the kitchen display, a diner on their own phone.
• A screenshot, if the problem is something you can see on screen.

Before you write in

A couple of quick checks solve a surprising share of issues, and they're worth thirty seconds first:

• Is the device online? A dropped connection is the usual reason a screen looks frozen — see Real-time sync.
• Have you reloaded the page once? That catches a screen back up if it briefly lost connection.
• If it's about who can do what, check the person's role first — see Your team and their roles.

If none of that helps, send it over with the details above and we'll take it from there.