Everything you need to go live.

SavvyMenu turns your restaurant's menu into an assistant that answers guests — on your website, and on a hosted menu page guests reach by scanning a QR code at the table. It answers from what you publish and the facts you write, follows a short set of house rules, and says so when it doesn't know.

What it's good at

• Questions about your dishes, prices and ingredients — from your published menu.
• Hours and “are you open right now?” — once you've set your hours and timezone.
• Sending guests to your booking link and your full menu.
• Saying “I don't know” instead of guessing, and flagging the question so you can teach it.

What it won't do

• Take orders, payments or reservations.
• Say a dish is vegan, halal, gluten-free or allergen-free unless your menu or facts say so.
• Make up policies, prices or your restaurant's story.
• Ask guests for their name, phone number or email.

1. Create your workspace. Sign up with Google or email and name your restaurant. One workspace per location.
2. Upload your menu. Menu → Add your menu. A PDF, or a photo of each page (JPG or PNG, up to 25 MB). Scanned pages and photos take a minute or two to read.
3. Review and publish. Read through the draft sections, fix anything that came out wrong, then click Publish. Your assistant only uses what you publish.
4. Set your hours, timezone and links. Settings → Hours & links. Add your booking link so guests who want a table get a button for it.
5. Add a few facts. Settings → Custom facts: parking, large parties, your allergy policy. See good facts.
6. Test it. Ask the Playground what your guests ask. Test questions count toward your daily chats.
7. Go live. Settings → Add to website (paste one line into your site) and/or Settings → Table QR (print it).

What you can upload

• PDF, JPG or PNG, up to 25 MB per file. Uploading the exact same file twice is refused.
• Text PDFs are read directly. Scanned pages and photos are read by an AI vision model — that takes a minute or two, and you can leave the page while it works.
• For a multi-page paper menu, upload a photo of each page.

Drafts, then publish

An upload becomes draft sections — blocks of your menu's text, each named after its first line. They aren't separate dishes with structured prices: the assistant quotes what the text says, so make sure each section reads correctly. Nothing reaches guests until you click Publish. Editing or deleting a published section updates your assistant straight away.

Your website's About pages

Menu → Add your menu → Scan website imports your About, Story or FAQ pages as draft sections, so the assistant can answer “who are you?” questions. Review and publish them like menu sections.

Starting over

Purge all menu data (bottom of the Menu page) deletes every menu section and draft. Your custom facts, dish facts and chat history are kept.

Custom facts are short, true statements for what a menu can't say. When a fact answers a question, it wins over the menu. Free includes 3, Pro 10 — keep each one to a sentence or two.

Good custom facts

• “Reservations for parties of 6 or more are by phone only: (555) 010-0123.”
• “We have vegetarian, vegan and gluten-free dishes, but we're not an allergen-free kitchen — please tell your server about allergies.”
• “Our meat is not halal-certified.”
• “Free parking in the lot behind the building.”
• “Wheelchair-accessible dining room and washrooms.”
• “Takeout and delivery through UberEats; pickup is usually ready in about 15 minutes.”

The assistant only knows your phone number if it's on your menu or in a fact. Want these as a printable sheet? Open the starter facts handout.

Dish facts

Dish facts (Menu → Dish facts) belong to one dish: dietary tags, portion size and notes. Free includes 10, Pro 200. The tags are vegetarian, vegan, gluten-free, halal, contains-nuts, dairy-free, spicy-mild, spicy-medium and spicy-hot. They also show as labels on your menu page.

Personality

Pick Friendly, Formal or Energetic in Settings → Widget look (or the Playground's settings). It changes the tone, not the facts. Changes apply to your live widget immediately.

When it can't answer

Instead of guessing, the assistant gives one of four replies. These are the defaults; rewrite them in Settings → Replies & identity:

• Off-topic question: “I can only help with menu questions — try asking about a dish or category. 🍴”
• Not on the menu: “I don't see that on the menu. Want to ask about something else? 🍽️”
• Dietary or allergen claim it can't verify: “I don't have verified info on that. Best to call the restaurant directly to confirm. 📞”
• A detail the menu doesn't list (portion, how it's cooked): “Great question — the menu doesn't list that detail. Your server will know exactly! 🍽️”

Not a restaurant? Settings → Replies & identity also lets you say who the assistant works for, e.g. “Maple Street Bakery's catering service”.

• Weekly hours — one opening range per day (split lunch and dinner hours aren't supported yet).
• Timezone — used to answer “are you open right now?”. It's taken from your browser when you create a workspace; double-check it in Settings → Hours & links.
• Address — shared when guests ask where you are.
• Booking link — shown as a Book Table button when guests ask to book. Without one, the assistant tells guests you don't take online reservations and to call or walk in, so add your link if you take bookings anywhere online.
• Menu link — shown as a View Menu button when guests ask to see everything.

Copy your line from Settings → Add to website and paste it just before </body> on every page — most site builders have a “footer code” box for this. It looks like this:

<!-- Your exact line is in Settings → Add to website -->
<script src="https://savvymenuai.com/widget.js"
        data-id="pk_live_…"></script>

The widget reads its look and behaviour from your dashboard, so you only paste it once. The key in the line (pk_live_…) is meant to be public: it can only be used to chat with your assistant.

Platform guides

• WixNeeds a Premium plan with a connected domainSettings → Custom Code (under Advanced) → Add Custom Code. Paste the line, choose All pages and Body – end, then publish.
• SquarespaceNeeds the Core plan or higherOpen Code Injection (Settings → Advanced, or Website → Website Tools on newer sites) → Footer. Paste and save.
• WordPress (self-hosted)Any siteInstall the free WPCode – Insert Headers and Footers plugin, then Code Snippets → Header & Footer → Footer. Paste and save. WordPress.com sites need a paid plan that allows plugins.
• ShopifyDuplicate your theme firstOnline Store → Themes → ⋯ → Edit code → layout/theme.liquid. Paste just before </body> and save. Theme updates can undo edits — check after updating.
• WebflowNeeds a paid site planSite settings → Custom code → Footer code. Paste, save, then publish.
• GoDaddy Website BuilderUse your menu page insteadIts custom-code sections run inside a box on the page, so the chat bubble can't float. Link your menu page from your site's menu instead.

Check it worked

Open your site in a private window. The chat bubble appears in the corner you chose in Settings → Widget look. Ask it something only your menu would know.

Can't add code?

Use your menu page and QR code — no website changes needed.

Every workspace has a public menu page with the assistant docked at the bottom. It shows your published menu and the dietary tags you've set, with a note asking guests to check allergies with staff. Guests don't need an app or an account.

• Settings → Table QR: download the code as an image or print it for tables, the window and takeout bags.
• Link the same page from your Google Business Profile or Instagram bio.
• Publish your menu first — before that, the page is empty.

Guests Asked lists the questions people ask, newest first. Playground tests appear there too, since they're chats. Analytics shows chats per day, your busiest hours, the most-asked questions, how often each dish comes up, and how many answers came from saved replies, over the last 7, 14 or 30 days. The mood of each conversation is estimated automatically, so treat it as a rough signal.

What lands here: answers where the assistant found nothing in your menu or facts and gave a fallback reply, or hit an error.

What to do: add a custom fact or dish fact, or fix the menu section — then use Test to ask the same question in the Playground. Items stay listed for 90 days.

• One chat is one guest question and its answer. Playground tests count.
• The daily count resets at midnight UTC. There are no overage charges.
• At the limit the assistant pauses until the reset, and guests are asked to call or visit instead. Watch your usage in Settings → Plan & usage.
• To stop abuse, each workspace also handles at most 30 chats a minute, and each guest device 20.
• Pro is $29 CAD/month. Request it from Settings → Plan & usage — upgrades are switched on by hand for now. See pricing.

Every workspace's assistant follows the same built-in rules. You can't switch them off:

• Answer only from your published menu, website sections, custom facts, dish facts and hours.
• No dietary or allergen claims — vegan, halal, gluten-free, nut-free, spice level and so on — unless your content says so word for word.
• Details the menu doesn't give (portion size, how it's cooked) → “your server will know”.
• Informational only: no orders, payments or bookings, and never a pretend confirmation.
• Broad questions (“what do you have?”) get a few categories and a follow-up question, not the whole menu.
• No invented history, family stories or atmosphere.
• “Are you open?” is answered from your hours and timezone, worked out before the AI sees it.
• Guests' messages are treated as questions, never as instructions to change these rules.

What's stored

• Your account (handled by Clerk), workspace settings, menu text, facts and dish facts.
• Guest questions and the assistant's answers, for 90 days — so you can see what guests ask. Then they're deleted automatically.
• Saved replies: each answered question is saved with its answer, so a repeat question is answered faster. They're also deleted after 90 days, and cleared sooner whenever you change your settings, facts or published menu, purge your menu, or delete the workspace.
• In the guest's own browser: the widget remembers the conversation for 24 hours so it survives a page reload. You can switch this off in Settings → Widget look.

The assistant never asks guests for names or contact details — but guests can type anything, so treat chat history as possibly personal.

Who processes it

• Groq runs the AI model that writes answers: it receives the question and the relevant parts of your menu and facts.
• Clerk handles sign-in. Vercel hosts this website and its anonymous visit statistics. Our servers run on DigitalOcean.
• Error reports may go to Sentry, and website scans of JavaScript-heavy sites may use Firecrawl to load the page.

We don't sell your data, and we don't train AI models on your menus or chats.

Deleting data

Settings → Danger zone deletes a workspace. For anything else — or a copy of your data — email support@savvymenuai.com.

1. Published menu sections are indexed for meaning (embeddings) so they can be found by question, not just keyword.
2. When a guest asks, SavvyMenu first checks its saved replies, then finds the most relevant published sections (with a keyword fallback for exact dish names).
3. Those sections, your facts, your hours and the house rules go to a large language model (served by Groq), which writes the reply in your chosen personality — or one of the fallback replies.
4. SavvyMenu adds reminders and action buttons, sends the answer to the widget (streamed as it's written), and logs the chat for Guests Asked.

The widget is a small script (about 18 KB compressed) that loads after your page and reads its look and behaviour from your dashboard.

When an answer should come with a button (Book Table, View Menu), the assistant appends a hidden block to its reply. The widget strips it out and renders the buttons; guests never see the JSON.

The ||| delimiters are split with a plain string match rather than parsed as markup, so a malformed reply can't break the page: invalid blocks are dropped, and a button only opens a link when it's an http(s) address.

There's no public API yet. The widget talks to SavvyMenu with your workspace's publishable key, which is safe to expose — it can only chat with your assistant and read its public look. Need an API for a kiosk, POS or phone system? Tell us.