What are your hours / do you take walk-ins
Opening hours, walk-in policy, and typical wait expectations, answered consistently from your published information.
AI chatbot for restaurants and reservations
AI chatbot for restaurants and reservations
Diners ask about hours, dietary options, and group bookings every day, often right at the moment they're deciding where to eat. GoBrise answers those from your own published menu and policy information, and hands anything about a specific reservation to a person.
- Dietary and allergen questions repeat before every booking decision
- Hours, walk-in policy, and group-booking rules get asked constantly
- A specific reservation's real details live in your booking system, not a knowledge base
- A large-party or special-event enquiry often needs direct coordination with staff
Last reviewed 20 September 2026
Quick summary
Procedural
Hours, dietary options, dress code, and general booking policy — answered from your published information.
Escalate
A specific booking, a large-party enquiry, or a special-event request is routed to your team directly.
$0
Unlimited human live chat on the Free plan while you evaluate AI.
24/7
Diners deciding where to eat outside your hours get an accurate answer instead of no response.
What people actually ask
Real questions this page answers, drawn from the conversations teams like yours handle every day.
Do you have options for [dietary requirement]
Vegetarian, vegan, gluten-free, and allergen information from your published menu — a question that decides whether someone books at all.
Can I book a table for a large group
Your general group-booking policy and any minimum notice required; an actual large-party or event booking is routed to your team for coordination.
What's your dress code / is it kid-friendly
Dress code, atmosphere, and family-friendliness, answered from your published information to set accurate expectations.
I have a question about my existing reservation
Anything about a specific booking is escalated to a person — the assistant doesn't look up or modify real reservations without a separate integration.
How it works
Step 1
Write dietary and allergen information precisely
This is a safety-adjacent category — document it accurately and keep it current, since a wrong answer here has real consequences for a guest.
Step 2
Document hours, walk-in and booking policy clearly
Include any seasonal or holiday-hour exceptions explicitly, since a stale hours answer is a common source of a wasted trip.
Step 3
Set the boundary for group and event enquiries
General group-booking policy is automatable; an actual large-party or special-event request should route to your team for real coordination.
Step 4
Install the widget on your menu and reservation pages
These are where dietary and booking questions actually happen — not just the homepage.
Step 5
Test with real dietary and group-booking wording
Pull actual past questions, including specific allergen queries, and confirm answers are accurate and group enquiries route correctly.
Step 6
Review whenever your menu or hours change
Update dietary and hours content immediately after any menu or schedule change — this is the fastest way stale content causes a wrong answer here.
Who this is — and isn't — for
An honest read on where GoBrise fits, so you can rule it out quickly if it doesn't.
A good fit if
- Most enquiries are about published information: hours, dietary options, dress code, general booking policy
- Your dietary and allergen information is documented precisely and kept current
- You want large-party and special-event enquiries routed to your team for real coordination
- You get meaningful volume from diners researching or deciding outside your hours
- You want any specific-reservation question to reach a person rather than being guessed at
Not the right tool if
- You want the assistant to look up or modify a specific reservation — that needs a separate booking-system integration
- Your dietary or allergen information isn't documented anywhere current — write that first, given the stakes
- Most of your enquiries are already event or large-group coordination rather than general questions
- Your hours or menu change frequently without being reflected in written content
- You have no team available to pick up routed group or event enquiries
Frequently asked questions
Can it check my existing reservation?
No — that requires real booking-system data. It answers general questions from your published information; a specific reservation is escalated to a person.
Can it answer detailed allergen questions safely?
Only as accurately as your documented allergen information — write this precisely and keep it current, since it's a safety-adjacent category where a wrong answer has real consequences.
Can it book a table directly?
Not without a separate reservation-system integration. It can explain your booking process and capture an enquiry for your team to follow up on.
How do we handle a large private-event request?
Route it to your team for direct coordination — the assistant explains general group-booking policy but shouldn't attempt to handle event-specific logistics.
What if our hours change for a holiday?
Update the content immediately for any seasonal or holiday exception — stale hours information is a common cause of a wasted trip for a diner.
Does it work across multiple locations?
Yes, though hours, menu, and policy should be documented per location if they differ, so the right location's information is retrieved.
Can it capture a reservation enquiry for us to confirm?
Yes, using the same lead-capture and handoff actions available across GoBrise, useful for enquiries your team then confirms directly.
Is it white-labelled?
Yes, on Growth and Business plans the widget carries your own branding, no GoBrise mark.
Try it on your own content
Start free with unlimited human live chat, add your content, and judge the answers for yourself.