Answer
Use approved menu, pricing, hours, location, booking, and policy information.
AI restaurant guest agent · always on
Every menu question answered. Every table intent captured.
Aigency helps guests discover the right dish, find a suitable booking slot, and explain a group request in one WhatsApp conversation. It answers from your approved restaurant information and hands valuable or sensitive moments to staff with the full story attached.
WhatsApp-firstApproved menu answersBooking-ready requestsHuman handoff
AI
Restaurant hostOnline · ready to help
•••
Tonight
Table for four tomorrow around 19:00. One guest is vegetarian and another avoids nuts.20:42
I can help. Your approved menu has several vegetarian dishes; allergy handling must be confirmed by the team. I found an open 19:15 slot. Indoor or terrace?20:42
Terrace, birthday dinner. A quiet corner if possible.20:43
I have prepared the 19:15 request with the dietary note, birthday, terrace preference, and contact details. The team will confirm the allergy plan and table.20:43
Table request ready for staff confirmation
01
Answers after hours
Guests can ask while the floor team is serving.
02
Guides menu discovery
Approved dishes, prices, availability, and policies stay consistent.
03
Captures booking intent
Party, timing, occasion, and requirements arrive together.
04
Protects staff attention
People step in for allergies, exceptions, and valuable groups.
Three restaurant conversations
A quick answer becomes a useful next action.
This Aigency Restaurant use case combines SalesGuy menu/listing flows, BookingsBot-style reservations, and staff handoff without pretending to replace a restaurant's POS or kitchen systems.
AI
Restaurant hostMenu discovery
Approved menu
What vegetarian mains do you have under R220?
The approved menu currently lists wild mushroom risotto at R195 and charred cauliflower steak at R210. The cauliflower dish is marked vegan.
Is the risotto gluten-free?
It is not marked gluten-free in the menu source, so I won't guess. I can ask the kitchen team to confirm.
Menu question routedNeeds kitchen
Dish · dietary question · guest contact · no unsupported promise
Useful answers, no confident guessing.
Guests see approved menu information. Missing or sensitive details reach the kitchen or floor team.
AI
Restaurant hostTable request
Booking slots
Can I book two people for Saturday at 18:30?
I found open configured slots at 18:15 and 18:45. Which works better?
18:45. Indoors please.
Done — the booking record has been created for 18:45. Reference: TBL-7H4K2. Save it for changes or cancellation.
Booking TBL-7H4K2Recorded
2 guests · Saturday 18:45 · indoor · source: WhatsApp
Only call it booked when a record exists.
Open slots, participant details, and booking references keep the guest and team aligned.
AI
Restaurant hostGroup dining
High-value enquiry
We need a client dinner for 28 people next month. Private room, set menu, around R32,000.
I can prepare this for the events team. What date, dietary mix, drinks preference, and decision deadline should I include?
14 September, six vegetarian, wine pairing, decision Friday.
Thank you. The complete group brief is ready for the restaurant team to review and respond.
Qualified group leadHigh value
28 guests · R32k · private room · set menu · wine pairing · decision Friday
Large tables arrive with the commercial detail.
The right owner receives headcount, budget, requirements, timing, and decision date together.
All exchanges are illustrative. Actual answers and actions depend on configured menu listings, stock records, booking slots, policies, integrations, and staff approvals.
Restaurant workflow building blocks
Answer. Understand. Record. Route. Remember.
Routine questions keep moving. Your people remain responsible for food safety, allergy decisions, unusual service recovery, final group proposals, and anything the system cannot verify.
Understand
Capture party size, date, time, dietary needs, occasion, budget, and intent.
Record
Create a booking or request only when the configured workflow supports it.
Route
Send kitchen, front-of-house, reservations, or events the complete brief.
Remember
Reuse consented guest context without making assumptions about this visit.
One queue for guest intent
Staff see what matters before they reply.
Aigency keeps the original conversation, structured request, current owner, and next action together. A person can take over at any point.
“Who is the guest, what are they asking for, and what must we confirm?”
Guest requests
Nomsa K.
Group dinner · 28 guests
Table TBL-7H4K2
Saturday · 18:45
Menu question
Kitchen confirmation
Qualified opportunity
Assign eventsClient dinner · 14 September
Private dinner for 28. Six vegetarian guests, set-menu request, wine pairing, R32,000 indicative budget, decision required Friday.
Party28 guests
BudgetAbout R32,000
FormatPrivate · set menu
DecisionBy Friday
Next actionAssign event owner and prepare proposal →
NK
Nomsa K.Returning guest · context updated today
Previous visits3 recorded bookings
Saved preferenceTerrace when available
Dietary noteVegetarian preference
Open requestClient dinner proposal
Contact channelWhatsApp
OwnerEvents team
Use saved preferences as a prompt to confirm, never as proof that today's guest requirements are unchanged.
Guest memory
Recognition without the awkward restart.
With permission, useful context can follow a guest across menu, booking, and group conversations. Authorised staff can see what was asked, what was saved, and what remains open.
- Previous booking references and open requests.
- Preferences the guest chose to save.
- Conversation and handoff history inside the workspace.
- Correction, export, deletion, and retention controls.
POPIA-aware by configuration. Collect only what the workflow needs, ask before reusing sensitive preferences, and keep role-based access and human review.
Connected where it matters
A guest layer, not a fictional restaurant stack.
Start with the workflows Aigency can support today, then scope deeper integrations around the systems your restaurant actually uses.
Listings, prices, availability, and policies must be approved and current. Unknown answers become staff questions.
A table is confirmed only when the configured booking path records it or staff confirms it.
Allergies, food safety, refunds, complaints, and unusual arrangements go to trained staff.
SalesGuy menu/listing flowsBookingsBot-style reservationsPublic booking linksWhatsApp entry pointsConfigured message deliveryStaff handoffNot a POS or kitchen display replacement
Serve guests, not repetitive questions
Let every restaurant conversation arrive ready for action.
Bring your menu, booking rules, and one real guest journey. We will show how Aigency can answer, capture, remember, and hand off around the way your team already works.