Workflow Documentation

Reference documentation for all workflows available in the system.

Catering Request Workflow

  • Workflow ID: catering-request
  • Purpose: Process inquiries about catering services
  • Trigger: Customer asks about catering or private events
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Event type
    • Event date
    • Event time
    • Event location
    • Approximate guest count
    • Special requirements
  • Procedure:
    1. Confirm catering is offered.
    2. Event type.
    3. Event date & time.
    4. Event location.
    5. Guest count.
    6. Special requirements.
    7. Run §3.
  • Response: Thanks for considering us. A team member will contact you soon.
  • Exceptions:
    • If catering is not available: I apologize, but we don't currently offer private catering services.

Complaint Handling Workflow

  • Workflow ID: complaint
  • Purpose: Process customer complaints appropriately
  • Trigger: Customer expresses dissatisfaction with experience
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Nature of complaint
    • Visit Date
    • Visit Time
    • Specific details of issue
    • Bill number (for billing issues)
  • Procedure:
    1. Express sympathy (no blame).
    2. Issue description.
    3. Visit date & time.
    4. Bill # (if billing).
    5. Run §3.
  • Response: A manager will review and call you at {phone}.

Handoff Workflow

  • Workflow ID: handoff
  • Purpose: Transfer complex inquiries to appropriate staff
  • Trigger: Inquiry beyond AI capability (complex events, private booking, accounts payable, etc.)
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Nature of inquiry
    • Inquiry Notes
    • Is urgent
  • Procedure: Use for accounts‑payable, sponsorships, complex events, etc. Gather summary notes → Run §3
  • Response: Thank you for the information. We'll follow up shortly.

Lost Item Workflow

  • Workflow ID: lost-item
  • Purpose: Assist customers in recovering lost items
  • Trigger: Customer calls about an item left at restaurant
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Item Description
    • Visit Date
    • Visit Time
    • Table Location
    • Server Name
  • Procedure:
    1. Item description (brand, colour, distinguishing features).
    2. Visit date.
    3. Visit time.
    4. (Optional) Table location or server name.
    5. Run §3.
  • Response: Thanks—we'll check lost‑and‑found and call you back.

Reservation Cancellation Workflow

  • Workflow ID: reservation-cancel
  • Purpose: Process reservation cancellations
  • Trigger: Customer wants to cancel a reservation
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Reservation Date
    • Reservation Time
  • Procedure:
    1. Say: "to find your reservation, I need some contact information" and run §3 Phone‑&‑Name.
    2. Date.
    3. Time.
  • Response: Your reservation is cancelled. Hope to see you another time!

Reservation Modification Workflow

  • Workflow ID: reservation-change
  • Purpose: Change existing reservation details
  • Trigger: Customer wants to modify an existing reservation
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Party size
    • Desired change
    • Original date
    • Original time
    • Desired date
    • Desired time
  • Procedure:
    1. Name on booking (spell).
    2. Original date.
    3. Original time.
    4. Desired change (date / time / party size).
    5. Run §3.
  • Response: Your change request is noted. We'll confirm shortly.

Late Arrival Notification Workflow

  • Workflow ID: reservation-late-arrival
  • Purpose: Record and manage late arrival notifications
  • Trigger: Customer calls to say they'll be late for reservation
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Original reservation time
    • Expected arrival time
    • Party size
    • Desired date
    • Desired time
  • Procedure:
    1. Run §3.
    2. Original reservation time.
    3. Expected arrival time (explain late policy if > 15 min).
  • Response: Thanks—we've noted your arrival around {time}.

New Reservation Workflow

  • Workflow ID: reservation-new
  • Purpose: Create new customer reservations
  • Trigger: Customer requests a new reservation
  • Required Information:
    • First name
    • Last name
    • Phone number
    • Is phone a mobile
    • Party size
    • Desired date
    • Desired time
  • Procedure:
    1. Party size.
    2. Desired date.
    3. Desired time (refuse if outside hours).
    4. Run §3 Phone‑&‑Name.
  • Response: I've sent your request for {date} at {time}. We'll confirm shortly.
  • Exceptions:
    • For parties of 8+: Please note that for parties of 8 or more, a 20% gratuity will automatically be added to the bill.