Zendesk Ticketing System: Triggers, Macros, SLAs, Routing

Zendesk's ticketing system turns every incoming email, chat, call or social message into a ticket, then moves it through fixed statuses with triggers, hourly automations, macros and views. The core rules engine is on every plan, including the cheapest. Zendesk's pricing page lists Support Team at $19 per agent per month billed annually, or $25 billed monthly, and Suite Professional at $115 billed annually, or $149 billed monthly.^[1] Billing is per agent, so every agent seat is paid; our Zendesk pricing guide covers the full bill. The verdict: small email-only teams get a complete rules engine on Support Team, but SLA policies, skills-based routing and multiple ticket forms all start on Suite Professional. Plan for that jump before you design workflows around them.

Where tickets come from on each plan

The channel list depends on the plan, and this is the first decision. Support Team is email ticketing with multiple support addresses, plus public social channels such as Facebook and X. It has no messaging or live chat, no help center and no voice. Suite Team adds messaging and live chat through the Web Widget, mobile SDKs and WhatsApp, telephony with voicemail, one help center in one language, and omnichannel routing. Suite Professional adds multiple ticket forms with conditional fields, which matters once different request types need different data. On other plans you get the basic default form only.

AI agents create tickets too. Every conversation handled only by an AI agent becomes a read-only ticket. SLAs, routing, macros, merging and most triggers ignore it until it escalates to a human. When Zendesk made these tickets generally available, it added a Support type is Agent condition to existing views, so they stay out of your queues. From 3 Nov 2026 they arrive with status New and no AI assignee. They also count toward data storage. How those AI conversations are billed is covered in our Zendesk AI playbook.

The life of a ticket, from New to archived

Tickets move through New, Open, Pending, On-hold (optional) and Solved, and then Closed. Some accounts also have In Progress, and Agent Workspace allows custom statuses. A ticket never returns to New. Agents cannot close tickets themselves. A standard automation closes them 4 days after Solved; you can change that window from one hour to 28 days, but you cannot disable or delete it.^[2] Separately, the system closes any solved ticket after 28 days, whatever else happens to it.

Closed is final. A customer reply to a closed ticket does not reopen it; Zendesk creates a follow-up ticket instead, and Explore reports that follow-up under the Web channel. Then comes archiving. Zendesk archives tickets 120 days after they close, sooner for accounts with extremely high volume.^[3] Archived tickets drop out of views and run no triggers or automations, yet stay reachable through search, user profiles, Explore and the API. Tickets with more than 10,000 events or records above 2 MB are never archived.

The hard limits are worth knowing before you import history. A comment holds at most 65,535 characters, a ticket at most 5,000 comments, and a subject 150 characters. Attachments top out at 50 MB on every plan, and that ceiling cannot be raised. Suspended tickets, usually suspected spam, are deleted after 14 days, and triggers do not fire on them until an agent recovers them.

Triggers, automations, macros and views

These four tools do different jobs. Triggers are event-based: they run on every ticket create or update and act at once, which makes them right for notifications, tagging and assignment. Automations are time-based. They run hourly over tickets that are not closed, so they suit reminders, escalations after a wait and the close rule above. Expect up to an hour of delay.

Automations carry limits that bite in larger accounts. Each one processes at most 1,000 tickets an hour, an account can keep at most 500 active, and a single ticket can be updated by automations no more than 100 times (the close automation is the exception). Each rule must stay under 65 KB. One trap is easy to miss: automations stop running on accounts where no one has signed in for 14 days. Another: custom date fields in rules and views are always evaluated in GMT, not your account time zone.

Macros are one-click responses that can also set fields, tags and status in the same click. Shared macros belong to the account; personal ones belong to the agent. Downgrading an agent deletes that agent's personal views and macros, while shared ones remain. AI-suggested macros belong to the Copilot add-on, which costs $50 per agent per month, paid yearly, on Professional and higher plans, bought for all agent seats.

Views are saved ticket lists filtered by conditions, the agent's working queue. Custom field columns sort by the underlying tags in alphabetical order, not by field titles. If you pull views through the API, execution is limited to 5 requests per minute per view per agent. Plan polling scripts around that. Messaging now feeds views directly: new messaging activity updates the Latest Update timestamp, and an indicator marks active conversations, on all accounts with no setup.

Routing: who gets which ticket

Support Team offers ticket routing through triggers and groups. Suite Team adds omnichannel routing in Agent Workspace, which assigns new and open email, messaging and call tickets by agent availability and capacity. You choose round robin or highest spare capacity. Voicemail tickets are not routed this way, and live chat alone cannot use it.

Suite Professional adds skills-based routing, routing by priority and custom queues. Skills come in up to 10 skill types with 30 skills each, so a ticket in Spanish about billing can wait for an agent tagged with both. Plans with custom queues also get predictive routing for messaging tickets, with no add-on. Custom agent statuses are capped at 5 on Suite Professional and 100 on Suite Enterprise, which also adds subqueues, up to 5.

The gap is real money. By our arithmetic, moving from Support Team to Suite Professional adds $96 per agent per month billed annually. For ten agents on annual billing that is $11,520 a year, so buy the higher plan for SLAs and skills, not for routing alone if round robin is enough. A middle step exists: Suite Team already brings omnichannel routing and the extra channels, so price it against your channel needs first.

SLA policies on Suite Professional

SLA policies are a Suite Professional feature. They are absent on both Team plans. A policy tracks up to six metrics: first reply, next reply, periodic update, requester wait, agent work and total resolution time. Each ticket gets one SLA, taken from the first matching policy from the top of the list, so order your policies from the most specific to the most general. Policies key off the system Priority field (Low, Normal, High, Urgent), so that field must be filled in.

Three behaviors catch teams out. SLAs do not apply to AI agent tickets. Breaches are not back-dated, so a policy created today will not flag yesterday's late replies. And most accounts created from 3 Mar 2025 start with a standard SLA that sets a one-hour first reply time on normal priority, which you should review on day one. Suite Enterprise adds group SLAs, also called OLAs, on top of the ticket SLA, plus business hours per priority.

Side conversations and light agents

Not every reply belongs on the customer thread. Side conversations let an agent pull in a vendor, a finance colleague or an engineer by email, Slack, Microsoft Teams or a child ticket, without exposing that exchange to the requester. An administrator must turn them on. They are included in Suite; Support plans need the Collaboration add-on. Note that when someone replies to a side conversation, the parent ticket's assignee gets no email unless you build a trigger for it. Replies to an email or Slack side conversation on a closed ticket create a follow-up ticket automatically.

Light agents are the cheap way to involve colleagues. They use no paid seat, and on non-Enterprise plans admins set which tickets they can view and whether they can open Explore. Suite Professional includes up to 100 light agents; Team plans buy them as an add-on. Everyone who answers customers still needs a full seat, including suspended agents.

The bottom line

Zendesk's ticketing core is the same rules engine on every plan: triggers for instant reactions, hourly automations for time-based work, macros for repeated replies and views for queues. What changes with the plan is everything around it. Support Team suits a small email-only desk. Suite Team adds channels and omnichannel routing. Suite Professional is the first plan with SLA policies, skills routing and multiple forms, so decide early whether you need them and size the bill by agent before you build.