Help Center DoctorPrint Ticket History alternatives: printing and exporting Zendesk tickets after 21 October 2026
Zendesk's Print Ticket History app stops working on 21 October 2026, and Zendesk's own announcement says the Agent Workspace has no bulk printing. Here is what changes, what still works, three ways to print or export tickets today, and a checklist for the switch.
What Zendesk retires, and when
On 7 April 2026 Zendesk announced the discontinuation of seven Built-by-Zendesk apps: Print Ticket History, Project Management, Sidebar Search, Assignment Control, iFrame, Attachment Manager and Proactive Tickets. The announcement (support article 10479808424986) gives three dates: the apps were removed from the Marketplace on 7 April 2026, are unsupported since 30 June 2026, and will not function after 21 October 2026. The stated reason is that their capabilities are being incorporated into the Agent Workspace, together with low usage.
For Print Ticket History the replacement Zendesk points to is the browser's print command on the ticket page. On batches Zendesk is explicit, and worth quoting because it is the whole point of this page: "The Agent Workspace doesn't currently support bulk printing operations".
So on 22 October 2026 the situation is: one ticket can be printed from the browser; a list of tickets cannot be printed or exported as documents with anything Zendesk ships.
What the browser's print command does and does not print
- It prints the page as it is on screen: the conversation as far as it is loaded and expanded, collapsed messages collapsed, internal notes only if they are open, the sidebar apps and context panels included unless you hide them.
- It has no cover, no table of contents, no attachment list, no page break logic, no choice of paper size beyond the print dialog.
- It is one ticket at a time, by hand. There is no way to print a view, a search or a list of ids.
For a quick paper copy of a short ticket it is fine. For a legal request, an insurance file, a customer's records or an archive before deletion, it is not.
Three ways to print or export tickets in bulk today
1. The browser, ticket by ticket
Open each ticket, expand every message, hide the sidebar, print to PDF. Free and immediate; at 3 to 4 minutes per ticket a list of 50 tickets is an afternoon and the result has no index, no attachment list and no guarantee that every note was expanded.
2. The API with a script
The reliable recipe for developers: GET /api/v2/search/export.json?filter[type]=ticket&query=… to list the tickets with an exact count (the plain search endpoint stops at 1,000), GET /api/v2/tickets/{id}/comments.json per ticket, GET /api/v2/users/show_many.json to turn requester and author ids into names, then render HTML and convert to PDF with a headless browser. It works and it is what Ticket Print & PDF does internally; it also takes a few days to write and maintain, needs an API token or OAuth app that then has to be protected, and Zendesk is retiring API tokens for some integrations in April 2027, which pushes the script towards OAuth or an app.
3. Ticket Print & PDF (our app, disclosure: we sell it)
Ticket Print & PDF is our Zendesk Marketplace app, and this page exists because we built it for exactly this retirement. It runs inside Zendesk Support with the agent's session, no server, no token:
- Open a ticket and use the sidebar panel: Print / PDF, HTML or Word for that ticket, free.
- For batches, open the app from the navigation bar: paste ids or links, pick a view, or build a search (status, dates, tags, requester, group, brand, custom fields, text) with an exact count for the whole account.
- Click Read tickets: the app reads each ticket, its conversation and the names, with progress, and reports any ticket it could not read without stopping the batch.
- On Document, choose internal notes on or off, attachments, metrics, custom fields, a date range, order, cover, contents, page breaks, paper size, logo and footer, and the language of the labels; then Print / Save as PDF, HTML, Word, ZIP (one file per ticket with
index.csvandmanifest.json) or a CSV index.
Free prints one ticket at a time. Pro ($19 per account per month) reads up to 500 tickets per document from ids, views or searches and adds Word, ZIP, CSV, cover, contents and branding. Business ($49) reads up to 5,000 per run in files of 500, writes a SHA-256 hash of every ticket file into the index and the manifest for legal holds, shares presets with the account and keeps an evidence record of every document. Attachments are listed with links, not embedded, because a browser-side app cannot read them; the listing says so.
Comparison, dated September 2026
| Browser print | API script | Ticket Print & PDF | |
|---|---|---|---|
| Batches (view, search, ids) | — | ✓ (you write it) | ✓ up to 5,000 per run |
| Exact count of the tickets matched | — | ✓ with search/export | ✓ |
| Internal notes marked | Only if expanded | ✓ (you render it) | ✓, admins decide for agents |
| Attachments listed with links | — | ✓ (you render it) | ✓ |
| Cover, contents, page breaks, paper size | — | ✓ (you render it) | ✓ (Pro) |
| Word, HTML, ZIP, CSV | — | ✓ (you render it) | ✓ (Pro) |
| Hash manifest and evidence record | — | ✓ (you write it) | ✓ (Business) |
| Credentials | None | API token or OAuth app | None: the agent's session |
| Where the data goes | Stays in Zendesk | Wherever the script runs | Stays in Zendesk and the agent's browser |
| Cost | Time | Days of engineering | $0 / $19 / $49 per account per month |
Migration checklist
- Find out who used Print Ticket History. Admin Center → Apps and integrations → Zendesk Support apps shows the installation and its role restrictions; ask those teams what they print (single tickets? files for legal? archives before deletion?).
- Decide the internal-notes policy. Print Ticket History printed everything. If some teams must not hand internal notes to customers or third parties, use an app that lets admins switch notes off for agents.
- Decide what "the file" needs. A cover with the criteria and the date, a contents page, the attachment list, a hash for legal holds: write it down before choosing a tool.
- Test on a real case. Print one long ticket with notes and attachments, and one batch of 50 from a view; check the page breaks, the order and the names.
- Install before 21 October 2026 and remove the old app so nobody discovers the retirement on the day they need a file.
- Archives before deletion: if you delete old tickets under a retention rule, export them first; Data Custodian runs the retention side with a dry run and evidence, and Ticket Print & PDF produces the archive from the same search.
Frequently asked questions
When does the Print Ticket History app stop working? After 21 October 2026, per Zendesk's announcement. It has been unsupported since 30 June 2026 and off the Marketplace since 7 April 2026.
Can the Agent Workspace print tickets in bulk? No; Zendesk says so in the same announcement. One ticket at a time from the browser is the native option.
How do I print a Zendesk ticket with its internal notes? With the browser, expand every note first. With Ticket Print & PDF, tick "Include internal notes" (admins decide whether agents may) and the notes are printed on a coloured background with an "Internal note" badge.
How do I export hundreds of tickets as PDF? A script against the API, or Ticket Print & PDF from a view or a search: one document up to 500 tickets, or a ZIP with one file per ticket, up to 5,000 per run on Business.
Are attachments included in the PDF? Not by any browser-side app; they are listed with name, type, size and a link that works for signed-in agents. The files stay in Zendesk.
Is there a free plan? Yes: one ticket at a time, Print / PDF and HTML, from the sidebar or by id, without a time limit.
Related: Ticket Print & PDF · exporting tickets with comments to CSV or Excel · the Proactive Tickets retirement, same date · try the demo.
Support: support@helpcenterdoctor.app.