For teams that run on Zendesk
Zendesk redact personal data from tickets
Customers often send more than you need: a passport number, a national ID number, a bank account number or health details. Zendesk removes credit card numbers on its own; for the rest, an agent removes it by hand or the account needs an add-on. In many countries the numbers have their own format.
How it goes today
- Spot the number while reading the ticket.
- Remove it by hand from the comment.
- Ask colleagues to do the same.
- Find old tickets with numbers during an audit.
How it can go
Keep national ID and account numbers out of your ticket history.
You choose what to remove, such as national ID numbers for your countries, bank account numbers or dates of birth, and how long they may stay, for example until a check is done. New comments are checked and the matches are removed after that time, with a tag on the ticket. A weekly list shows what was removed.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your Zendesk key in the portal, never in the chat.
With Hypamoon, check new comments in Zendesk for the kinds of numbers I choose, such as national ID numbers for our countries and bank account numbers. Remove them after the period I set and tag the ticket. Send me a weekly list of what was removed.
An administrator creates an OAuth client in Zendesk Admin Center, under Apps and integrations, APIs, OAuth clients, and limits what it may read and change. It stays yours.
More for teams on Zendesk
- I want a customer contact added as CC when a ticket matches a rule.
- Real emails end up in suspended and nobody looks in time.
- I want to see which macros are used and which are not.
- We only see the comment on a low rating if we open the ticket events.
- Customers want an overview of their company's tickets.
- I want to know what customers ask about, beyond how many tickets.
- I want help center articles as a PDF to print or send.
- A customer says thanks and the solved ticket is open again.
- When someone changes a trigger, I can't go back to how it was.
- I want the time we spent per client each month, so we can bill it.
- Tickets stay with an agent who is on leave.
- Every year I enter the holidays in each schedule again.
- I copy every order number into the shop to see what is going on.
- I want to send one message to a list of customers from Zendesk.
- I log in to each review site to read and answer reviews.
- Our contracts allow a number of tickets per month and nobody keeps count.
- We pay for agents who have not logged in for months.
- I want a message when a queue goes over a number.
- People without report access ask me for an export every week.
- I want a ticket to come back on the date I agreed with the customer.
- For every billing question I open another system to see what they pay.
- The same customer opens three tickets about one question.
- The same customer has two or three profiles in Zendesk.
- I look up every tracking number on the site of the carrier.
- Buyer questions on the marketplaces are answered outside Zendesk.
- We want NPS again and the score next to the customer in Zendesk.
- A customer asks for their data and I search ticket by ticket.
- I want to see which customers keep opening new tickets.
- The account details in our CRM do not reach Zendesk.
- IT hears about a new colleague when they are already at the door.
- I print tickets one by one to build a case file.
- I download attachments from each ticket to collect the documents.
- Everything for Zendesk