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.
New Submission on your "Onboarding intake" form
Create a customer in Help Scout with the name, email, company and account details from the form
One-directional. A submission triggers the action — nothing is written back into your form.
Onboarding is where you learn the most about a customer and where it is easiest to lose it. This flow takes what the intake form collects and writes it onto a Help Scout customer record before anyone has opened a conversation.
Teams running a hands-on onboarding reach for it because the payoff comes later. The first time that person emails support, the company, the size and the use case are already sitting in the sidebar, and nobody has to ask twice.
Setting it up
- 1
Create the customer properties you want to fill in Help Scout first. Industry and Company Size will not appear in Zapier's field list until they exist on the Help Scout side.
- 2
Publish the "Onboarding intake" form with Email Address required. Help Scout keys customers on the email, and a record without one can never be matched to a later conversation.
- 3
In Zapier, use formformform's "New Submission" trigger and select the onboarding form.
- 4
Add Help Scout's "Create Customer" action rather than "Create Conversation". This recipe builds the profile; it does not open a thread.
- 5
Map Your Name into the first and last name fields, and Company Name into the company field on the customer record so the account shows next to the person.
- 6
Map Industry and Company Size onto the matching customer properties, and put Primary Use Case into the background notes where an agent will actually read it.
- 7
Refresh the sample submission in Zapier after any change to the form, or questions you added later will be missing from the mapping list.
- 8
Test with an address Help Scout has not seen before, check the record in the sidebar, then turn the Zap on.
What maps where
Using the Customer Onboarding Survey as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Help Scout |
|---|---|
| Your Name | First and last name on the Help Scout customer |
| Email Address | Primary email on the customer record — the key everything else matches on |
| Company Name | Company field on the customer profile |
| Industry | Customer property, visible in the sidebar during a conversation |
| Company Size | Customer property, so agents see the account size before replying |
| Primary Use Case | Background notes on the customer record |
Variations worth knowing
Add a second Help Scout action after the customer step: Create Conversation in the Onboarding mailbox, using the same email address. Because the customer already exists, the conversation attaches to the profile you just built instead of creating a second one.
A profile nobody looks at is a form nobody finishes. Cut the intake to name, email, company and the one question that changes how you reply. Primary Use Case usually earns its place; a question about technical background rarely does.
If something isn't arriving
Help Scout rejects a second customer with an email it already holds. Put a Zapier filter or a Find Customer step ahead of the action so people already on file are skipped or updated, rather than created again and failing the run.
Company and customer properties only surface once a conversation is linked to that customer by email. If the person later writes in from a personal address instead of the work one they gave you, Help Scout treats it as a different customer.
Frequently asked questions
Does the record update when someone fills the intake in again?
Not by itself. Create Customer builds a new record and fails on a duplicate email. To keep a profile current, add a Find Customer step and use Help Scout's update action, or treat the newest submission as the record of what changed.
What is the point of a customer with no conversation attached?
The profile is waiting when the first conversation arrives. An agent opening a reply sees the company, the size and the use case in the sidebar, instead of asking questions the customer already answered during onboarding a month earlier.
Can I store which plan someone is on?
Yes, as a customer property. Create the property in Help Scout, map the form answer to it, and it appears in the sidebar on every conversation with that person. The value is set from the form; nothing flows back the other way.
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.
- 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.
- 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