industry · 5 min read

Voice AI for Restaurants: Menus, Hours, No Hold Music

A practical look at how restaurants are using voice AI on their websites in 2026: what diners actually ask, what works, and what ruins the experience.

Published April 26, 2026

A marble restaurant table at dusk with candles, wine glass, and a tablet showing a reservation page with a small blue Spelo voice button

Most restaurant websites are still designed for the part of the job that doesn't matter: showing pictures of food. The part of the job that does matter (answering whether you're open Tuesday, whether the squid ink risotto has nuts, whether you can squeeze in two at 7:30) happens by phone, by email, or not at all. Voice AI on the restaurant's own site fills that gap without tying up the host stand.

This is a quick tour of what voice does well for a restaurant site, what it does badly, and what the install actually looks like. We'll skip the marketing language about "conversational commerce"; that's for the chatbot vendors. Restaurants want to know whether the thing books a table or not.

The four things diners actually ask

Every restaurant gets the same handful of questions. Spelo (or any decent voice agent) handles all of them; we'll go through them in order of how often they come up.

1. "Are you open tonight?"

The single most-asked question. Hours change for holidays, private events, slow Tuesdays. Most restaurant websites paste static hours on the contact page and update them once every three years. The diner calls. The host puts them on hold to check the actual schedule.

Voice changes the loop: the assistant reads the live hours from the page, answers in three seconds, and if the page says "closed for a private event tonight" the diner hears "we're closed tonight for a private event, but we're open tomorrow at six." No call. No wait.

2. "Can you fit two at 7:30?"

Reservations through OpenTable, Resy, Tock, or your own form: voice handles all of them the same way. The assistant fills the form by listening, confirms the slot, and submits. Date inputs accept "next Friday." Time inputs accept "7:30." Party size accepts "two of us." The diner doesn't tap a screen.

When a slot isn't available, the assistant offers the next three. Most diners take the alternative; they were committed to the night, not the time.

3. "Does the [dish] have [allergen]?"

This is where voice earns its keep. Allergen questions take real attention from a server, are time-sensitive (your party is standing at the door), and a wrong answer is a hospital trip. Most restaurants handle them in person, badly, by reading the ingredient list off a printed menu while a line forms.

Voice works because the menu is a structured document. If the dish lives in your CMS or your menu page, the assistant reads it, applies the diner's filter ("anything with peanuts?"), and answers truthfully. Where ingredients aren't documented, the assistant says so out loud, which is the right answer, not a guess.

4. "Where can I park?"

The forgettable question that generates the most one-star reviews. The diner couldn't find your driveway, parked in the neighbor's lot, got towed, and is now writing about it. Voice handles parking the way it handles hours: read the page, answer with directions, optionally open the map.

What ruins the experience

Voice AI on a restaurant site fails predictably when:

The menu is a PDF. The assistant can't read inside images of menus reliably. If you serve allergens, your menu needs to be HTML, or you need the Done-For-You add-on so we can hand-feed the menu data into Spelo's knowledge base.
Hours live in three places that disagree. Google Business says one thing, your site says another, the chalkboard outside says a third. The assistant reads the site, so the site has to be right. (This is a problem voice exposes; the website was already wrong, but no diner used to bother with it.)
The reservation form is a third-party iframe. If your "Book a table" button opens an OpenTable iframe, Spelo can't see inside it to fill fields. Either embed the form natively, link out to the platform, or use Done-For-You so we wire the OpenTable API directly.

The install

For most restaurant sites (Squarespace, Wix, WordPress, plain HTML) Spelo is a single tag pasted into the site footer. The orb appears in the corner. Diners who never use it don't notice it. Diners who tap it get answers.

Squarespace: Settings → Advanced → Code Injection → Footer. WordPress: install the plugin or paste the tag in your theme header. Wix: Settings → Custom Code. Nothing else changes about your site.

The free plan includes ten voice minutes a month, enough to put it on the site, run it through the questions you get most often, and decide whether it's worth the upgrade. Most restaurants that stay past the free tier do it because the host stopped getting interrupted to check hours.

Where to start

The honest order of operations:

Audit your site. If hours are wrong or the menu is in a PDF, fix that first; voice will only amplify what's already there.
Install the script tag (two minutes).
Talk to it the way a diner would. "What's the soup tonight? Can I bring my dog? What's the corkage fee?" The questions it can't answer are the questions to add to your site.
Once the site can answer the top ten questions, the host stops being interrupted by the phone. That's the actual goal.

Spelo for restaurants walks through the use case in more detail. The full Spelo feature set covers what every install can do. Or just paste the tag and watch what diners ask; the data shows up in the dashboard. For broader hospitality context, Skift's travel research and Hotel Tech Report both track how the front-of-house experience is shifting toward instant answers.