Merge Duplicate Tickets and Reply Once
For outage days. DuckyHelper learns Zendesk's web API once, finds every ticket about the same problem, merges them in bulk, and drafts one clear reply for all of them. You check it, then it goes out.
“Find all Zendesk tickets about today's login outage, merge duplicates, and draft one reply for everyone.”
- 01Turn Zendesk's own requests into an APIIt watches Zendesk's own requests once and saves them as actions. Kept on your device.
searchTickets(query)mergeTickets(target, ids)replyAll(ids, body) - 02Find tickets about the same problem
- 03Merge the duplicates in one call
- 04Draft one clear reply
- 05Ask before it replies to everyone
You getA clear queue in minutes. One answer for everyone, and a queue that shows the real issues again.
A run, drawn from this page · early access on Mac
It's built to wait for your OK.
It does the work, then stops with the reply ready for you. You see exactly what it wrote, then Send, Edit or Deny.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
Do it once. Then let it repeat.
When it's done, it offers to keep doing it: every weekday at 8:00 AM. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.
Always-on automations are in early access on Mac.
Before you ask it.
What do I say?
Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Find all Zendesk tickets about today's login outage, merge duplicates, and draft one reply for everyone."
Why is the second time faster?
The first time, it writes small JavaScript tools for Zendesk and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.
Will it send anything without me?
It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.
Why not just do it by hand?
When something breaks, the queue floods with the same question, and agents answer it one ticket at a time.
Can it keep doing this on its own?
Yes. When it's done it offers to make it automatic (every weekday at 8:00 AM). Each run goes the same way and is still built to ask before it sends or pays.
Can I use this today?
Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.
- Early access
“Triage new Zendesk tickets: set priority and area, route urgent ones to on-call, and tag billing.”
Triage the Support Queue in One Go
See it run - Early access
“Draft a reply to this Zendesk ticket using the customer's HubSpot account and their past tickets.”
Support Reply With the Customer's Full Story
See it run - Early access
“Handle this Intercom refund request: find the Stripe charge, check our 30-day policy, and prepare the refund and the reply.”
Handle a Refund Request End to End
See it run
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.
