Open an Intercom conversation from a support form
Form-based support tickets arrive in the Intercom inbox as real conversations agents can reply to and assign.
New submission on your "Contact support" form
Create a Conversation in Intercom from the customer's email, with the issue summary and priority as the message body
One-directional. A submission triggers the action — nothing is written back into your form.
Support requests that arrive by form usually land in a shared mailbox, where they lose the reply history and the assignment rules the rest of the team already uses. This recipe opens a real Intercom conversation instead, attached to the person who submitted, so an agent can answer from the inbox they work in all day.
Internal IT desks and small support teams use it to retire a second mailbox. The priority the requester chose travels into the message body, so triage happens before anyone opens the ticket.
Setting it up
- 1
Publish the help desk form with Priority and Issue Type as required questions — the conversation body is only as useful as those two answers.
- 2
In Zapier, choose formformform's "New Submission" trigger and select the support form.
- 3
Add Intercom's "Create a Conversation" action and set it to come from the user, using Work Email as the person the conversation belongs to.
- 4
Build the message body from Ticket Subject on the first line, then Priority and Issue Type, then Issue Description underneath.
- 5
Append Affected Device or System and "When Did the Issue Start?" to the end of the body so the first responder does not have to ask.
- 6
Agree with the team what happens to senders Intercom has not seen before, since those arrive as new records rather than as known customers.
- 7
Test with a low priority submission, confirm the conversation lands in the inbox and can be assigned, then turn the Zap on.
What maps where
Using the IT Help Desk Ticket as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Intercom |
|---|---|
| Work Email | The Intercom user the conversation is created from |
| Full Name | Name on the Intercom contact the conversation attaches to |
| Ticket Subject | First line of the conversation body |
| Priority | Conversation body, above the description, for triage |
| Issue Description | Main text of the conversation body |
| Affected Device or System | Appended to the end of the conversation body |
Variations worth knowing
Add a Zapier path or filter on Priority. High priority submissions run an Intercom action that assigns the conversation to your on-call team, while everything else opens unassigned in the general inbox.
Follow the conversation step with Intercom's "Add Tag to Contact" action, using Issue Type as the tag. Reporting on which categories generate the most tickets then comes out of Intercom rather than out of a spreadsheet export.
If something isn't arriving
Intercom needs an email address to attach a conversation to someone. If Work Email is optional on the form, submissions without it will fail the Zapier step. Make the field required, or add a filter that skips submissions with no email.
Zapier does not add line breaks for you. Put each mapped field on its own line in the body editor, and keep Priority on a line by itself so it is readable at a glance from the inbox list.
Frequently asked questions
Can agents reply from Intercom and reach the person who filled in the form?
Yes, because the conversation belongs to a real contact carrying the email address from the form, so the reply goes out through Intercom as normal. The form is not part of that thread and never receives anything back from it.
What happens if the same person submits the support form twice?
Each submission opens its own conversation. Intercom attaches both to the same contact when the email address matches, so an agent can see the earlier thread in that person's history and close whichever one is the duplicate.
Do I need the IT help desk template, or will any support form work?
Any form works. This recipe uses the help desk template because it already asks for a subject line and a priority, which are the two answers that make a conversation readable in the inbox. Add both if you build your own form.
Related automations
- Create a contact for every new order
Each order form submission creates or updates the buyer's Intercom contact and records what they ordered.
- Log customer feedback as a note on the contact
Feedback lands as a note on the customer's Intercom record, so the next agent to open the conversation has the context.
- Record webinar signups on the contact record
Webinar registrations build an Intercom audience with a registered_event attribute you can send reminders against.
- Tag contacts by what they asked for
The option someone picks on the interest form becomes an Intercom tag, so segments and outbound series stay accurate.
- Turn demo requests into Intercom contacts
Every demo request becomes an Intercom contact with company, role and a source attribute, ready for follow-up.
- 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