Support Reply With the Customer's Full Story
For replies that should know who they're talking to. DuckyHelper reads the conversation, the customer's plan and owner in HubSpot, and their last five tickets, then drafts a reply in the ticket for you to send or edit.
“Draft a reply to this Zendesk ticket using the customer's HubSpot account and their past tickets.”
- 01Write small tools for Zendesk and HubSpot, onceSmall JavaScript tools made from how each site already works. The next run calls them directly.
getTicket(id)listTickets(requester)getCompany(domain)
- 02Read the ticket conversation
- 03Pull the account's plan and owner from HubSpot
- 04Read their last five tickets
- 05Draft a reply that fits
- 06Leave it for you to send
You getReplies that feel personal. Every reply knows the customer's history. With both sites learned, the next draft is instant.
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.
ZendeskReplyNeeds your OKBefore 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 "Draft a reply to this Zendesk ticket using the customer's HubSpot account and their past tickets."
Why is the second time faster?
The first time, it writes small JavaScript tools for Zendesk and HubSpot 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?
The customer has written in four times this month, but the agent only sees today's ticket.
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
“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 - 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.