Zendesk AI Ticket Summary Limits: Cooldowns, Meters, and Closed Tickets (2026)

Zendesk's built-in AI ticket summaries are genuinely useful, and for many teams they are enough. But the feature ships with a set of documented constraints that surprise people, usually at the worst moment: mid-shift, when the refresh button goes gray. This page collects every limitation we could verify in Zendesk's own documentation, explains why each one exists, and describes what it means in day-to-day support work.

The limits at a glance

1. Summaries are manually triggered, not live

Per Zendesk's help center article on summarizing ticket comments using generative AI, an agent has to click to generate a summary, and an existing summary does not update on its own when new comments arrive.

This is a sensible engineering choice. Regenerating a summary on every incoming comment would multiply model calls across an entire account, most of which nobody would read. But it puts the burden on the agent to remember that a summary reflects the ticket as it was at click time. On a fast-moving ticket, the summary at the top of your sidebar may already be a reply or two behind the actual conversation. The practical habit: treat the summary as a starting snapshot, and refresh before you rely on it for a handoff.

2. Refresh is limited to once every five minutes

The same documentation notes that a summary can be refreshed at most once every five minutes. If a customer sends three messages in quick succession, you cannot re-summarize after each one; you wait out the cooldown.

Again, the reason is understandable: a cooldown is a straightforward way to cap compute cost on a feature bundled into plan pricing. The day-to-day effect shows up on exactly the tickets where summaries help most, the long and fast-moving ones. During an active back-and-forth, the five-minute window means the summary and the conversation can stay perpetually out of sync, so most agents end up reading the new comments directly anyway.

3. Summaries draw from a monthly usage allowance

Summaries consume a monthly usage allowance. When the account's allowance runs out, the refresh button is dimmed for the rest of the cycle unless the account has the Copilot add-on, which is priced at $50 per agent per month. This behavior is covered in Zendesk's docs and was reported in detail by the independent Zendesk-ecosystem blog Internal Note.

From a packaging standpoint this makes sense: generative AI has a real per-use cost, and the allowance lets Zendesk include the feature in base plans without unbounded expense. The day-to-day problem is predictability. Usage is pooled and invisible to most agents, so the meter tends to run out near the end of a month, on a busy day, without warning. Teams that come to rely on summaries either ration clicks or budget for the add-on. If you are weighing that decision, our companion post on Zendesk Copilot pricing breaks down what the add-on costs at different team sizes.

4. No summaries for closed tickets, ever

This is the limitation that catches teams off guard. Zendesk stores summaries in ticket custom fields, and custom fields become read-only when a ticket closes. Two consequences follow, both documented in the configuration article and the summarization article linked above:

• Summaries are not stored for closed tickets, and are not accessible via the API or views after the fact.
• A summary that was never generated before a ticket closed cannot be generated afterward. The window is simply gone.

The cause is architectural rather than arbitrary: closed tickets are immutable in Zendesk by design, and the summary storage mechanism inherits that immutability. But the effect is that your summary history evaporates exactly when it becomes historical. QA reviews, escalation post-mortems, and "what did we tell this customer last time" lookups all happen on closed tickets, and none of them can lean on native summaries.

5. Summaries cover the conversation only

Native summaries are built from the ticket conversation: public comments by default, plus internal notes if an admin enables that option. They do not draw on help center articles or any other knowledge source.

This is a reasonable scope for a summarization feature; it is summarizing the ticket, not answering it. It just matters that you know the boundary. The summary will tell you what the customer said and what agents replied. It will not tell you whether the answer given matches your documentation, and it cannot pull in context the conversation never contained.

6. It requires a Professional plan or above

AI ticket summaries are available on Suite Professional and Support Professional plans and above. Team plans do not include the feature at all. If you are on a Team plan, the limitations above are academic; the button simply is not there, and the upgrade path is a plan change, not a toggle.

When the native summaries are enough

Honestly, for plenty of teams, they are. If your ticket volume is moderate, your tickets are short, and you mostly want a quick refresher when picking up an unfamiliar ticket, the built-in summaries do the job at no extra cost on a qualifying plan. The five-minute cooldown rarely bites on slow-moving tickets, and a modest team may never touch the monthly ceiling. If your workflow does not involve revisiting closed tickets, the storage limitation will not affect you either. We compared native summaries against other approaches in our guide to summarizing long Zendesk tickets, and the native option holds up well for light use.

When you'll want more

The limits above compound for high-volume teams: heavy use hits the meter, fast tickets hit the cooldown, and QA work hits the closed-ticket wall. That combination is what ZenBriefr was built for. It is a Zendesk sidebar app that handles summarization differently on each of these axes:

• No cooldown, no meter. Summaries regenerate on demand, as often as you need, with no monthly allowance to run out.
• Four summary modes. Quick, handoff, resolution, and an auto-detect mode that picks the right format for the ticket's stage.
• Closed tickets work. Because summaries are not tied to ticket custom fields, you can summarize a ticket that closed last month.
• Auto-translation. Summaries can be translated into each agent's own language, with 48 languages supported.
• Attachment OCR. Text inside images and PDFs is extracted and fed into the summary, so a screenshot of an error message actually informs the output.
• Flat pricing. $149 per month for unlimited agents, on any Zendesk plan, including Team. There is a 14-day free trial with no credit card required.

To be clear about what this is and is not: these are workflow and packaging differences, not a claim that any one tool summarizes more accurately than another. If the native limits never bite you, you do not need a second tool.

FAQ

Do Zendesk AI summaries update automatically when a customer replies?

No. Summaries are generated when an agent clicks the button and do not refresh on their own as new comments arrive.

How often can I refresh a Zendesk AI summary?

Once every five minutes, per Zendesk's documentation.

Can I get an AI summary of a closed Zendesk ticket?

Not with the native feature. Summaries are stored in custom fields that become read-only at close, so existing summaries are not retained or accessible, and new ones cannot be generated on closed tickets. Third-party sidebar apps such as ZenBriefr can summarize closed tickets because they do not store summaries in ticket fields.

What happens when the monthly summary allowance runs out?

The refresh button is dimmed until the next cycle, unless the account has the Copilot add-on ($50 per agent per month), which removes the constraint.

Which Zendesk plans include AI ticket summaries?

Suite Professional and Support Professional and above. Team plans do not include the feature.

Do native summaries use help center content?

No. They summarize the ticket conversation only: public comments, plus internal notes if an admin has enabled that option.

Sources

• Zendesk: Summarizing ticket comments using generative AI
• Zendesk: Turning on and configuring AI-generated ticket summaries
• Internal Note: Updates to Agent Copilot summaries in Zendesk (independent Zendesk-ecosystem blog)