Ticket craft

A ticket is not an email

New support VAs treat tickets like emails — read, reply, done. Professionals treat a ticket as a record inside a machine: it has a requester, a status, a priority, tags, an SLA clock counting down, internal notes the customer never sees, and a history that the next agent will rely on. Learn the machine and you can work any helpdesk. This lesson uses Zendesk and Gorgias because they dominate the hiring market — Zendesk for SaaS and services, Gorgias for Shopify stores.

The anatomy, tool by tool

In Zendesk: every ticket has a status you must manage — Open (ball's in your court), Pending (waiting on the customer), Solved (done, pending auto-close). Views are saved filters that build your work queue; triggers automate actions; macros are canned replies with placeholders. The SLA clock starts the moment the ticket lands — first-response time is the metric most clients watch first.

In Gorgias: same skeleton, but wired into Shopify — the customer's orders, tracking status, and refund buttons live in the sidebar next to the conversation. You can check "where's my order" and answer it without leaving the ticket. That integration is why Shopify brands hire Gorgias-skilled VAs specifically.

Macros without the robot voice

Macros exist because 60% of tickets are variations of ten questions. Using them isn't lazy — sounding like them is. The pro pattern: macro skeleton, personalized top and bottom. The opening line responds to what this specific customer said; the middle carries the accurate policy/process language; the closing line matches their situation. Two rules that never bend: read the whole ticket before firing a macro (the #1 rookie disaster is answering a question the customer didn't ask), and never let a macro promise something you haven't verified in their actual order.

What a good reply looks like

Break down why this works: it validates the frustration without groveling, shows the agent actually checked (Memphis hub — a specific fact), solves the real problem (the birthday, not the tracking number), and closes with a commitment that has a deadline. Notice what's absent: no "we apologize for any inconvenience," no policy recital, no blaming the carrier and stopping there.

Tone matching and the CSAT drivers

Mirror the customer's register: brief and businesslike gets brief and businesslike; warm and chatty gets warmth back; furious gets calm, specific, and generous — never matching heat with heat, never meeting anger with a wall of cheerfulness. Use their name once, naturally.

What actually moves CSAT scores, in order: feeling heard (your first sentence proves you read their message), resolution on first touch (solve it completely instead of volleying), and speed (fast first response buys patience for everything after). Most beginners obsess over speed and neglect the first two — which is exactly backwards, because a fast reply that misreads the problem generates an angrier second ticket.

Do this now

Rewrite these three real-world bad replies in your own doc: (1) "We apologize for any inconvenience. Please allow 5–10 business days. Is there anything else I can help you with?" — sent to a customer whose package is three weeks late. (2) "As per our policy, returns require original packaging." — sent to a customer who received a cracked vase. (3) "Your issue has been forwarded to the relevant team." — sent to someone asking a simple sizing question. For each: write the version you'd send, using the validate–verify–solve–commit structure from the Jennifer reply. Save all three as your "reply portfolio" page — hiring managers for support roles ask for writing samples, and this is that sample. 20 minutes.