Common guest / front-desk requests
- Are you open tonight?
- Do you have a table for four?
- Can I move my reservation?
- Can I cancel?
- Where are you located?
- Do you have outdoor seating?
- Can someone call me back?
- What are your opening hours?
Restaurants
Answer guests. Handle reservations. Keep the front desk connected.
NLDONA helps restaurants answer routine questions, manage supported reservation requests and keep guest conversations connected to the same business schedule and operations.
Incoming call
“Do you have a table for four on Friday at 7?”
AI Receptionist
“Friday at 19:00 is available for four people.”
Guest
“Yes, please.”
Reservation
Friday · 19:00 · Party of 4 · Confirmed
Operations
Reservation created · Confirmation ready
Conversation → capacity-aware reservation → operational outcome. Not POS or ordering.
Front desk reality
Guests ask the same questions every day.
NLDONA is for guest and front-desk conversations — not restaurant POS or kitchen systems.
Outside NLDONA’s restaurant scope
POS, food ordering, delivery platforms, kitchen displays, floor plans and table assignment are not NLDONA’s product. Unsupported or unusual requests hand off to your team with relevant guest context.
AI Receptionist
Let NLDONA handle routine calls without separating reservations from the business.
NLDONA helps with repetitive guest and reservation work. It does not replace your restaurant staff.
- Answer approved restaurant questions
- Understand reservation intent and party size
- Check available reservation options
- Create, reschedule and cancel supported reservations
- Preserve appropriate guest context
- Hand off when a person is needed
NLDONA assists the front desk. Your team remains part of the operating model.
Reservations
Reservations that understand party size and capacity.
Party size, time windows and capacity use NLDONA’s shared scheduling model — described in restaurant language.
- Party
- 4 guests
- Date
- Friday
- Requested
- 19:00
- Available
- 18:30 · 19:00 · 20:15
- Selected
- 19:00
Confirmed on the restaurant schedule
Illustrative restaurant language over shared NLDONA scheduling. Not a floor plan, seat map, table-joining engine or dining-duration optimiser.
Reschedule
- Existing reservation: Friday · 19:00 · party of 4
- Guest asks for 20:00 instead
- NLDONA checks current availability and capacity
- Guest selects a supported option
- Old capacity released · new reservation confirmed
- Confirmation and reminders update
Cancel
- Reservation cancelled
- Capacity becomes available
- Future reminders stop or adjust
- Operations reflects the outcome
Guest context
Useful front-desk context without pretending to be a restaurant CRM.
NLDONA Customers helps the front desk with contact and reservation context. It is not a loyalty or marketing profile system.
- Name
- Phone / email where available
- Preferred language
- Preferred confirmation channel
- Upcoming reservation
- Relevant previous booking activity
Phone or email may help locate context. They do not automatically prove identity.
No inferred dining preferences, allergy clinical truth, loyalty status, spending profiles or marketing segmentation.
Keep the reservation connected after confirmation.
Supported reminder behavior follows the restaurant’s booking outcome.
- Reservation created
- Configured reminder policy applies
- Customer communication is sent where configured
- Changes or cancellation update future reminder behavior
Not marketing campaigns, promotional SMS or loyalty automation.
Capture demand when nothing fits — with confirmation before booking.
When no suitable reservation is available, your team can capture waitlist demand in scheduling. Offers require customer confirmation before a booking is created.
- No suitable reservation available
- Operator-supported waitlist capture where accepted
- Capacity opens
- Eligible guest is offered a time
- Guest confirms
- Reservation created
Waitlist offers require customer confirmation before a booking is created. Public Booking waitlist self-serve join is not claimed as live. NLDONA does not auto-book from waitlist without confirmation.
Human handoff
When the request needs your team, the context follows.
Unusual groups, unsupported requests or questions outside approved Knowledge escalate with relevant context.
- Guest asks something outside safe AI scope
- NLDONA stops or escalates
- Restaurant team receives relevant guest and reservation context
- Guest
- Current request
- Reservation context
- Actions already completed
- Open issue
No chain-of-thought exposure. NLDONA does not invent POS or kitchen answers before handoff.
AI Secretary & Operations
Know what NLDONA handled — and what still needs the restaurant.
Business-facing visibility for outcomes and Needs Attention — illustrative states only.
Today
Upcoming reservations on supported channels.
Needs Attention
Guest waiting · handoff waiting · calendar connection · knowledge gap.
Recent outcome
Reservation moved.
Illustrative operations states. Not fake performance KPIs.
Knowledge
Answers based on information your restaurant approves.
Approved restaurant business knowledge — not live inventory or POS truth.
- Opening hours
- Location and parking
- Reservation policy
- Cancellation policy
- Approved service information
- Business FAQs
Restaurant-owned approved content. Not real-time item availability, stock, ingredient inventory or menu pricing authority.
Integrations
Connect calendars, email and approved files the restaurant already uses.
Only currently supported NLDONA integrations.
Google Calendar / Microsoft Calendar
External busy constraints and outward booking projection where configured.
Gmail
Bounded business email workflows with human confirm-send where required.
Google Drive
Selected approved files as governed Knowledge.
Not OpenTable, Resy, Quandoo, SevenRooms, TheFork, Lieferando, Uber Eats, Wolt, POS or delivery-platform integrations.
How setup works
Set NLDONA up around the restaurant you already run.
Guided setup in restaurant language — no need to understand backend abstractions.
- 01
Business information
Add the public details your front desk already uses.
- 02
Reservation rules
Configure availability, capacity and reservation services your guests request.
- 03
Knowledge
Add approved hours, policies and business FAQs.
- 04
Connect tools
Connect supported calendars, email and Knowledge files.
- 05
Test
Try conversations and reservation scenarios under your review.
- 06
Go live
Activate when the restaurant is ready.
Concrete guest flows restaurants recognise.
Shared NLDONA capabilities, described in restaurant language.
New reservation
- Party size requested
- Availability
- Reservation
- Confirmation
Reschedule
- Existing reservation
- New availability
- Confirmation
- Capacity updated
Cancellation
- Reservation cancelled
- Capacity released
- Reminder adjusted
Outside AI scope
- Request identified
- Human handoff
- Guest context passed
Trust
AI for guest and reservation operations — not restaurant management software.
Clear boundaries keep NLDONA useful without overclaiming POS or kitchen systems.
Approved restaurant information
Answers follow knowledge the restaurant reviews and approves.
Controlled business actions
Reservation actions stay inside restaurant policy and NLDONA authority.
Human handoff
Unsupported or sensitive requests escalate to your team.
Governed access
Customer data access remains under tenant permissions.
FAQ
Common questions about NLDONA for restaurants.
Short answers based on current product truth.
What can NLDONA do for a restaurant?
Help with routine guest conversations, supported reservations with party size and capacity, changes, reminders, approved Knowledge, handoff and operational visibility.
Can NLDONA answer restaurant calls?
Yes, on supported voice and messaging channels for approved front-desk and reservation flows.
Can NLDONA make reservations?
Yes, for supported reservation flows that follow the restaurant’s availability, capacity and booking rules.
Can NLDONA handle party size?
Yes. Party size is part of NLDONA’s shared reservation and capacity scheduling model.
Can guests reschedule or cancel?
Yes, within restaurant policy. NLDONA updates shared capacity and related reminders.
Does NLDONA support a waitlist?
Yes. Your team can capture waitlist demand in scheduling. Offers require customer confirmation before a booking is created. Public Booking waitlist self-serve join is not claimed as live.
Can NLDONA send reminders?
Yes, where reminder policies are configured for booking outcomes.
Can a person take over a conversation?
Yes. NLDONA can hand off with relevant guest and reservation context so your team can continue.
Does NLDONA integrate with my POS?
No. NLDONA does not claim POS integration or POS replacement.
Does NLDONA take food orders?
No. NLDONA is not an ordering, delivery or kitchen system.
Is NLDONA a restaurant-management system?
No. NLDONA is not positioned as complete restaurant software, an all-in-one restaurant management platform, or a floor-plan table-management system.
Can I test it with my website?
Yes. Paste your public restaurant website to start a temporary demo under your review. Nothing becomes Production truth until you activate.
Try NLDONA
See how NLDONA could fit your restaurant.
Paste your public restaurant website to start a temporary demo under your review.
Public information only. Demo experiences stay isolated from production.