TicketScope drafts client-facing status update emails in one click

The task that takes longer than it should at every MSP: writing a professional status update email to a client. You know what you want to say — "we're working on it," "we need a response from you," "we fixed it." Getting that into a client-appropriate email takes three minutes you don't have when you're juggling ten tickets.

TicketScope now has three status update buttons that do it in three seconds.

How it works

Three buttons appear in the TicketScope sidebar when you're on a ticket:

In Progress — Drafts a "we're working on it" email with the right level of detail: what we know, what we're doing, expected next update timeframe. Doesn't commit to a resolution time you might miss.

Waiting on Client — Drafts a "the ball is in your court" email with a clear ask: what we need, why we need it, and a soft deadline. Professional but direct.

Resolved — Drafts a resolution summary: what the problem was, what we did, what to do if it recurs. The thing you should send but usually don't because the ticket is closed and you've already moved on.

Each draft includes a subject line. Copy the subject. Copy the body. Paste both into CW's email field. Done.

What Haiku knows when drafting

The AI reads the ticket before drafting:

• Ticket title and board (Service, Project, Help Desk)
• Current status and priority
• Notes thread — what's been tried, what's been found
• Client company name
• Any custom context you add in the sidebar before clicking

The "Waiting on Client" email is the most useful of the three. The naive version just says "please provide X." The TicketScope version includes context from the notes — "we've confirmed the issue is in your SSL configuration, and we need read access to your certificate management console to proceed" — which reduces back-and-forth because the client understands what you're asking for and why.

The writing constraints

Client-facing status emails have a consistent set of rules:

• No jargon (or define it if you use it)
• Never say "as per our previous email" — that's passive-aggressive
• Never promise a resolution time you're not certain about
• Sound like a person, not a legal disclaimer
• Short — most clients read on mobile

The Haiku prompt enforces all of these. The output is reviewable in 10 seconds and rarely needs more than a quick personalization touch.

Where this fits

TicketScope already drafts time entries (what did I bill for?), resolution summaries (KB article), and AI ticket summaries (what's going on in this ticket?). Client status updates are the communication layer — the thing that happens between those steps, while work is in flight.

Together, they cover the full lifecycle of a ticket from first note to closed and documented. The only thing left is actually doing the work.