Send refund requests to the billing mailbox
Refund requests become trackable conversations in the Billing mailbox, with the order number in the subject and an owner attached.
New Submission on your "Refund request" form
Create a conversation in the Billing mailbox with the order number, reason and purchase details, assigned to the billing queue
One-directional. A submission triggers the action — nothing is written back into your form.
A refund request that lands as an unstructured email gets answered when somebody happens to notice it. As a conversation in the Billing mailbox it has an order number in the subject, a reason in the body and a named owner.
Small e-commerce teams use this to keep finance and support out of each other's way. The form gathers what is needed to make the decision; the refund itself is still issued in whatever tool took the original payment.
Setting it up
- 1
Publish the refund form with Order Number required, and use conditional logic to ask the return question only when the reason involves a physical item.
- 2
In Zapier, set the trigger to formformform's "New Submission" and select the refund form.
- 3
Add Help Scout's "Create Conversation" action and set Mailbox to Billing, so refunds sit apart from general support traffic.
- 4
Compose the subject as "Refund" followed by Order Number. Finance searches by order, and a subject that opens with the same three words for everyone is useless in a list.
- 5
Map Email Address to the customer. Help Scout attaches the request to the buyer's existing history, so an agent can see what they bought and what they have already asked about.
- 6
Put Reason for Refund, Additional Explanation and Preferred Refund Method into the body in that order, each behind a short heading.
- 7
Set an assignee on the action, or add a Help Scout workflow on the refund tag that assigns to the billing queue. An unassigned money question is the one that gets left.
- 8
Test with a real order number, confirm the conversation lands assigned, then turn the Zap on.
What maps where
Using the Refund Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Help Scout |
|---|---|
| Order Number | Conversation subject, so the mailbox is searchable by order |
| Email Address | Customer on the conversation — matches the buyer's existing history |
| Reason for Refund | First line of the conversation body |
| Additional Explanation | Body, under the reason |
| Has the item been returned or will it be returned? | Body, so the agent knows whether to wait for the return |
| Preferred Refund Method | Body, for whoever processes the refund in your payment tool |
Variations worth knowing
Create the conversation with the status set to Pending when the return question says the item is still with the customer. Help Scout keeps pending conversations out of the active queue, so finance only sees the ones ready to process.
The form captures the request; the refund is issued in whatever payment tool took the original order. Treat the Help Scout conversation as the record of the decision and the reply, not as the transaction.
If something isn't arriving
Either the field is optional on the form or the mapping points at a question the customer skipped. Make Order Number required in formformform and add a Zapier filter that drops submissions without one, so finance never opens a request it cannot look up.
The action is writing to the wrong mailbox. Zapier keeps the last mailbox you selected when a Zap is duplicated, so reopen the Help Scout step, set Mailbox to Billing explicitly, and re-test instead of assuming the change saved.
Frequently asked questions
Can the conversation refund the order automatically?
No. The form captures the request and Help Scout holds the thread, but the refund is issued in the payment tool that took the original order. Native payment handling is not part of the product, so the money step stays where it already lives.
How do I tell which requests have been dealt with?
Use the conversation status. Active means nobody has looked, Pending means it is waiting on a return or a payment run, and Closed means the customer has been answered. Finance can filter the Billing mailbox by status at the end of each week.
Do customers get a reference number they can quote?
Only if you put one in the reply. Help Scout gives every conversation a number, and a saved reply that includes it gives the customer something concrete to mention when they write back about the same order.
Related automations
- Collect product feedback as tagged conversations
Ratings and comments open as tagged conversations in a Feedback mailbox you can filter, search and revisit when planning.
- Create the customer record before the first reply
Onboarding intake answers become a Help Scout customer record, so agents see who the person is before the first conversation opens.
- Land demo requests in the sales mailbox
Demo requests open as conversations in the Sales mailbox, carrying company size, the problem to solve and the timing.
- Open a support conversation from every contact form message
Each contact form message arrives in your Support mailbox as a conversation, attributed to the sender and ready to assign.
- Route bug reports into a tagged engineering conversation
Bug reports open in the Engineering mailbox, tagged and carrying the severity and reproduction steps the reporter filled in.
- Capture feature requests as labelled tickets
Product ideas from your feedback form land in Freshdesk as Feature Request tickets the team can group and revisit.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free