The story of every plate.
Chef and bar interviews, dish photographs and video, accurate descriptions, wine pairing reasons and inviting language for the table.
HeyKOS · Hospitality academy + Kitchen Ordering & Orchestration System
Train the team.
Coordinate the service.
Turn your menu, wine list and service standards into a practical academy for the people who represent your restaurant.
Start with reviewed lessons, descriptive media and friendly recommendations. Build toward “Hey KOS”—voice ordering and coordinated service through the POS, kitchen display and each team member’s earbud.
Academy production is scoped per venue. Connected POS, KDS and voice orchestration are proposed development work.
The first engagement / Your hospitality academy
Give the team
something useful today.
One approved menu record becomes several useful training and selling tools. Start with a defined department or menu, review it with your chef and beverage lead, then expand.
Your standards, made teachable.
Short lessons, narration, steps of service, roleplay, online practice checks and a floor guide built from your operation.
Keep the knowledge current.
Named content owners, approval dates, menu revisions and manager-observed service practice. Agree a maintenance scope for seasonal changes.
Captured 3D familiarization, trainer avatars and interactive tutoring can be scoped as additional production. They are not functioning features of this demonstration.
A focused pilot / A clear production brief
One venue. One menu.
A complete training sample.
Bring the current menu, beverage list and house standards. We agree the items, capture sessions, lesson formats, approvals and delivery dates before production. The proposal separates content production, ongoing updates and any software development.
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.
KOS development / Prove each connection
From trained people
to coordinated action.
The academy’s reviewed information provides a starting point for later software. Each operational phase needs its own agreed scope, technical access and service testing.
Rehearse the workflow.
Replay sample tickets and test prompts, station routing, read-back and escalation without changing live orders.
Connect one service.
Validate menu IDs, seats, courses, modifiers and duplicate prevention with one supported POS and kitchen display connection.
Put the workflow in reach.
Test two-way staff voice, earbuds and optional table zones. Confirm the request, record acceptance and track the assigned person’s acknowledgement.
Broader use includes drive-through intake, dining-room requests, sommelier visits, room service and hotel team coordination. Vendor support, hardware behavior and performance require validation; the ordinary manual workflow remains available.
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.