AI phone reservations for restaurants

01What callers can do

• Make a reservation: "a table for four Saturday at seven thirty".
• Change the day, time or party size.
• Cancel a reservation.
• Say they're running late. Zogu notes it on the reservation.
• Order pickup in the same call.

02One read-back, one yes

Nothing is booked until Zogu has read the reservation back and the caller has said yes. Zogu's code checks that, not the AI model.

The name only ever comes from the caller's own words. More on how the one read-back works.

03It checks your capacity and hours

• You set your services and how many guests each can take, day by day.
• Closures, special hours and how far ahead you take reservations all count.
• When a time is full, it offers the nearest open times, or the same time on another day.
• It never books past your limits.

04Large parties get your own line

Over your phone limit, the caller hears the limit and a line you write, such as "For parties over 10, please email our reservations address." Zogu never transfers the call or promises a call-back.

05Reservations land in your book

Each reservation goes into the Bookings tab in the Zogu console, with the name, number, party size and any notes for the team. Reservations stay in Zogu's book and don't go into your POS. For now our team runs the console.

06What it won't do

• No confirmation texts or emails. The caller hears "There's no text, but you're all booked in."
• No deposits, and no card details by voice.
• No waitlist.
• No link to another reservation system yet.