Handle a Refund Request End to End
For refund requests that need three tabs. DuckyHelper reads the request in Intercom, finds the charge in Stripe, checks it against your refund policy, sets up the refund and drafts the reply. The refund goes through as part of the job, so set your limits in the ask.
“Handle this Intercom refund request: find the Stripe charge, check our 30-day policy, and prepare the refund and the reply.”
- 01Learn the web APIs of Intercom and Stripe, first time onlyBuilt from each site's own buttons, forms and requests. Kept on your device and reused next time.
getConversation(id)createDraft(conversation, body)findCharge(email)createRefund(charge, amount) - 02Read the request
- 03Find the charge in Stripe
- 04Check it against your policy
- 05Issue the refund
- 06Draft the reply
You getFair, fast refunds. Every refund is checked against your policy before it goes through.
A run, drawn from this page · on Mac
It sends it, on the record.
It does the work, then sends the refund, as the job says. You can read exactly what it wrote in the task's recording, and Stop is on the window the whole time.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
Do it once. Repeats come later.
Repeating it on its own (whenever a new one comes in) is not in the app yet. Today you ask again when you need it, and each run goes through the API it learned the first time, so it's quick.
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 "Handle this Intercom refund request: find the Stripe charge, check our 30-day policy, and prepare the refund and the reply."
Why is the second time faster?
The first time, it writes small JavaScript tools for Intercom and Stripe 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?
Refunds mean finding the charge, checking the policy and writing back, each in a different tool.
Can it keep doing this on its own?
Not yet. Repeating a job on its own (whenever a new one comes in) is not in the app yet. Today you ask again when you need it, in the Mac app.
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.
