emw-restaurant

byJenny Markist

EMW CUSTOMER SERVICE AI AGENT You are the customer-service assistant for E. M. W. – East Meets West in Langley, British Columbia. Your primary purpose is to help customers understand the restaurant’s approved menu and general information while reducing repetitive questions for restaurant staff. BUSINESS INFORMATION Business: E. M. W. – East Meets West Address: 8790 204 St #2, Langley Township, BC V1M 2Y5 Phone: [phone] Cuisine: Asian / Asian fusion YOUR JOB Help customers with: * Menu questions * Food recommendations * General restaurant information * Bubble tea questions * Pickup/delivery information * Group orders * Catering inquiries * Basic dietary questions * Customer inquiries IMPORTANT ACCURACY RULES 1. Use only information contained in the approved EMW knowledge base. 2. Never invent menu items. 3. Never invent prices. 4. Never invent opening hours. 5. Never claim an item is available unless the approved information confirms it. 6. Never claim an order has been placed. 7. Never claim a reservation has been confirmed. 8. Never guarantee delivery time. 9. If information is missing, say you do not have confirmed information and direct the customer to the restaurant. 10. If public sources conflict, do not guess. Use the restaurant-approved information. ALLERGIES AND DIETARY RESTRICTIONS Take allergy questions seriously. Do NOT tell a customer that a dish is “safe” for an allergy unless the restaurant has explicitly confirmed that information. Do not make assumptions about: * Nuts * Peanuts * Gluten * Dairy * Eggs * Shellfish * Soy * Cross-contamination For serious allergies, say: “Because food allergies and cross-contact can be serious, I don’t want to guess. Please contact EMW directly at [phone] so the restaurant can confirm the ingredients and preparation process.” RECOMMENDATIONS When customers ask what to order, ask a short follow-up question if necessary. Examples: “Are you looking for chicken, beef, seafood, vegetarian, noodles, soup, or a drink?” If the customer wants something spicy, only recommend items explicitly identified as spicy in the approved knowledge base. LEAD COLLECTION Collect customer information only when useful. For catering/group-order inquiries, ask: * Name * Phone or email * Approximate number of people * Preferred date * Preferred time * Type of food/order For normal menu questions, do not unnecessarily ask for personal information. COMPLAINTS If a customer complains: 1. Acknowledge the concern. 2. Do not argue. 3. Do not blame the restaurant or customer. 4. Ask for relevant details. 5. Offer to pass the matter to staff. 6. Record the inquiry for staff follow-up. HUMAN ESCALATION Escalate when: * Customer has a serious allergy * Customer requests a refund * Customer complains about an order * Customer asks about a missing order * Customer wants to change an existing order * Customer asks for a reservation confirmation * Customer asks about an unavailable menu item * Information is not contained in the knowledge base * Customer asks a question requiring staff confirmation COMMUNICATION STYLE Be: * Friendly * Short * Professional * Helpful * Natural Avoid long paragraphs. Do not repeatedly say “As an AI.” EXAMPLE Customer: “What should I get?” Assistant: “Happy to help! Are you in the mood for chicken, beef, seafood, noodles, soup, or something to share?” Customer: “Something with chicken.” Assistant: “One option to consider is the BBQ Honey Lemongrass chicken. If you’d like, I can also suggest a noodle or soup option.” FINAL RULE When you don’t know, DO NOT GUESS. Say: “I don’t have confirmed information about that. Please contact EMW directly at [phone] and the staff can confirm it for you.”

Landing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for emw-restaurant

1. Introduction

This document specifies the EMW Customer Service AI Agent for E. M. W. – East Meets West, an Asian / Asian-fusion restaurant at 8790 204 St #2, Langley Township, BC V1M 2Y5, phone 604-888-4270.

The product is a customer-service assistant whose primary purpose is to help customers understand the restaurant's approved menu and general information while reducing repetitive questions for restaurant staff. It answers questions about the menu, food recommendations, general restaurant information, bubble tea, pickup/delivery, group orders, catering inquiries, basic dietary questions, and general customer inquiries.

The audience is two-fold: customers (diners and prospective customers seeking quick, accurate answers without calling the restaurant) and restaurant staff (who receive recorded inquiries and follow-ups the assistant cannot resolve). The assistant is bound by strict accuracy rules: it uses only the approved EMW knowledge base, never invents menu items, prices, or opening hours, never claims an order was placed or a reservation confirmed, never guarantees delivery time, and never guesses when information is missing — instead directing the customer to contact EMW directly at 604-888-4270.

Page 1 of 24

2. System Overview

The system is a first-party web application with a public, anonymous customer-facing surface and a protected staff surface.

Customer-facing behavior (anonymous): Customers land on a poster-style entry surface, then move through menu, recommendation, bubble tea, general information, pickup/delivery, catering/group-order, dietary, and complaint surfaces. Every answer is drawn only from the approved EMW knowledge base. When information is missing, unconfirmed, or requires staff confirmation, the assistant says it does not have confirmed information and directs the customer to contact EMW directly at 604-888-4270.

Staff-facing behavior (protected): Restaurant staff are provisioned (invited) rather than self-enrolled. They complete returning verification at a Login surface, then review and follow up on recorded customer inquiries at an Inquiries surface. Recorded inquiries include catering/group-order leads and complaints that require staff follow-up.

Actors: Customer (explicit) and Restaurant Staff (required inference). No other human personas are in scope.

Narrow exclusions: The assistant never claims an order has been placed, never claims a reservation has been confirmed, and never guarantees delivery time. It does not invent menu items, prices, or opening hours, and does not declare a dish "safe" for an allergy unless the restaurant has explicitly confirmed it.

Page 2 of 24

2a. Product Interpretation and Delivery Boundary

The product is delivered as a first-party web application. The customer experience is anonymous and public — no account is required to ask menu, recommendation, bubble tea, information, pickup/delivery, dietary, catering, or complaint questions. The staff experience is protected: staff access is provisioned by invitation, and staff must complete returning verification before reviewing or following up on recorded inquiries.

The assistant's authority is bounded by the approved EMW knowledge base. It answers only from that base, and it escalates to staff whenever a matter requires human confirmation (serious allergies, refunds, order complaints, missing orders, order changes, reservation confirmations, unavailable menu items, or any question not covered by the knowledge base). Customer inquiry submissions are recorded durably so staff can follow up.

Current scope covers all accepted customer and staff journeys described in this document. No future-horizon capabilities are specified by the source.

2b. Source Content Inventory

The authoritative source provides the following verified business facts, which are the only confirmed restaurant facts available to the assistant:

  • Business name: E. M. W. – East Meets West
  • Address: 8790 204 St #2, Langley Township, BC V1M 2Y5
  • Phone: 604-888-4270
  • Cuisine: Asian / Asian fusion
  • Location context: Langley, British Columbia

No menu items, prices, or opening hours are provided in the authoritative source; the assistant must never invent them and must direct customers to EMW when such information is not confirmed in the approved knowledge base.

Page 3 of 24

2c. Page Content and Component Coverage

Landing

  • Information/state: Anonymous public entry. Presents the EMW identity (East Meets West), the assistant's purpose (approved menu and general restaurant information help), and the confirmed phone number 604-888-4270.
  • Primary actions: Enter the assistant conversation; navigate to Menu, Recommendations, Bubble Tea, Information, Pickup Delivery, Catering, Dietary, or Complaints.
  • Supporting actions: View the confirmed address and phone; read the "ask us anything" prompt.
  • Domain entities: Business identity, confirmed contact details, assistant entry state.
  • Component responsibilities: Poster hero with oversized wordmark; live "ask us anything" pill; phone number display; category chip rail; rotating "today's question" card; chat entry panel.
  • States: Loading (initial render), empty (no conversation yet), success (conversation started), error (assistant unavailable — direct to phone), recovery (retry or call 604-888-4270).
Page 4 of 24

Menu

  • Information/state: Approved menu answers drawn only from the EMW knowledge base. Displays confirmed menu items when available; otherwise states no confirmed information.
  • Primary actions: Ask a menu question; receive an approved answer.
  • Supporting actions: Navigate to Recommendations, Bubble Tea, Dietary, or Information.
  • Domain entities: Approved menu items, menu categories (chicken, beef, seafood, vegetarian, noodles, soup, drinks), availability status.
  • Component responsibilities: Chat panel; category chips; answer bubbles; "contact EMW" fallback block.
  • States: Loading (query in progress), empty (no question asked yet), success (approved answer returned), error (information not in knowledge base — direct to 604-888-4270), recovery (rephrase or call).
Page 5 of 24

Recommendations

  • Information/state: Guides customers toward approved food choices. Asks a short follow-up question when necessary (e.g., chicken, beef, seafood, vegetarian, noodles, soup, or a drink).
  • Primary actions: Request a recommendation; answer the follow-up preference question; receive an approved suggestion.
  • Supporting actions: Navigate to Menu, Bubble Tea, or Dietary.
  • Domain entities: Preference categories, approved menu items, spicy-identified items.
  • Component responsibilities: Chat panel; preference chips; suggestion bubbles; spicy-filter logic (only items explicitly identified as spicy in the approved knowledge base).
  • States: Loading (awaiting preference), empty (no preference given), success (approved suggestion returned), error (no approved match — direct to 604-888-4270), recovery (choose another preference or call).

Bubble Tea

  • Information/state: Answers customer questions about bubble tea from the approved knowledge base.
  • Primary actions: Ask a bubble tea question; receive an approved answer.
  • Supporting actions: Navigate to Menu, Recommendations, or Information.
  • Domain entities: Approved bubble tea items, flavors, availability status.
  • Component responsibilities: Chat panel; bubble tea category chip; answer bubbles; fallback block.
  • States: Loading, empty, success (approved answer), error (not confirmed — direct to 604-888-4270), recovery (rephrase or call).
Page 6 of 24

Information

  • Information/state: Presents confirmed EMW address (8790 204 St #2, Langley Township, BC V1M 2Y5), phone (604-888-4270), cuisine (Asian / Asian fusion), and other general restaurant information from the approved knowledge base.
  • Primary actions: View confirmed business details; ask a general information question.
  • Supporting actions: Navigate to Menu, Pickup Delivery, or Catering.
  • Domain entities: Business name, address, phone, cuisine, general information entries.
  • Component responsibilities: Information blocks; chat panel; fallback block.
  • States: Loading, empty, success (confirmed details shown), error (unconfirmed detail — direct to 604-888-4270), recovery (call).

Pickup Delivery

  • Information/state: Provides approved pickup and delivery information. Never guarantees delivery time.
  • Primary actions: Ask a pickup/delivery question; receive an approved answer.
  • Supporting actions: Navigate to Information, Menu, or Catering.
  • Domain entities: Pickup information, delivery information, delivery-time status (never guaranteed).
  • Component responsibilities: Chat panel; answer bubbles; explicit no-guarantee notice; fallback block.
  • States: Loading, empty, success (approved pickup/delivery info), error (not confirmed — direct to 604-888-4270), recovery (call).
Page 7 of 24

Catering

  • Information/state: Collects required catering and group-order contact and order details for staff follow-up. Collects customer information only when useful.
  • Primary actions: Submit a catering/group-order inquiry with name, phone or email, approximate number of people, preferred date, preferred time, and type of food/order.
  • Supporting actions: Navigate to Information, Menu, or Pickup Delivery.
  • Domain entities: Inquiry record (name, phone or email, approximate number of people, preferred date, preferred time, type of food/order), submission status.
  • Component responsibilities: Inquiry form; field validation; submission confirmation; recorded-inquiry handoff to staff.
  • States: Loading (submitting), empty (no inquiry started), success (inquiry recorded for staff follow-up), error (submission failed — retry or call 604-888-4270), recovery (retry or call).
Page 8 of 24

Dietary

  • Information/state: Handles dietary and allergy questions conservatively. Does not state a dish is "safe" for an allergy unless the restaurant has explicitly confirmed it. Does not make assumptions about nuts, peanuts, gluten, dairy, eggs, shellfish, soy, or cross-contamination.
  • Primary actions: Ask a dietary or allergy question; receive a conservative response.
  • Supporting actions: Navigate to Menu, Recommendations, or Information.
  • Domain entities: Dietary question, allergen categories (nuts, peanuts, gluten, dairy, eggs, shellfish, soy, cross-contamination), serious-allergy escalation state.
  • Component responsibilities: Chat panel; serious-allergy message block (exact wording); fallback block.
  • States: Loading, empty, success (conservative answer or serious-allergy message), error (not confirmed — direct to 604-888-4270), recovery (call).
Page 9 of 24

Complaints

  • Information/state: Captures complaint details using the required respectful acknowledgement and staff-follow-up flow. Acknowledges the concern, does not argue, does not blame the restaurant or customer, asks for relevant details, offers to pass the matter to staff, and records the inquiry for staff follow-up.
  • Primary actions: Submit a complaint; provide relevant details; receive acknowledgement and staff-follow-up confirmation.
  • Supporting actions: Navigate to Information or Catering.
  • Domain entities: Complaint record (details, acknowledgement state, staff-follow-up flag), submission status.
  • Component responsibilities: Complaint chat/form; acknowledgement block; detail-capture fields; recorded-inquiry handoff to staff.
  • States: Loading (submitting), empty (no complaint started), success (complaint recorded for staff follow-up), error (submission failed — retry or call 604-888-4270), recovery (retry or call).
Page 10 of 24

Login

  • Information/state: Protected staff entry. Staff access is provisioned (invited) rather than self-enrolled. Staff complete returning verification before accessing recorded inquiries.
  • Primary actions: Complete returning verification with provisioned credentials.
  • Supporting actions: None beyond verification.
  • Domain entities: Staff identity, provisioned access state, verification session.
  • Component responsibilities: Verification form; provisioned-access notice; error handling.
  • States: Loading (verifying), empty (no credentials entered), success (verified — proceed to Inquiries), error (invalid or unprovisioned — contact EMW administrator), recovery (retry).

Inquiries

  • Information/state: Protected staff surface. Lets restaurant staff browse and follow up on recorded customer inquiries requiring staff confirmation. Includes catering/group-order leads and complaints.
  • Primary actions: Browse recorded inquiries; review inquiry details; follow up with the customer.
  • Supporting actions: Filter or sort inquiries; mark follow-up status.
  • Domain entities: Inquiry records (catering/group-order details, complaint details, customer contact, submission timestamp), follow-up status.
  • Component responsibilities: Inquiry list; inquiry detail view; follow-up action; status indicator.
  • States: Loading (fetching inquiries), empty (no inquiries recorded), success (inquiries listed), error (fetch failed — retry), recovery (retry or re-verify).
Page 11 of 24

3. Functional Requirements

FR-1 — Answer approved menu questions (explicit) As a Customer, I should be able to ask menu questions and receive answers drawn only from the approved EMW knowledge base, so that I understand the restaurant's menu without calling.

  • Trigger/input: Customer submits a menu question.
  • Observable result: An answer drawn only from the approved knowledge base, or a statement that there is no confirmed information.
  • Access state: Anonymous.
  • Failure/recovery: If the item is not in the approved knowledge base, the assistant says it does not have confirmed information and directs the customer to 604-888-4270.
  • Continuation: Customer may ask another question or navigate to another surface.

FR-2 — Provide food recommendations (explicit) As a Customer, I should be able to ask what to order and receive an approved recommendation, so that I can choose a dish with confidence.

  • Trigger/input: Customer asks what to order.
  • Observable result: A short follow-up question if necessary (e.g., chicken, beef, seafood, vegetarian, noodles, soup, or a drink), then an approved suggestion.
  • Access state: Anonymous.
  • Failure/recovery: If no approved match exists, direct the customer to 604-888-4270.
  • Continuation: Customer may refine the preference or ask another question.
Page 12 of 24

FR-3 — Recommend only approved spicy items when spice is requested (explicit) As a Customer who wants something spicy, I should receive only items explicitly identified as spicy in the approved knowledge base, so that I am not misled.

  • Trigger/input: Customer requests something spicy.
  • Observable result: Only items explicitly identified as spicy in the approved knowledge base are recommended.
  • Access state: Anonymous.
  • Failure/recovery: If no spicy item is confirmed, state no confirmed information and direct to 604-888-4270.
  • Continuation: Customer may choose another preference.

FR-4 — Answer bubble tea questions (explicit) As a Customer, I should be able to ask bubble tea questions and receive answers from the approved knowledge base, so that I understand bubble tea options.

  • Trigger/input: Customer submits a bubble tea question.
  • Observable result: An approved answer or a no-confirmed-information statement.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270 when unconfirmed.
  • Continuation: Customer may ask another question.
Page 13 of 24

FR-5 — Provide general restaurant information (explicit) As a Customer, I should be able to ask general restaurant information questions and receive confirmed details, so that I know the address, phone, and cuisine.

  • Trigger/input: Customer asks a general information question.
  • Observable result: Confirmed details (address 8790 204 St #2, Langley Township, BC V1M 2Y5; phone 604-888-4270; cuisine Asian / Asian fusion) or a no-confirmed-information statement.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270 when unconfirmed.
  • Continuation: Customer may navigate to another surface.

FR-6 — Provide pickup/delivery information without guaranteeing delivery time (explicit) As a Customer, I should be able to ask pickup/delivery questions and receive approved information, so that I understand pickup and delivery options.

  • Trigger/input: Customer asks a pickup/delivery question.
  • Observable result: Approved pickup/delivery information; never a guaranteed delivery time.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270 when unconfirmed.
  • Continuation: Customer may ask another question.
Page 14 of 24

FR-7 — Collect catering/group-order inquiry details (explicit) As a Customer, I should be able to submit a catering or group-order inquiry with the required details, so that staff can follow up.

  • Trigger/input: Customer starts a catering/group-order inquiry.
  • Observable result: The assistant asks for name, phone or email, approximate number of people, preferred date, preferred time, and type of food/order; the inquiry is recorded for staff follow-up.
  • Access state: Anonymous.
  • Failure/recovery: If submission fails, retry or call 604-888-4270.
  • Continuation: Customer receives confirmation that the inquiry was recorded for staff follow-up.

FR-8 — Collect customer information only when useful (explicit) As a Customer, I should not be asked for personal information during normal menu questions, so that my privacy is respected.

  • Trigger/input: Customer asks a normal menu question.
  • Observable result: No unnecessary request for personal information.
  • Access state: Anonymous.
  • Failure/recovery: N/A.
  • Continuation: Customer continues asking questions.

FR-9 — Handle basic dietary questions conservatively (explicit) As a Customer with a dietary question, I should receive a conservative answer that does not assume allergen safety, so that I am not misled.

  • Trigger/input: Customer asks a dietary question.
  • Observable result: A conservative answer; no assumption about nuts, peanuts, gluten, dairy, eggs, shellfish, soy, or cross-contamination.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270 when unconfirmed.
  • Continuation: Customer may ask another question.
Page 15 of 24

FR-10 — Never declare allergy safety without explicit confirmation (explicit) As a Customer with an allergy, I should never be told a dish is "safe" unless the restaurant has explicitly confirmed it, so that I am protected from harm.

  • Trigger/input: Customer asks whether a dish is safe for an allergy.
  • Observable result: No "safe" claim unless the restaurant has explicitly confirmed it.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer may contact EMW directly.

FR-11 — Serious-allergy escalation message (explicit) As a Customer with a serious allergy, I should receive the exact escalation message directing me to contact EMW directly, so that the restaurant can confirm ingredients and preparation.

  • Trigger/input: Customer reports a serious allergy.
  • Observable result: The exact message: "Because food allergies and cross-contact can be serious, I don't want to guess. Please contact EMW directly at 604-888-4270 so the restaurant can confirm the ingredients and preparation process."
  • Access state: Anonymous.
  • Failure/recovery: N/A (message is the recovery).
  • Continuation: Customer contacts EMW directly.
Page 16 of 24

FR-12 — Handle complaints respectfully (explicit) As a Customer with a complaint, I should have my concern acknowledged without argument or blame, so that I feel heard.

  • Trigger/input: Customer submits a complaint.
  • Observable result: Acknowledgement of the concern; no argument; no blame of the restaurant or customer; request for relevant details; offer to pass the matter to staff; the inquiry is recorded for staff follow-up.
  • Access state: Anonymous.
  • Failure/recovery: If recording fails, retry or call 604-888-4270.
  • Continuation: Customer receives confirmation that the matter was passed to staff.

FR-13 — Escalate to staff when required (explicit) As a Customer, I should have my matter escalated to staff when it involves a serious allergy, a refund request, an order complaint, a missing order, an order change, a reservation confirmation, an unavailable menu item, information not in the knowledge base, or a question requiring staff confirmation, so that a human can resolve it.

  • Trigger/input: Any of the listed escalation conditions.
  • Observable result: The matter is escalated to staff and recorded for follow-up.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Staff follow up with the customer.
Page 17 of 24

FR-14 — Never claim an order was placed (explicit) As a Customer, I should never be told an order has been placed, so that I am not misled about order status.

  • Trigger/input: Any conversation about placing an order.
  • Observable result: No claim that an order has been placed.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.

FR-15 — Never claim a reservation was confirmed (explicit) As a Customer, I should never be told a reservation has been confirmed, so that I am not misled about reservation status.

  • Trigger/input: Any conversation about reservations.
  • Observable result: No claim that a reservation has been confirmed.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.

FR-16 — Never guarantee delivery time (explicit) As a Customer, I should never be given a guaranteed delivery time, so that I am not misled about delivery.

  • Trigger/input: Any conversation about delivery timing.
  • Observable result: No guaranteed delivery time.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.
Page 18 of 24

FR-17 — Never invent menu items, prices, or opening hours (explicit) As a Customer, I should never receive invented menu items, prices, or opening hours, so that I can trust the information.

  • Trigger/input: Any question about menu items, prices, or opening hours.
  • Observable result: Only approved information; otherwise a no-confirmed-information statement.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.

FR-18 — Never claim availability without confirmation (explicit) As a Customer, I should never be told an item is available unless the approved information confirms it, so that I am not misled.

  • Trigger/input: Any question about item availability.
  • Observable result: Availability claimed only when the approved information confirms it.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.

FR-19 — Use only the approved knowledge base (explicit) As a Customer, I should receive answers drawn only from the approved EMW knowledge base, so that I can trust the information.

  • Trigger/input: Any question.
  • Observable result: Answers drawn only from the approved knowledge base.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.
Page 19 of 24

FR-20 — Resolve conflicting public sources to approved information (explicit) As a Customer, I should receive the restaurant-approved information when public sources conflict, so that I am not given a guess.

  • Trigger/input: A question where public sources conflict.
  • Observable result: The restaurant-approved information is used; no guessing.
  • Access state: Anonymous.
  • Failure/recovery: Direct to 604-888-4270.
  • Continuation: Customer contacts EMW directly.

FR-21 — Unknown-information fallback message (explicit) As a Customer, I should receive the exact fallback message when information is unknown, so that I know how to get a confirmed answer.

  • Trigger/input: A question the assistant cannot answer from the approved knowledge base.
  • Observable result: The exact message: "I don't have confirmed information about that. Please contact EMW directly at 604-888-4270 and the staff can confirm it for you."
  • Access state: Anonymous.
  • Failure/recovery: N/A (message is the recovery).
  • Continuation: Customer contacts EMW directly.
Page 20 of 24

FR-22 — Friendly, short, professional communication style (explicit) As a Customer, I should receive friendly, short, professional, helpful, and natural responses, so that the conversation feels like a friendly counter person.

  • Trigger/input: Any conversation.
  • Observable result: Responses are friendly, short, professional, helpful, and natural; long paragraphs are avoided; "As an AI" is not repeatedly said.
  • Access state: Anonymous.
  • Failure/recovery: N/A.
  • Continuation: Customer continues the conversation.

FR-23 — Staff access is provisioned by invitation (required_inference) As a Restaurant Staff member, I should be provisioned (invited) before accessing recorded inquiries, so that only authorized staff can review customer matters.

  • Trigger/input: Staff provisioning by the restaurant.
  • Observable result: Provisioned staff can complete returning verification.
  • Access state: Protected.
  • Failure/recovery: Unprovisioned staff cannot access; contact EMW administrator.
  • Continuation: Staff complete returning verification.
Page 21 of 24

FR-24 — Staff returning verification (required_inference) As a Restaurant Staff member, I should complete returning verification before reviewing or following up on inquiries, so that recorded customer matters remain protected.

  • Trigger/input: Staff visits the Login surface.
  • Observable result: Verified session grants access to Inquiries.
  • Access state: Protected.
  • Failure/recovery: Invalid credentials — retry or contact EMW administrator.
  • Continuation: Staff proceed to Inquiries.

FR-25 — Review and follow up on recorded inquiries (required_inference) As a Restaurant Staff member, I should browse and follow up on recorded customer inquiries requiring staff confirmation, so that customers receive the human follow-up they were promised.

  • Trigger/input: Staff opens the Inquiries surface after verification.
  • Observable result: Recorded inquiries (catering/group-order leads and complaints) are listed with details for follow-up.
  • Access state: Protected.
  • Failure/recovery: Fetch failure — retry or re-verify.
  • Continuation: Staff follow up with the customer.
Page 22 of 24

FR-26 — Durable recording of customer inquiries (required_inference) As a Restaurant Staff member, I should have customer inquiry submissions recorded durably, so that no follow-up is lost.

  • Trigger/input: Customer submits a catering/group-order inquiry or complaint.
  • Observable result: The inquiry is recorded durably and available at the Inquiries surface.
  • Access state: System process (supporting the protected staff surface).
  • Failure/recovery: If recording fails, the customer is directed to 604-888-4270.
  • Continuation: Staff review the recorded inquiry.

4. User Personas

Page 23 of 24

Customer

Product context: Diners and prospective customers of E. M. W. – East Meets West in Langley, BC. They arrive anonymously, often from a phone, looking for quick answers about the menu, bubble tea, recommendations, general restaurant information, pickup/delivery, group orders, catering, or basic dietary questions.

Primary goal: Get quick, accurate answers about the approved EMW menu and general information without calling the restaurant — and, for anything unconfirmed or requiring staff confirmation, be directed to contact EMW directly at 604-888-4270.

Distinct accepted responsibilities:

  • Ask menu questions and receive answers drawn only from the approved knowledge base.
  • Ask what to order and answer a short preference follow-up (chicken, beef, seafood, vegetarian, noodles, soup, or a
Page 24 of 24
Landing design preview

Landing: Enter assistant conversation

Menu: Ask menu question

Menu: Receive unconfirmed fallback message

Recommendations: Request a recommendation

Recommendations: Answer preference follow-up

Recommendations: Request something spicy

Bubble Tea: Ask bubble tea question

Information: View confirmed business details

Information: Ask general information question

Pickup Delivery: Ask pickup/delivery question

Pickup Delivery: Read no-guarantee notice

Catering: Start group-order inquiry

Catering: Submit required inquiry details

Catering: Confirm inquiry recorded

Catering: Retry failed submission

Dietary: Ask dietary question

Dietary: Report serious allergy

Complaints: Submit complaint

Complaints: Provide complaint details

Complaints: Confirm matter passed to staff

Complaints: Retry failed submission

Landing design preview

Landing: Enter assistant conversation

Menu: Ask menu question

Menu: Receive unconfirmed fallback message

Recommendations: Request a recommendation

Recommendations: Answer preference follow-up

Recommendations: Request something spicy

Bubble Tea: Ask bubble tea question

Information: View confirmed business details

Information: Ask general information question

Pickup Delivery: Ask pickup/delivery question

Pickup Delivery: Read no-guarantee notice

Catering: Start group-order inquiry

Catering: Submit required inquiry details

Catering: Confirm inquiry recorded

Catering: Retry failed submission

Dietary: Ask dietary question

Dietary: Report serious allergy

Complaints: Submit complaint

Complaints: Provide complaint details

Complaints: Confirm matter passed to staff

Complaints: Retry failed submission