Skip to content

Commit 733b834

Browse files
Avijit-MicrosoftAvijit-Microsoft
authored
Merge pull request #200 from microsoft/tech-connect-sql
chore: updated sample questions and tag
2 parents 4e588ed + f5aadd4 commit 733b834

File tree

5 files changed

+63
-45
lines changed

5 files changed

+63
-45
lines changed

‎infra/main.bicep‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ param embeddingModel string = 'text-embedding-ada-002'
8686
@description('Capacity of the Embedding Model deployment')
8787
param embeddingDeploymentCapacity int = 80
8888

89-
param imageTag string = isWorkshop ? 'latest_workshop_convo_id' : 'latest_v2'
89+
param imageTag string = isWorkshop ? 'latest_workshop' : 'latest_v2'
9090

9191
@description('Deploy the application components (Cosmos DB, API, Frontend). Set to true to deploy the app.')
9292
param deployApp bool = false

‎infra/main.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
"_generator": {
66
"name": "bicep",
77
"version": "0.40.2.10011",
8-
"templateHash": "15275092260487391319"
8+
"templateHash": "15246189512269241745"
99
}
1010
},
1111
"parameters": {
@@ -149,7 +149,7 @@
149149
},
150150
"imageTag": {
151151
"type": "string",
152-
"defaultValue": "[if(parameters('isWorkshop'), 'latest_workshop_convo_id', 'latest_v2')]"
152+
"defaultValue": "[if(parameters('isWorkshop'), 'latest_workshop', 'latest_v2')]"
153153
},
154154
"deployApp": {
155155
"type": "bool",

‎workshop/docs/01-deploy/04-run-scenario.md‎

Lines changed: 51 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -69,44 +69,62 @@ python scripts/08_test_agent.py
6969

7070
```
7171
============================================================
72-
Orchestrator Agent Chat
72+
AI Agent Chat (Fabric SQL + Native Search)
7373
============================================================
74+
Chat Agent: dauypdob4c4d2k-ChatAgent
75+
SQL Mode: Fabric Lakehouse
76+
Lakehouse: <workshop_lakehouse_1>
7477
Type 'quit' to exit, 'help' for sample questions
7578
7679
------------------------------------------------------------
7780
78-
You: How many outages occurred last month?
79-
80-
Agent: Based on the database, there were 16 network outages recorded
81-
in January 2024.
82-
83-
You: What are the policies for notifying customers of outages?
84-
85-
Agent: According to our Customer Service Policies document:
86-
87-
- Customers must be notified within 15 minutes of confirmed outage
88-
- Use SMS, email, and app notifications for affected customers
89-
- Provide estimated restoration time when available
90-
- Send updates every 30 minutes during extended outages
91-
92-
[Source: customer_service_policies.pdf]
93-
94-
You: Which outages exceeded the maximum duration defined in our policy?
95-
96-
Agent: Let me check the outage data against our policy thresholds...
97-
98-
Based on a 4-hour (240 minute) maximum duration policy, these
99-
outages exceeded the threshold:
100-
101-
| Outage ID | Duration (min) | Impact Level |
102-
|-----------|----------------|--------------|
103-
| OUT011 | 472 | Medium |
104-
| OUT004 | 446 | Low |
105-
| OUT007 | 445 | Low |
106-
| OUT005 | 417 | Medium |
107-
| OUT003 | 411 | Low |
108-
109-
5 outages exceeded the policy maximum duration.
81+
You: How many tickets have priority = 'High'?
82+
83+
Agent: There are **4 tickets** with priority **High**.
84+
85+
You: What is the average score from inspections?
86+
87+
Agent: The average score from inspections is **77**.
88+
89+
You: What are the requirements for handling customer tickets?
90+
91+
Agent: Here are the requirements for handling customer tickets:
92+
93+
1. **Ticket Handling Procedures**:
94+
- All customer tickets must be acknowledged within **1 hour**.
95+
- Closed tickets should provide feedback to clients.
96+
97+
2. **Priority Definitions**:
98+
- High priority tickets must be resolved within **4 hours**.
99+
- Medium priority tickets should be resolved within **24 hours**.
100+
- Low priority tickets should not exceed **72 hours** for resolution.
101+
102+
3. **Compliance and Service Level Agreements (SLAs)**:
103+
- Define minimum service quality levels.
104+
- For major outages, resolutions must be completed within **4 hours**.
105+
106+
4. **Documentation Requirements**:
107+
- All outages and tickets must be documented, including resolution times and customer impacts.
108+
109+
5. **Response Time Expectations**:
110+
- Representatives must respond to outage inquiries within **1 hour** during business hours and within **3 hours** outside of business hours.
111+
112+
6. **Ticket Escalation Process**:
113+
- All outages and tickets must be documented, including resolution times and customer impacts.
114+
115+
7. **Customer Feedback Mechanism**:
116+
- Gather customer feedback through follow-up surveys sent within one week of ticket closure.
117+
118+
These procedures ensure timely communication, accountability, and continuous improvement in customer service.
119+
120+
You: Are we meeting our resolution targets for high priority tickets according to our Ticket Management Policy?
121+
122+
Agent: According to the Ticket Management Policy, high priority tickets must be resolved within 4 hours. Here’s the current status regarding high priority tickets:
123+
124+
- **Total High Priority Tickets:** 4
125+
- **High Priority Tickets Resolved Within Target (4 hours):** 1
126+
127+
This indicates that we are currently not meeting our resolution target for high priority tickets, as only 1 out of 4 tickets were resolved within the specified timeframe.
110128
111129
You: quit
112130
```

‎workshop/docs/02-customize/index.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,8 @@ Simply provide two inputs:
4141

4242
**Sample Questions:**
4343

44-
- "Which outages exceeded our maximum duration policy?"
45-
- "What are the escalation procedures for high-impact outages?"
44+
- "Do any inspections violate quality control standards in our Inspection Procedures?"
45+
- "Are there any tickets that require follow-up assessments based on our Inspection Procedures?"
4646

4747
=== "Retail"
4848

‎workshop/docs/deployment-guide.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -118,10 +118,10 @@ python scripts/08_test_agent.py
118118

119119
**Sample questions to try:**
120120

121-
- "How many outages occurred last month?"
122-
- "What's the average resolution time?"
123-
- "What are the policies for notifying customers of outages?"
124-
- "Which outages exceeded the maximum duration defined in our policy?"
121+
- "How many tickets have priority = 'High'?"
122+
- "What is the average score from inspections?"
123+
- "What are the requirements for handling customer tickets?"
124+
- "Are we meeting our resolution targets for high priority tickets according to our Ticket Management Policy?"
125125

126126
### 7. Test the Fabric Data Agent
127127

@@ -139,9 +139,9 @@ python scripts/08_test_agent.py
139139
140140
**Sample questions to try:**
141141
142-
- "How many outages occurred last month?"
143-
- "What is the average duration of outages?"
144-
- "What is the average resolution time for tickets?"
142+
- "How many tickets have priority = 'High'?"
143+
- "What is the average score from inspections?"
144+
- Show tickets grouped by status.
145145
146146
### 8. Deploy and launch the application
147147

0 commit comments

Comments
 (0)