For teams that run on Zendesk
Zendesk GDPR request: one person's data
Under privacy laws such as the GDPR in Europe and the UK, the CCPA in California or the LGPD in Brazil, a person can ask what you hold on them and ask you to delete it, within a set time. In Zendesk their data can sit in many tickets, profiles and attachments, and someone gathers it by hand.
How it goes today
- Search the person by email, phone and name.
- Open each ticket and copy the conversation.
- Download the attachments one by one.
- Delete the tickets and the profile by hand.
How it can go
Answer privacy requests on time without searching ticket by ticket.
You give the request: who it is and whether they want their data or want it deleted. Their profile, tickets, comments and attachments are gathered into one file with a list of what was found, which you check and send. When they ask for deletion, the tickets and profile are deleted after you approve, and the date is kept in your log.
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, when I log a privacy request, find what we hold on that person in Zendesk: profile, tickets, comments and attachments. Put it in one file with a list of what was found for me to check. If they ask for deletion, delete their tickets and profile after I approve, and keep a log with the date.
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.
- Customers send ID numbers and we remove them by hand.
- 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