Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-ticket-status

List your AssureSwarm support-ticket threads from your own Gmail and flag which are waiting on your reply: read-only against your mailbox, no Canvas writes.

The “where do my tickets stand” check. Because tickets live as email threads rather than Canvas items, this skill operates on your own Gmail: it searches your sent and inbox folders for messages to or from AssureSwarm support, parses each subject prefix for category and severity, and surfaces the threads awaiting your response first. It’s read-only against your mailbox: it never replies or modifies anything, and makes no Canvas writes. Use /coach-ticket-followup to respond.

When to use

Section titled “When to use”

To see the state of the support tickets you’ve opened: which are waiting on you, which are waiting on the vendor, and which are resolved. To reply to one, use /coach-ticket-followup; to open a new one, use /coach-ticket-open.

Inputs

Section titled “Inputs”
Flag Required Notes
--since <YYYY-MM-DD> No How far back to search. Default 90 days ago.
--include-resolved No Include resolved threads. Default false: they’re hidden unless asked.
--support-address <email> No Override the default support@assureswarm.com.

Example

Section titled “Example”

/coach-ticket-status searches your Gmail for threads to or from support@assureswarm.com in the last 90 days, classifies each as waiting on me, waiting on vendor, or resolved, and renders a table grouped with “waiting on me” first: subject, category, severity, last activity, and message count. For a thread where the vendor asked a question, it suggests /coach-ticket-followup --thread <id> to draft the reply.

Good to know

Section titled “Good to know”
  • Read-only. It never replies or changes anything; /coach-ticket-followup is how you respond.
  • It only sees your own Gmail. A ticket a teammate opened from their account won’t appear here.
  • “Waiting on me” means the latest message is from the vendor and unread, or it ends on a question.
  • Resolved threads are hidden unless you pass --include-resolved; a thread counts as resolved when it carries [resolved] or the coworkcanvas-support/resolved label.
Section titled “Related”