Things that come up in the first week. Most are small. All are fixable.
Foodie says something off-brand
What it sounds like: the response is technically correct but doesn't sound like your venue. Maybe too casual, too formal, or just generic.
Why: the response style or opening line probably needs adjusting.
Fix: Voice & personality. Try a different style. Customize the opening line. Re-test by calling yourself.
Foodie can't pronounce your name
What it sounds like: "Cheez Mark" instead of "Chez Marc."
Why: no IPA pronunciation entry. Boosted keywords might also help with hearing it correctly when guests say it.
Fix: Pronunciation, keywords, keypad. Add an IPA entry for your venue's name and any tricky dishes.
A booking didn't reach OpenTable
What it sounds like: Foodie said "booked" to the guest, but the reservation isn't in Guest Center.
Why: OpenTable returned an error and Foodie still concluded the booking. Or a dining-area / party-size mismatch caused a silent fail.
Fix: thumbs-down the call card, tell us what guest expected. We check OpenTable, fix the configuration, follow up with the guest if needed.
Same question, two wrong answers in a week
What it sounds like: "Is your patio dog-friendly?" "I'm not sure." (Twice in a week.)
Why: missing entry in your knowledge base.
Fix: House rules → Dogs. Toggle the right answer. Update Agent.
Transfers fail
What it sounds like: Foodie says "connecting you," rings, then comes back: "unfortunately we couldn't reach the team."
Why: transfer number not being answered, OR an infinite-loop because your transfer number is your forwarded number.
Fix: Live transfers. Check the transfer number. If you're on forwarding, use a different number for transfers.
Push notifications stopped
What it sounds like: the iPad isn't pinging. Cards are landing in the Inbox, but staff don't see them.
Why: iOS sometimes revokes push permissions, especially after updates. Or notifications were never fully enabled.
Fix: Turn on push notifications. Re-enable in Account → Push Notifications. Check iOS Settings → Notifications → Tablevoice → Allow Notifications.
Group request notifications go to the wrong person
What it sounds like: the FOH iPad is getting catering requests; the catering coordinator never sees them until they happen to log in.
Why: notification routing isn't role-based.
Fix: Notifications. Add a separate notification entry for the catering coordinator subscribed to Catering Request and New Group Reservation Request.
A complaint went stale
What it sounds like: a guest complained on day 3, your team marked the card closed, but nobody actually called back. Now they're posting a 1-star review.
Why: Closed in the Inbox doesn't mean the customer was helped — just that your team is done with the AI's prompt. The follow-up still has to happen.
Fix: for complaints specifically, add an internal comment with the next step before closing. Treat the comment as a hand-off.
When to call us
Anything that feels systemic (happens twice or more) or potentially bad (deposit-related, complaint pattern, customer expressed serious frustration). For one-offs, the thumbs-down + a quick note in the form is enough.
The week-one debrief is where we tackle the patterns. Save up your observations, drop us a note, and we'll work through them together at day-7.