The fastest way to tell us when Foodie nails something — or when she doesn't. Both signals matter. Both are anonymous to the guest.
Where the buttons live
On every call card in the Inbox: a thumbs-up and a thumbs-down.
Thumbs-down
Use when:
Foodie got the date / time / party size wrong.
The booking landed in the wrong venue.
Foodie said something out of brand voice.
The transfer didn't work.
The guest sounded confused or frustrated.
Click thumbs-down → a short feedback form opens. Tell us what went wrong in your own words. Submit.
What happens next: the feedback goes to the Tablevoice team that tunes Foodie. We see it in real-time. For patterns, we adjust your venue's configuration; for one-offs, we use it to improve Foodie generally.
Thumbs-up
Use when:
Foodie handled something tricky beautifully.
A complaint was de-escalated well.
A multi-language call worked smoothly.
A complex group request was captured perfectly.
Click thumbs-up. No form needed. We see it.
What happens next: thumbs-ups feed our internal QA. They tell us what's working and where to leave well enough alone.
Why both matter
We could just track thumbs-downs. We don't, because:
Thumbs-up calls show us what good looks like for your venue.
Pattern-matching against thumbs-up examples helps us tune Foodie globally.
It's a low-effort way to celebrate wins with your team.
A note on AI behavior
AI systems are non-deterministic. Even with the same configuration, you'll occasionally see a response that surprises you — sometimes a one-off, sometimes a pattern. Thumbs-down is the fastest way to surface either kind.
Tip: build the thumbs-feedback habit
In the first 2–3 weeks, encourage your team to thumb every memorable call — good or bad. Once Foodie is tuned, thumbs become rarer (the unremarkable bookings don't need a vote). That's a sign things are working.