Escalate a Ticket to Engineering, Properly
For bugs that customers find first. DuckyHelper reads the ticket, writes the repro steps and impact, creates the Linear issue, links the two, and puts the ticket on hold. The Slack heads-up goes out with it.
“Escalate this Zendesk ticket: create a Linear issue with repro steps, link it, and draft a note for #eng.”
- 01Write small tools for Zendesk and Linear, onceSmall JavaScript tools made from how each site already works. The next run calls them directly.
getTicket(id)addNote(id, text)setStatus(id, status)createIssue(team, fields) - 02Read the ticket and write repro steps
- 03Create the Linear issue with its impact
- 04Link the issue on the ticket and put it on hold
- 05Draft a two-line note for #eng
You getBugs engineers can act on. A clean issue, linked both ways, with the customer kept in the loop. The next escalation is one ask.
A run, drawn from this page · on Mac
Nothing to send, so it runs straight through.
Nothing in this job sends a message or pays for anything, so it works through to the end and tells you when it's done. It does not stop to ask before it acts, so keep an eye on any task that touches messages or money.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
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 "Escalate this Zendesk ticket: create a Linear issue with repro steps, link it, and draft a note for #eng."
Why is the second time faster?
The first time, it writes small JavaScript tools for Zendesk, Linear and Slack 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 doesn't stop to ask for now: when the job sends a message or pays, it does it. A Stop control stays on the window the whole time, Take control hands it back to you, and every task is recorded so you can watch it again. 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?
Bug reports get retyped from tickets to issues, and the customer details fall off along the way.
Can I use this today?
Yes: doing jobs in your apps is in the Mac app, for everyone. Talking to DuckyHelper, and having it see your screen and draw on it, works on Mac, Windows and Linux.
- On Mac
“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 - On Mac
“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 - On Mac
“Find all Zendesk tickets about today's login outage, merge duplicates, and draft one reply for everyone.”
Merge Duplicate Tickets and Reply Once
See it run
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in the Mac app. Asking works on Mac, Windows and Linux.
