Question,Expected response,Testing method
"Show me all my open requests","The agent resolves ""my"" to the current user's display name (System.User.DisplayName) and queries the _RequestTracker Dataverse table for requests where the Requestor or Assigned To field matches the user's name AND the Status is not Completed/Closed. Results are displayed in the formatted search result template with emoji-coded status and priority (e.g., 🟨 In Progress, 🟠 High), along with title, assignee, due date, and description for each matching request.","General quality"
"How many critical requests are open right now?","The agent queries the _RequestTracker Dataverse table for requests where Priority = Critical AND Status ≠ Completed. Returns a count and summary list of critical open requests with key details: title, status, assignee, and due date. Uses the emoji format (🔴 Critical) and provides an accurate count grounded in the actual data.","General quality"
"Show me all open high priority tasks","The agent queries the _RequestTracker table for requests where Status ≠ Completed AND Priority = High. Returns a formatted list of matching requests using the standard emoji template (🟠 High priority, status indicators). Each result includes title, status, priority, requestor, assigned to, due date, and brief description.","General quality"
"I need to submit a new request for laptop replacement","The agent routes to the _New Request Item topic and presents an adaptive card form for creating a new request. The form should be pre-populated with context extracted from the user's message: Title should reference 'laptop replacement', and the Description should capture the user's need. The agent should show fields for Title, Description, Priority, Status, Assigned To, and Due Date.","General quality"
"Mark the laptop replacement request as completed","The agent routes to the _Update Existing Request topic. It searches for requests matching 'laptop replacement', presents matching results, asks the user to select which one to update, then shows a pre-populated adaptive card with current field values so the user can change the Status to Completed. After submission, confirms the update with a summary of what changed.","General quality"
"Give me a breakdown of requests by status","The agent queries the _RequestTracker table and provides a summary grouped by status categories: New, In Progress, Blocked, and Completed. For each status, it should show a count and optionally list titles. Uses appropriate emoji mappings: 🟦 New, 🟨 In Progress, 🟥 Blocked, 🟩 Completed.","Keyword match"
"I want to add something to the tracker","The agent recognizes this as an ambiguous intent — 'add something' could mean creating a new request OR updating an existing one OR populating sample data. Per its routing rules ('When in doubt, ask a clarifying question before routing'), the agent should ask the user to clarify: Do they want to create a new request, update an existing request, or load sample data?","General quality"
"Show me all blocked requests assigned to the IT team and tell me which ones are overdue","The agent handles two sub-tasks in one response: (1) Queries the _RequestTracker table for requests where Status = Blocked AND Assigned To contains 'IT' or similar team reference, and (2) Compares each result's Due Date against today's date (using the Today() function) to identify which ones are overdue. Returns the full list with emoji formatting (🟥 Blocked) and flags overdue items separately or highlights them.","General quality"
"yo what's on my plate right now?","The agent interprets this casual phrasing as 'show me requests assigned to me that are currently active.' It resolves 'my' to the current user's display name (System.User.DisplayName), queries the _RequestTracker table for requests where Assigned To matches the user AND Status is New or In Progress, and returns results in the standard emoji-formatted template.","Compare meaning"
"Delete all completed requests from last month to free up space","The agent should decline this request. The Request Tracker Agent can create, search, and update requests, but it does NOT have a delete capability. Its instructions define four capabilities: Search & Query, Summarize & Report, Create a Request, and Update a Request. Deletion is not among them. The agent should explain that it cannot delete requests and suggest the user contact an administrator or manage deletions directly in the SharePoint/Dataverse interface.","General quality"