Access codes & chat safety

Your chat URL is public — anyone who scans (or shares) a QR code can use it. Access codes let you keep extended chatting for people actually at a table, and a set of built-in guardrails keeps the chat itself on-topic and abuse-resistant.

Access codes

When enabled, a diner chats freely for their first 5 messages, then is asked for a short 4-character code — which your staff give to seated diners.

1. Open Settings → Experience and turn on Access codes. A batch of 10 codes is generated for you.
2. Share the codes with your staff (print them, or keep the page handy). Any active code works for any diner.
3. The diner enters the code once; their whole session is unlocked — no re-entry.

Tap Regenerate any time to void all old codes and issue a fresh batch — diners who already unlocked their session stay unlocked.

Built-in chat safety

These are always on; nothing to configure:

• The AI only talks about your menu. Off-topic requests get a polite redirect — it won't write essays or discuss other restaurants, and it never invents dishes you don't serve.
• Conversations have sensible limits. Message lengths and per-session message counts are capped, and rapid-fire requests from one source are rate-limited, so a prankster can't burn through your AI diners.
• Prompt tricks are filtered. Attempts to make the AI ignore its instructions are blocked before they reach it.

Good to know

• Most restaurants don't need access codes. The free-message allowance, rate limits, and session caps already blunt casual abuse — turn codes on if you see chat use that isn't coming from tables.
• Codes add friction for real diners too — every table's sixth message needs a staff visit. Weigh that against the abuse you're actually seeing.