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.
New Submission on your "Contact us" form
Create a conversation in the Support mailbox using the submitter's name and email, with their message as the conversation body
One-directional. A submission triggers the action — nothing is written back into your form.
A contact@ address collects everything and sorts nothing. Sending the form into a Help Scout mailbox gives each message a customer record, a subject line worth scanning, and one person on the hook for the reply.
Small support teams reach for this when the inbox has outgrown one person. The form keeps its embed code and its own URL; the only change is where the message lands and who is responsible for answering it.
Setting it up
- 1
Publish the "Contact us" form with Subject and Message both required. Help Scout will not create a conversation without a subject, and an empty body leaves the first thread blank.
- 2
In Zapier, pick formformform's "New Submission" trigger and select the contact form itself, not another published form on the same account.
- 3
Add the Help Scout action, choose "Create Conversation", and authorise the Help Scout account whose mailboxes you want to write into.
- 4
Set Mailbox to Support. The dropdown only lists mailboxes the connected Help Scout user can see, so connect an account with access before you map anything else.
- 5
Map Email Address to the customer email. Help Scout matches it against existing customers and creates a new one when the address is unfamiliar.
- 6
Map Full Name into the customer first and last name fields. Zapier splits on the first space, so a single-word entry lands entirely in the first name.
- 7
Map Subject to the conversation subject and Message to the thread body, and set the thread type to customer so the message reads as though it came from the sender rather than from your team.
- 8
Leave the status as Active, send one test submission, confirm the conversation carries the right customer, then switch the Zap on.
What maps where
Using the Contact 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 |
|---|---|
| Full Name | Customer first and last name on the conversation |
| Email Address | Customer email — Help Scout matches an existing customer or creates one |
| Subject | Conversation subject line in the Support mailbox |
| Message | Body of the first customer thread |
| Phone Number | Phone number on the customer profile |
Variations worth knowing
Turn the form's Subject into a choice list and add a Zapier paths step on the answer. Billing questions can open in the Billing mailbox while everything else stays in Support, with the same customer mapping in each branch.
Add a static tag such as web-form on the Create Conversation step. Help Scout reports can then separate form volume from replies that arrive by email, and a saved search on that tag shows what the form is bringing in each week.
If something isn't arriving
The customer email is mapped to a fixed address, usually the notification address on the Zap, instead of the form's Email Address field. Re-map it to the field itself and re-test. Help Scout groups by email, so one address means one customer with a very long history.
Help Scout only sends the mailbox auto-reply when the conversation is created with auto reply switched on, and that setting is off by default on the Zapier action. Turn it on, or send the confirmation from formformform on submission instead.
Frequently asked questions
Can an agent's reply write anything back to the form?
No. The connection runs one way: a submission opens the conversation, and nothing returns to formformform. Your reply goes to the sender by email from the Support mailbox, while the submission stays in your responses list as the original record of what was asked.
Which mailbox do conversations land in if I run several?
The one you pick on the action step, and only that one. A single Zap writes to a single mailbox. Route by adding a paths step in Zapier before the action, or let a Help Scout workflow move the conversation once it has arrived.
Do the messages still exist in formformform?
Yes. Every submission stays in your responses list, where you can filter, search and export it. Help Scout holds the conversation and the reply history; the form holds the original answers, which matters when a mailbox is later archived or tidied up.
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.
- 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.
- 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.
- 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