The Introduction scenario is the starting point for all conversations between the user and the AI Employee. It is always designated as Scenario 0.
Primary objective
The AI Employee will greet the user and identify the reason for their inquiry. It will also gather the minimum information needed to determine the next step by:
Identifying the intent type (e.g., Regular Table Booking, General Information Request, Guest Support)
Collecting critical parameters (e.g., reason for contact, desired date/time, specific service requests)
The AI Employee remains in this scenario until all required information is collected and confirmed. Once complete, the system transitions to the appropriate scenario based on the identified intent (per the Intent Type Map).
Formatting rules
1. Title
Always use: ## Scenario 0: “Introduction”
2.1 Body (Numbering)
Always use the format: ### **Step 0.X:** [instruction], where X is the step number.
Example: ### **Step 0.1:**, ### **Step 0.2:**, ### **Step 0.3:**
❗❗ IMPORTANT
Number steps sequentially, and they must match the scenario number (i.e., Scenario 0 → Steps 0.1, 0.2, 0.3, etc.).
2.2 Body (Instructions)
Each step describes one conversational action, such as:
Asking a question
Confirming information
Transitioning to another scenario
Example
Title
## **Scenario 0:** “Introduction”
Body
In this scenario, you must determine the **required fields**:
- **reason for their call**,
- **number of guests** if it's a reservation request,
- **date** if it's a reservation request,
- **time** if it's a reservation request,
You must remain in this scenario until you have gathered this information.
### **Step 0.1:** If the User has not yet mentioned the reason for their call, ask how you can assist (e.g., "Would you like to book a table, or is there anything else I can assist you with?"). Otherwise, start the relevant scenario based on the User's intent and **<IntentTypeMap>**
- Only after determining the **required fields**, start the relevant scenario based on the **<IntentTypeMap>**.