What a ticketing system is (for SaaS support)

Why SaaS teams use tickets

Customer email alone does not show ownership, SLA clocks, or history across agents. A ticketing system turns conversations into shared work items with status, assignee, priority, tags, and often macros. Tools differ (Zendesk, Jira Service Management, Intercom, and others), but the mental model is similar.

Core concepts

• Queue / view — the filtered list of tickets an agent works from (unassigned, my open, enterprise VIP, etc.).
• Status — new, open, pending, on-hold, solved, closed (names vary).
• Assignee and group — who owns the next action.
• Priority — urgency for the support team (SLAs, priority, and severity).
• Macros / automations — reusable replies and field updates that keep answers consistent.
• Internal notes — collaboration that the customer does not see.

Support example

A billing bug arrives in the “Payments” view as New. You take ownership, set Pending while waiting for a HAR, leave an internal note with the failing endpoint, then Solve when a workaround ships. Another agent can continue from the same ticket without re-asking the customer for context.

Common mistakes

• Working issues only in personal email or chat so nobody else can continue them.
• Leaving tickets Open forever with no next owner or next question.
• Using macros that sound personal but include outdated product facts.