AETHERCollect the complete booking.
Date, time, party size, name and contact reach staff together.
FIJI RESTAURANTS + HOSPITALITY
Busy serving? AETHER can answer first.
Handle common questions and collect the date, time, party size, name and number for booking requests.
01
THE CUSTOMER REALITY
A familiar enquiry can still be incomplete.
A table request can arrive while the team is serving. Without a structured path, the date, party size, dietary needs or contact number can be spread across several messages.
Answer from approved information.
Surface opening hours, location, menu basics and known dietary options.
Move larger requests to the right person.
Collect date, group size, style, budget range and organiser contact.
02
THE USEFUL DETAILS
Collect what the team needs to act.
AETHER asks one relevant question at a time and remembers what the customer already said.
- Date and preferred time
- Number of adults and children
- Indoor, outdoor or event need
- Dietary and accessibility notes
- Occasion or special request
- Name and phone number
03
EXAMPLE ENQUIRIES
See the handoff before you build it.
These are realistic product-flow examples, not claimed client results.
Table for eight tomorrow?
- AETHER COLLECTS
- Date, time, party size, seating notes, name and number.
- TEAM RECEIVES
- The restaurant receives one clear request and confirms the table.
Can we book a birthday dinner for 30?
- AETHER COLLECTS
- Date, guests, service style, dietary needs, budget range and contact.
- TEAM RECEIVES
- The events lead gets enough context for a useful first call.
04
HOW IT GOES LIVE
Map, build, test and hand over.
The flow is shaped around the business's own information, rules and staff process.
- 01
Understand the current path
We map where customers find you, what they ask and where the conversation becomes slow or unclear.
- 02
Design the smallest useful flow
We decide which pages, questions, actions and connections are actually needed before the build begins.
- 03
Build and test real situations
The system is checked on phones and desktops using the kinds of enquiries your team receives.
- 04
Launch with a clear handoff
Your team knows what comes in, where it goes and which answers still need a person.
05
WHERE PEOPLE STEP IN
Automation has a clear boundary.
Staff confirm tables, large events, last-minute changes, allergies and complaints. Approved information can be answered automatically; uncertain details move to the team.
AETHER collects and clarifies. Your team keeps control of confirmation, judgement and the relationship.
FAQ
STRAIGHT ANSWERS
Questions before you start.
01Does an enquiry become a confirmed table?
Only when the system is connected to reliable availability and configured to confirm. Otherwise it is clearly marked as a request for staff approval.
02Can it answer menu questions?
Yes, using approved and maintained menu information. Daily specials and sold-out items need a live source or staff confirmation.
03Can it collect allergy information?
It can record a customer's note, but the restaurant must confirm what it can safely provide. The agent should not make medical or allergy guarantees.
04Can group enquiries go to an events person?
Yes. Routing rules can send larger or special-event requests to the agreed staff member.
START HERE
Show us how customers find you now.
Facebook page. Website. WhatsApp. Whatever you use. AETHER will ask a few questions before recommending anything.