The Scenario
Your support manager sends you a message at 9 AM: "Can you check which of the open tickets in the tracker are actually overdue? The director wants a status call at 11."
You open the shared Google Sheet. Column A has 90 OneDesk ticket IDs. Column E is blank. That's the column that's supposed to say "Overdue", "Due Today", or "On Track".
The last time someone did this check, they opened each ticket in OneDesk, noted the due date, compared it to the calendar, and filled in the status column. For 90 tickets, that took most of a morning. The status call ended up using numbers from two weeks prior because nobody had time to do the live check before it started.
The bad version:
- Open OneDesk and navigate to the first ticket
- Note the due date, compare to today's date, decide on the status, switch back to the sheet, type it in
- Repeat 89 times, keeping track of where you are so you don't skip rows or double-enter
Two hours of context-switching to produce a column that should exist as live data in the first place. And if any ticket's due date changed since the last time someone looked, you won't know unless you catch it in the lookup.
The status call is in two hours. You don't have a morning to spend on this.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the ticket IDs in column A, looks up each one's due date and status in OneDesk, and writes the classification back into column E.
For each OneDesk ticket ID in column A, fetch its due date and current status. Write "Overdue" into column E if the due date is before today, "Due Today" if it matches today, and "On Track" if it is in the future. Leave column E blank for any ticket with no due date set.
Ninety lookups. One prompt. The status call has current numbers.
What You Get
- Column E populated for all 90 rows with "Overdue", "Due Today", or "On Track"
- Tickets with no due date left blank rather than miscategorized
- Results reflecting live OneDesk data pulled at the moment you run the prompt
What If the Data Is Not Quite Ready
You want the number of days overdue, not just a label
The director wants to see severity — not just which tickets are overdue but how far past due each one is.
For each ticket ID in column A, fetch the due date from OneDesk. Write the number of days overdue into column E — use a negative number for days remaining and a positive number for days past due. If no due date is set, write "no due date".
Some tickets may have been closed in OneDesk already
A handful of the IDs in the tracker might have been resolved and closed. Closed tickets should be labeled differently.
For each ticket ID in column A, fetch the due date and status from OneDesk. If the ticket status is Closed or Resolved, write "Closed" in column E regardless of due date. Otherwise, write "Overdue", "Due Today", or "On Track" based on the due date vs. today. Flag any ticket where the status lookup fails.
You also need the actual due date in the sheet for the director's review
The director wants to see the raw due date alongside the classification so they can verify specific cases.
For each ticket ID in column A, fetch the due date and current status from OneDesk. Write the raw due date into column D. Write the classification into column E: "Overdue", "Due Today", "On Track", or "Closed" if the status is resolved. Flag lookup failures in column F.
Full pre-call audit: days calculation, closure check, due date populated, summary counts
For each ticket ID in column A, fetch the due date and status from OneDesk. Write the raw due date into column D. Write days remaining or overdue (negative for remaining, positive for past due) into column E. Write the classification into column F: "Closed" if resolved, "Overdue" if past due, "Due Today", "On Track", or "No Due Date". After all rows, add a note at the top of the sheet showing counts for each classification.
The summary counts land at the top of the sheet so you can read the numbers into the status call without doing any mental math.
Try It
Get the 7-day free trial of SheetXAI and open the open-ticket tracker before your next SLA or status call — ask it to run the live due-date check and classify every row in one pass. Also worth reading: how to fetch ticket detail fields into a reporting sheet, and the hub overview of all four methods for connecting OneDesk to Google Sheets.