← Back to Blog
Zendesk's Attachment Deletion Schedules Now Reach WhatsApp, Messenger and Chat. Check Your Rules.
·5 min read
On 6 November 2026, Zendesk widened its attachment deletion schedules to cover messaging and Chat tickets. If an account already had a schedule running, that rule now deletes files on channels it was never written for. The deletions can't be undone. Zendesk published how to opt out, but the date it gave for reviewing your rules has already passed.
What changed
Zendesk's announcement says: "Attachment deletion schedules now delete attachments on messaging and Chat tickets. This includes files shared through the Web Widget, as well as those handled by AI Agents, the Zendesk mobile SDKs, social messaging channels such as WhatsApp and Facebook Messenger, and live chat in the Agent Workspace."
Until now these channels were left alone: "Previously, attachment deletion schedules did not support messaging or Chat tickets."
Zendesk's reason is a good one: "Customers often share sensitive documents, such as IDs, receipts, and medical certificates, during messaging and Chat conversations." One schedule across every channel means less personal data kept for no reason.
Availability, in Zendesk's words: "This feature is available to all customers, with extra schedules and filters for customers using the Advanced Data Privacy and Protection add-on." The basic schedule is available to everyone. The extra schedules and filters come with that add-on.
The part to read twice
Under "What do I need to do?", Zendesk says: "If you have an active attachment deletion schedule, you don't need to do anything. After November 6th, your active schedules will also delete eligible attachments on messaging and Chat tickets."
Further down, in bold: "Important: Deleted attachments can't be restored."
Taken together, that means a rule written and tested against email tickets now also applies to WhatsApp, Messenger, chat and AI agent conversations. The conditions didn't change; the set of tickets they match did.
Zendesk did tell admins how to avoid surprises, in the same section: "Before then, review your conditions and make sure you want them to apply to these tickets. If you don't, update the conditions to exclude them, for example by group or tag." It also warns: "If you also use ticket deletion schedules, check them too. Removing an attachment counts as a ticket update which could defer deletion."
So the warning exists. The issue is where it sits: under a heading that opens with "you don't need to do anything", with a deadline of "Before then", meaning before 6 November. Any admin reading it today is already past that date.
What the schedules don't do
Zendesk lists the limits, and several of them are reassuring:
- Only old, closed tickets. "They delete attachments only on archived tickets (tickets closed for more than 120 days) that meet your conditions." Nothing on an open or recent ticket is touched.
- The conversation stays. "Each deleted attachment is replaced with a placeholder. The messages and the rest of the conversation stay on the ticket."
- Copies elsewhere remain. "Copies outside Zendesk aren't deleted." Zendesk says this covers files "already delivered to a customer's device or messaging app (WhatsApp, Messenger, and others), email mailboxes, and downloaded copies."
- Some chat is excluded. "Chat attachments on accounts that don't use the Agent Workspace aren't deleted."
- Other content is out of scope. "Side conversations and help center content are still out of scope."
- It takes time. "The daily limit of 24,000 attachments per account covers all channels. Accounts with a large backlog may see existing deletions take longer."
The limit on copies elsewhere matters most for privacy. Deleting a file in the helpdesk doesn't remove it from the customer's phone, a WhatsApp thread or an agent's downloads folder.
What to check this week
- List your active schedules and read each condition as if it now applied to every channel, because it does.
- Decide per channel. If messaging or chat files need a different retention period (for disputes, chargebacks or regulated records), exclude them by group or tag, as Zendesk suggests.
- Check ticket deletion schedules too. Removing an attachment counts as a ticket update and can push back the ticket's own deletion.
- Write down your retention policy outside the tool: what you keep, for how long, and why. Then check the tool against it after every product change.
Earlier this week we looked at a different question about files: who can open an attachment link. That was about access. This is about how long a file exists and which channels a rule reaches.
Where DeskLeap stands
We checked our own code on 7 November 2026, and the honest answer is that DeskLeap has no retention scheduling at all:
- No automatic deletion. Ticket files are kept until someone removes them. A team member can delete an individual attachment on a ticket, and everything is deleted when the account itself is deleted. There is no schedule, no age rule and no bulk purge.
- Fewer places files arrive. Customers can attach files to tickets through the customer portal. Our live chat widget doesn't accept file uploads, and DeskLeap has no WhatsApp or Messenger channel. So the multi-channel scope problem Zendesk just created doesn't arise for us, but only because we cover fewer channels.
- Files never leave in email. Our notification emails don't attach files or link to them; customers open them in the portal after signing in.
If your team needs files deleted on a schedule, for example ID documents removed after a set number of days, DeskLeap doesn't do that today, and you would be doing it by hand.
DeskLeap is a ticketing, live chat and knowledge base platform. The platform is 100% free with unlimited human agents; an optional AI Agent add-on is $29/mo each.
Sources
Zendesk, Announcing expanded attachment deletion schedules for messaging and Chat tickets (announced and rolled out 6 November 2026; read 7 November 2026). Quotations are verbatim from that page. DeskLeap's behavior is described from our own code as of 7 November 2026.