All professions
Commerce

Let the team serve the room while the desk organizes the next request.

The restaurant desk can answer approved menu, hours and policy questions, collect a reservation or catering request and prepare an order draft once the actual POS or reservation system is selected.

VERIFIED OUTCOME

Guest question → menu/policy answer → reservation, catering or order request

Restaurant flows are designed; dedicated API profile is still pending

RestaurantsChecking API
Prepared
Real API when active. Fictional test data only. No external action is performed here.
DEMO RECEPTION

I am the restaurant demo host. Use fictional details. I can explain approved menu and request steps; no table or order is confirmed here.

Do not enter real names, phones, account numbers, medical information or secrets.

01

What a useful day looks like.

The agent does not “do everything.” It moves each conversation to the next authorized state and shows what is still waiting.

  1. 01

    Menu question

    Uses approved menu facts and escalates uncertain allergen questions.

    Answered
  2. 02

    Reservation

    Captures party size and preference without promising a table.

    Pending
  3. 03

    Catering/order

    Prepares a reviewable request after menu, minimum and delivery rules are connected.

    Pilot
DELA / RESTAURANTSRECEIPT
OUTCOME OBJECTMenu question

Source recorded · human owner visible · destination pending until a verified response arrives.

Reviewable
02

More than chat: the complete profession desk.

Each module earns its status separately. A real conversation never implies that every external system is connected.

ANSWERPilot / Piloto

Approved answers

Services, hours, policies and terminology from reviewed sources.

CAPTUREPilot / Piloto

Structured requests

Turns a conversation into the exact fields the team needs.

SCHEDULEPilot / Piloto

Agenda

Availability, request and confirmation stay separate and visible.

RECORDS— / —

Records

Keeps the client or patient trail organized under the right permissions.

BILLINGPilot / Piloto

Billing

Prepares reviewable billing work without inventing fiscal validity.

PAYMENTSPilot / Piloto

Payments

Uses approved providers and marks paid only after a verified receipt.

ORDERSPilot / Piloto

Orders

Builds a clean draft; stock, price and submission remain controlled.

FOLLOWUPPilot / Piloto

Follow-up

Recovers open work with consent, ownership and a visible state.

INTEGRATIONSPilot / Piloto

Connections

Read first, test safely and require evidence from the destination.

Professional boundary

No table, allergen guarantee, order, charge or delivery is confirmed in the public demo.

03

What is connected, what needs a pilot, and what waits.

No integration becomes “live” because its logo appears in a catalog. It must pass the exact workflow test.

Profession agentPilot

Dedicated Lety profile must pass acceptance.

POS / reservation systemPilot

Exact product and version must be confirmed.

Delivery / paymentsExpansion

Separate destination and transaction acceptance.

See the DelAgentIA connection contract
04

Questions for Restaurants.

Specific answers, not generic AI promises.

Can it answer allergen questions?

Only from approved, maintained information and with an uncertainty handoff. It cannot make a medical safety guarantee.

Can it take an order?

It can prepare a draft. Submission requires the exact POS/order system and a returned receipt.

Is the restaurant bot live?

The page and shared gateway are prepared; the dedicated Lety agent is not labelled active until its acceptance test passes.

RESTAURANTS

Start with one outcome. Connect the rest only after it works.

The initial web experience can prove the conversation. Operational connections are scoped, tested and priced separately.

Build this desk