D·DDianDotHospitality operating system
Menu

A DIANDOT SERVICE WALKTHROUGH

See how the whole room moves
as one service.

This is a DianDot product walkthrough, not a restaurant booking page. Follow the same connected flow an independent restaurant team uses from the first guest arrival to the final report.

01guest journey
02front-of-house actions
03back-of-house outputs
04admin decisions

CLICK THROUGH THE SERVICE

See the product working.

Use the stages below. This is a neutral DianDot demo with sample data, not a live restaurant account.

DEMO DATA · NO REAL BOOKINGS
GUEST JOURNEYLIVE AVAILABILITY

A real available time, not a fake slot.

DianDot checks the room before it offers a guest a time. Party size, table duration, service hours and notice rules stay visible.

Tonight18:30
Party4 guests
Deposit£20
  • ✓Capacity-aware booking
  • ✓Configurable deposits
  • ✓Clear guest confirmation
THU 20 AUG4 guests
17:30Full
18:30Available
19:00Available
18:30 · Table suited£20 deposit · 90 minute table timeCONTINUE
01 / 06

ONE SHIFT · ONE OPERATING PICTURE

The detail changes. The service flow stays clear.

DianDot keeps the right context moving to the next person, so a booking becomes a table, a table becomes an order, and an order becomes useful information after service.

BEFORE SERVICE

Prepare the room.

See reservations, capacity, table time and arrivals before the first guest sits down.

DURING SERVICE

Move the next action.

Seat guests, take orders, route dishes and keep the kitchen and front of house aligned.

AFTER SERVICE

Understand the shift.

Review sales, refunds, VAT, service charge and the changes that shaped the night.

Reserve.
Seat.
Order.
Learn.
The same service story, visible from the floor to the admin view.

WHAT A TEAM ACTUALLY SEES

Each role gets the useful part of the same story.

The host sees arrivals and table fit. The floor sees guests and orders. The kitchen sees timed tickets. The admin sees the pattern after the room has gone quiet.

HOSTLive availability, party size, arrival notes and table context.
FLOORMenus, options, allergens, bills, payments and protected approvals.
KITCHENStation-specific tickets, timing and clear completion state.
ADMINCloud workspace, analytics, permissions and daily reporting.

THE PRODUCT IN MOTION

Designed to reduce the handovers that slow service down.

There is no China Fusion account or customer booking in this demo. It is a neutral view of what DianDot is built to connect for any restaurant.

01Reservations and capacity inform the floor before the shift begins.
02Order detail travels to the correct kitchen, bar or customer output.
03Every authorised device works from the same restaurant workspace.

Explore the product areas

Go deeper into the platform, reservations, KDS, analytics or hardware.

Explore DianDot