Know who and where.
Identify the staff role, outlet, table and seat. A proposed table-zone trigger would need explicit setup and testing.
HeyKOS hospitality academy / Clark’s example
Know the menu.
Connect the service.
A restaurant-specific academy turns the menu, cellar and service standards into confident recommendations. KOS carries that shared knowledge toward coordinated service.
Explore the steakhouse pairing guide and staff academy, then follow the proposed “Hey KOS” workflow—from drive-through orders and kitchen timing to sommelier requests and hotel coordination.
Interactive demonstration rebuilt for our site. Restaurant content awaits venue review; connected KOS ordering and orchestration remain development concepts.
HeyKOS hospitality academy · Clark’s example
Learn the menu.
Practice the service.
A native, interactive restaurant sample: explore the menu, rehearse a recommendation and follow a confirmed request into the proposed KOS workflow.
Demonstration content · Menu and beverage details await venue approval. KOS scenarios simulate actions; they do not send orders.
The hospitality academy
Learn it.
Say it naturally.
Chef, sommelier, bar and service knowledge become useful conversations. Explore the lesson text and practice checks below.
Kitchen Ordering & Orchestration System · Development preview
“Hey KOS.”
Say it. Review it. Confirm it.
The proposed earbud interface connects staff requests to the POS and KDS. At the pass, KOS coordinates station timing and acknowledgements under chef and expo control.
Keep the read-back.
Resolve uncertain items and modifiers. Staff approve the exact draft before a supported connection accepts it.
Close the handoff.
Carry the accepted ticket into the KDS. Role prompts request acknowledgement; overdue tasks return to expo.
Hey KOS · The voice of coordinated service
The right person.
The right task. The right time.
KOS is the proposed back-of-house expo, paired with the KDS to tell stations what to do and when. Across the wider KOS service workflow, that same coordination reaches the drive-through, dining room, bar, sommelier and hotel team.
KOS · Kitchen Ordering & Orchestration System
Use accepted tickets, course holds, station acknowledgements and reported readiness to propose the sequence of work. Route authorized fire instructions, synchronize station handoffs and call pickups. The KDS is the shared visual record; KOS is its two-way spoken companion. The chef or expo sets priorities and can intervene.
“Hey KOS” is the planned earbud-mic entry. Staff can give an instruction, report readiness, ask for status or acknowledge a task. Spoken order entry feeds the POS workflow; KOS coordinates execution after acceptance. Push-to-talk provides an alternative to the wake phrase.
From lane to line.
“Lane two’s order is confirmed. Route it to the kitchen.”
A connected drive-through voice system hands a confirmed order to the POS. Accepted items become station tasks in the KDS and KOS workflow, with the same order identity through pickup.
Know what fires next.
“Hey KOS, table twelve’s grill items will be ready in three minutes.”
Update the estimated station readiness, coordinate the remaining stations and alert expo to delays. Completion and pickup each require their own acknowledgement.
Bring the expertise to the table.
“Hey KOS, ask the sommelier to visit table twelve and arrange the selected bottle.”
Route the request with the table, selected wine and service timing. The sommelier confirms the bottle and availability, accepts the task and records the handoff.
Reach the person, wherever they are.
“Hey KOS, request the duty manager at table twelve in the north ballroom.”
Include outlet, room or event location and urgency. Assign the on-duty role, request acknowledgement and escalate to the designated alternate if unanswered. Staff can ask for status without leaving their station.
Request → Identify role & location → Confirm & assign → Acknowledge → Complete or escalate
Designed for quick service, restaurants, bars, banquets, room service and hotel operations. These are illustrative workflows and development objectives; vendor compatibility and wake-word hardware support require validation. Role permissions, order read-back, visible task status and manual fallback are part of the design.
Follow one service.
A guided illustration shows how the academy supports the KOS operating-system vision. These are sample conversations and transitions, with no live orders or integrations.
Staff academy · Sample training script
Confidence before the conversation.
“Tell me what makes this cut distinctive, then help me explain a pairing in one friendly sentence.”
The team learns a dish from the same reviewed record used for the menu guide. Tutoring and roleplay turn product facts into a natural conversation.
The shared information
Dish identity, approved description, pairing rationale and current revision.
The human checkpoint
Chef and beverage lead review the content; the manager observes practical service.
What a restaurant
engagement would include.
Use this sample to agree a defined content project first, with a separate brief for the connected software.
The content and training package
- Review the menu, recipes, wine list and house standards with the venue.
- Capture chef and bar footage and original dish photography as scoped.
- Produce descriptive clips, narration, pairing explanations and staff lessons.
- Add a floor guide, service rehearsal and knowledge checks.
- Agree approval, ownership, revision dates and ongoing menu updates.
The operating-system development
- Phone and drive-through voice connections, staff order entry and structured read-back.
- Validated POS and KDS connections with shared ticket identity.
- Two-way “Hey KOS” earbud interaction, KDS-paired expo timing, role routing and escalation.
- Floor-plan or captured 3D familiarization and a source-grounded virtual tutor.
- Staff permissions, audit history and a manual fallback throughout service.
Make it specific to your venue.
Start with your current menu, the people who approve it, and the service handoff you want to improve.
Directed voice channels / The latest KOS direction
Ask the station.
Bring the answer back.
HeyKOS is proposed as a broker for a specific request: use the approved academy record where appropriate, or ask the person with authority. Send the question to the assigned role, return the answer to the server and attach the exchange to the ticket.
A preparation decision.
Route temperature limits, off-menu requests, unavailable items and firing questions to the chef or expo. Their decision comes back before an order is changed.
A stock or drink question.
Check ingredients, cellar references, decanting and pour timing with the bar team. Confirm the actual selection before sending an order.
The table, ready.
Request steak knives, sharing plates, sauces or a reset with the table and course attached. Distinguish acknowledgement from completion.
A shared seating picture.
Request a turn extension, communicate an arrival or discuss re-seating. The host accepts the update and controls the seating plan.
Try the directed conversations in the Clark’s sample →
Illustrative design, with no live headset network or POS connection. Named roles receive the relevant prompts. Allergies go to trained people; payment stays in an approved payment flow.
The latest direction / Both sides of the pass
One menu record.
A shared understanding of service.
| Stage | The floor | The line |
|---|---|---|
| Now / Academy | Learn the plates, pairings and service sequence; rehearse with a manager. | Chef and bar lead approve the lessons and determine what information each role may access. |
| Next / Shadow service | Practice voice orders against sample or appropriately de-identified past tickets. | Replay station prompts and score routing and acknowledgement. Live service remains untouched. |
| Then / Hey KOS | Read back and confirm an order through a supported voice workflow. | Receive the accepted ticket in the KDS. Expo authorizes firing and tracks station readiness. |
| Later / KOS Shift | Explore venue-specific training and demonstrated readiness before accepting a shift. | Give a potential fill-in the venue’s menu, standards and role context before service. |
KOS Shift is a future concept. No staffing marketplace, external certification or shift placement is offered by this sample. Venue qualification, employment arrangements and shift terms would be separately developed.
Proposed voice workflow / One order or inquiry, seven handoffs
From a spoken request
to a visible record.
Wake
“Hey KOS” or push-to-talk starts the interaction. An optional, explicitly enabled table-zone trigger would be tested before use.
Hear
The phone interprets the request and identifies the staff member, outlet and table. Uncertain location is confirmed.
Match or route
Match approved items and modifiers, or route a live question to the named station. Use the same reviewed vocabulary taught in the academy.
Answer & read back
Return the station’s answer or repeat the exact draft order. Resolve uncertainty and wait for authorized staff confirmation before sending.
Send
A supported POS connection accepts the request with the correct table, seat and course.
Stage
The KDS shows the accepted ticket at the right station. Relevant runner and host views reflect confirmed task updates.
Log
Keep questions, station replies, read-backs, accepted changes and acknowledgements with the ticket, using venue-defined access and retention.
Phone, earbud and optional table-zone hardware are proposed components. No specific vendor compatibility is claimed. Allergy decisions go to trained staff; payments use an approved payment flow.