Turn a message into a well-prepared reservation.
Collect the party size, time and useful preferences. Give the floor team the details before the guests arrive.
A table outside, if available.
Bring the conversation into venue operations.
Customer conversation
Venue operations, subject to scope
Order operations, separately scoped
From the first message to the floor team.
See how the request reaches the person who can confirm it.
Could we book a table for 6 on Saturday at 8?
9:41
Team handoverReservation request prepared
Collecting the request- Party
- 6 guests
- Requested
- Saturday · 20:00
- Preference
- Terrace, subject to availability
- Owner
- Reservations team
The manager confirms availability and seating before the booking is final.
Read the full conversation
- Customer: Could we book a table for 6 on Saturday at 8?
- Assistant: Hi, I’m the restaurant’s AI assistant. I can request that for you. Any seating preferences for the team?
- Customer: Somewhere outside if possible.
- Assistant: I’ve passed your request for six at 20:00 to the team, including the terrace preference. They’ll confirm availability.
The floor team knows who is arriving.
Party size, agreed time and requests stay attached to the reservation. Anything outside the venue’s approved policy waits for a manager.
Collect the reservation
Ask for date, time and party size. Capture requests without promising they can be accommodated.
Check the availability
Use the actual reservation source and route larger or unusual bookings to the manager.
Prepare the floor
Attach the confirmed details and outstanding requests to the team’s reservation record.
Your team stays in control.
Allergy handling and special requests require the venue’s confirmation. Deposits, payment holds and waitlist automation are separately scoped, not implied by reservation intake.
Connections and setup
The example shows a proposed workflow. Connections, permissions and acceptance checks are agreed for your systems before a pilot.
API access and your plan determine what can be connected. Tool logos identify possible systems, not a partnership.
Map one real handover
A working sheet for the source, next action, owner and exception at each step.
Open the resourceBefore we get started.
Who stays in control?
We start with supervised work: Knot prepares, a named person reviews. Any permission to send, book or update a record is agreed action by action and tested before it is enabled.
Can we keep our existing software?
That is the starting point. We check API access, your subscription, permissions and the records the workflow needs. A logo here identifies a possible tool, not a preinstalled connector or a formal partnership.
Will it collect a deposit automatically?
Not as part of this reservation example. Payment handling requires a separate approved flow, provider access and clear cancellation terms.
Your business.
A place to start.
Start with your company website, then tell us what you’d like to improve. We’ll find a useful resource or a next step.
We read public pages and use AI to suggest Knot resources. Don’t include confidential information. Privacy