The support queue says “in progress.” The customer says nobody has called. Before buying another dashboard, check whether the ticket has an owner, a usable opening date and a current status.
Copilot in Excel can help turn an authorised ticket export into a reviewable exception list. The useful output is not a confident paragraph about service quality. It is a worksheet where a supervisor can trace each concern back to a ticket. Here is a bounded workflow for a Malaysian SME’s weekly support meeting.
1. Confirm access before using real tickets
Use a company-approved work account and a current Excel version. Microsoft’s documentation supports edit, chat and plan modes on Windows, Mac and the web. Open Copilot using the icon in Excel’s lower-right corner; check the selected mode before submitting anything. Editing can change the workbook directly. [1]
Licensing is not simply “everyone needs the same add-on.” Microsoft’s current Excel FAQ lists commercial Copilot subscriptions and Copilot Chat-eligible business or enterprise subscriptions among eligible routes. It distinguishes standard access, labelled M365 Copilot (Basic), from add-on priority access, labelled M365 Copilot (Premium). Availability also depends on tenant configuration. Ask IT to confirm your assigned access and permitted features rather than purchasing from an old tutorial. [2]
The operator needs authorised access to the export and permission to edit the analysis copy. This walkthrough does not require granting Global Administrator rights, installing a connector or allowing Copilot to search the whole organisation. Remove passwords, tokens, personal identifiers and unnecessary customer narrative before testing.
2. Make a clean, dated working copy
Export a snapshot from the ticketing system using its approved process. Preserve the original separately. Put the working copy in the company’s approved SharePoint or OneDrive location and save it as .xlsx. Record the export time and reporting timezone.
For this exercise, use one row per ticket with these headers: TicketID, OpenedDate, Status, Owner and Service. Keep dates as real Excel dates, not ambiguous text. Define the status values with your support lead; do not let AI guess whether “waiting” means closed.
Select the dataset, choose Home > Format as Table, confirm the range and headers, and name the table Tickets. Microsoft documents this table-creation process. [5] Add a separate cell named ReviewDate containing the fixed review date, rather than a moving date that changes tomorrow’s report. Set Calculation Options to Automatic, as required for Copilot editing. [2]
3. Inspect first; edit second
Start in Chat only mode, which keeps responses out of the worksheet. Ask:
Review the Tickets table only. Identify duplicate TicketID values, blank owners, missing or invalid OpenedDate values, and unexpected Status values. Show the affected TicketIDs. Do not change the workbook or infer missing values.
Check the returned rows yourself. A blank owner may indicate an unassigned ticket, but it can also reflect an incomplete export. Correct confirmed source issues through the normal ticketing process; do not quietly repair the report and leave the operational system wrong.
Microsoft recommends naming the columns or ranges in prompts. [3] If the result is unclear, ask for the specific rows and explanation, not a longer summary.
4. Build one transparent exception column
Once dates and statuses are validated, switch to editing and request:
In Tickets, add AgeDays. For Status exactly Closed, leave it blank. Otherwise calculate whole calendar days between OpenedDate and ReviewDate. Flag future opening dates for review; do not replace source values. Explain the formula before I rely on the result.
Copilot can generate formula columns and explain calculations. [4] Inspect the actual formula, not just its explanation. For valid, date-only records, a candidate is =IF([@Status]="Closed","",ReviewDate-[@OpenedDate]). This assumes the closed label is exactly Closed and the dates have already passed validation.
Hypothetical check: With ReviewDate set to 20 October 2026, an open ticket dated 17 October should show three calendar days; a ticket opened on the review date should show zero; a closed ticket should be blank. These are test cases, not AXO customer records. Calendar age is not SLA elapsed time: business hours, paused states and contractual rules require separate logic.
5. Turn the result into an accountable conversation
Ask for a review sheet listing non-closed tickets with blank owners, followed by the oldest non-closed tickets, retaining TicketID and source fields. Review it against the export before sharing. Do not ask Copilot to infer severity from customer names or automatically contact customers.
Assign follow-up in the ticketing system. The spreadsheet is a snapshot, not a replacement queue. A disputed age or ownership issue should be resolved against the authoritative record.
Share the approved review with named colleagues, choosing Can view for readers and Can edit only for maintainers. Microsoft’s sharing controls support those choices. [6] Check existing access too; a narrower new link does not remove older permissions.
Keep the prompt, review date and validated workbook together. Measure whether unassigned work gets an owner—not how polished the AI summary sounds. For help scoping a practical Microsoft 365 workflow, contact AXO Technologies.
