Reporting a problem
What this covers
How to reach support, what your report sends, and how to write one that gets fixed quickly. Anyone can report a problem — no special permission needed.
Where to find it
Report an Issue at the bottom of the sidebar, on every page. It opens a form titled Report an Issue / Request Support.
What it sends
| Field | Notes |
|---|---|
| Your name | Pre-filled. So support knows who to reply to |
| Your email | Pre-filled. Check it — the answer goes here |
| Current route | Pre-filled with the screen you were on, which saves a round of questions |
| Message | Required, up to 5,000 characters |
| Screenshot | Optional, captured by the button |
It goes by email to Tabledoo support. Your reply comes back by email, so a wrong address means an answer you never see — worth the two seconds to check.
The screenshot button
Press Capture screenshot and the form closes briefly, takes a picture of the page behind it, and reopens with the image attached — so you get the screen you were looking at, not the form covering it.
Take one whenever there is anything to see. A screenshot of an error, an unexpected number or a missing button answers more questions than a paragraph does.
Check what is in it before you send. It captures whatever is on screen, which on a Timeline or a guest page means guest names and phone numbers. That is fine and often necessary — but if the problem has nothing to do with those guests, consider navigating somewhere neutral first. You can remove an attached screenshot before sending.
Writing a report that gets fixed fast
The difference between a same-day fix and a week of emails is usually four sentences.
Include these five things
- What you expected. "I expected 19:30 to be offered for a party of four."
- What happened instead. "The list jumped from 19:00 to 20:30."
- The exact date and time — both when it happened and the booking date involved. "Trying this now, for Friday 17 October."
- The specific record. The booking reference, the guest's name, the table name. A reference beats a description every time.
- Whether it happens every time. "It does it every time I try" is a completely different problem from "it did it once".
A good report
Booking 4821, Sarah Mullen, Friday 17 October 19:30, table 12. I changed it from 4 to 6 people and saved. It saved, but the guest got no update email — we have update emails on, and she has an email address on her profile. The confirmation email when I created it on Tuesday did arrive. It has happened twice this week, both times when changing party size.
That report can be investigated without asking a single question.
A report that will take a week
Emails aren't working.
Two more things worth adding
- What you already checked. "The type is switched on and the guest has an email address" stops support suggesting what you have done.
- Whether anything changed recently — a plan change, a new member of staff, a settings change. It is often the answer.
Check the obvious first
Not to discourage reporting, but because these are genuinely most reports and you can solve them in two minutes:
- A missing menu item or page — usually your role or your plan (link A feature or menu item is missing)
- A time not offered — usually a booking rule working as configured (link No times are available)
- A guest saying they got nothing — usually a switch, a missing detail or SMS credits (link A guest didn't get their message)
- Cannot sign in (link Sign-in and session problems)
What to do while you wait
- Keep working. Almost everything has a manual route — take the booking on paper and enter it later rather than losing it.
- Do not repeat the action hoping it works. Retrying a save that appeared to fail is how you end up with duplicates.
- Write down what you did, with times. If it stops happening, that note is the only evidence left.
- Tell your team so three people do not report the same thing.
- If it affects guests — messages not going out, the booking page down — contact the affected guests directly. Do not wait.
Good to know
Support may ask to look at your workspace, and there are guarantees around that (link When support signs in to help).
Support cannot tell you a password, an API key or a webhook secret. None are stored in readable form — the answer will always be to reset or reissue.
Feature requests are welcome here too. The form says "Request Support" for a reason, and "we need X" from a working restaurant is the most useful kind of request there is.