Record a support request as an event
Each support form submission emits a "Support Requested" event with topic and priority, giving analytics a live view of inbound volume.
New Submission on your "Contact support" form
Create a "Support Requested" track event in Segment with topic and priority properties
One-directional. A submission triggers the action — nothing is written back into your form.
Support volume is a leading indicator, and it usually lives inside the helpdesk where nobody outside the support team looks at it. A spike in one issue type on a Tuesday afternoon stays invisible to everyone reading the analytics stack.
A "Support Requested" event changes that. Every intake submission lands in Segment carrying its issue type and priority, so a CS dashboard, an alerting tool and the warehouse all see inbound volume while it is happening rather than in next month's summary.
Setting it up
- 1
Publish the IT Help Desk Ticket form as your support intake, and keep Issue Type and Priority as fixed choice lists — free text in either one makes the properties useless for grouping.
- 2
In Zapier, set the New Submission trigger to that intake form and load a real ticket so the choice values come through as they will in production.
- 3
Add Segment as the action, choose Create Track Event, and name it Support Requested.
- 4
Map Work Email to the userId so tickets attach to the same profile your product events already use.
- 5
Send Issue Type as the topic property and Priority as the priority property. These two carry the whole recipe — everything else is context.
- 6
Add Ticket Subject as a subject property and Department as a department property, which is what lets you see whether one team generates most of the volume.
- 7
Keep Issue Description out of the event if tickets can contain personal detail. The event is for counting and routing; the description stays in the submission where access is controlled.
- 8
File one test ticket, confirm topic and priority appear on the event in the Segment source debugger, 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 | Segment |
|---|---|
| Work Email | userId on the Support Requested event |
| Issue Type | topic property |
| Priority | priority property |
| Ticket Subject | subject property |
| Department | department property |
| Affected Device or System | system property |
Variations worth knowing
Add a Zapier filter on Priority so only the highest tier continues to a second Segment action, an Urgent Support Requested event. Alerting destinations subscribe to that name alone, which keeps the on-call channel quiet during ordinary weeks.
When Did the Issue Start? gives you the respondent's own estimate. Send it as a started_at property alongside the event timestamp, and the gap between the two shows how long a fault runs before anyone tells you about it.
If something isn't arriving
Someone edited the choice labels on the published form. Segment stores whatever string arrives, so old and new labels count separately. Settle the list, then rename historical values in the warehouse rather than in the form.
Fall back to an anonymousId built from the Zapier submission ID when Work Email is blank. Volume reporting still works, and the event can be stitched to a profile later if that address ever signs up.
Frequently asked questions
Can I get alerted when high-priority support requests spike?
Yes, through Segment rather than the form. Send priority as a property, then have a destination that supports alerting watch the Support Requested event. The form's job ends at emitting the event; the threshold logic lives downstream.
Why send this to Segment instead of using a webhook?
A webhook is the right tool when one system needs the submission. Segment earns its place once several destinations need the same ticket data — dashboard, alerting, warehouse — because you map the fields once instead of maintaining three endpoints.
Does the person filing the ticket need an existing Segment profile?
No. Segment creates a profile from the userId on first sight, so a ticket from an unknown address simply starts one. Later events under the same email attach to it without any back-fill or manual merge.
Related automations
- Capture webinar registrations as track events
Each webinar signup fires a "Registered" event tied to the work email and session name, so reminders and reporting agree.
- Identify a new lead from a demo request
Every demo request becomes a Segment identify call, so the lead's traits reach your CRM, warehouse and ad tools at once.
- Log product feedback as an event
Each feedback response sends a "Feedback Submitted" event with rating and product category, ready to query beside in-app behaviour.
- Send order details as an Order Placed event
Each custom order submission emits an "Order Placed" event with product and quantity properties, feeding the warehouse without a developer.
- Track a newsletter signup as an event
Each subscribe form submission fires a "Signed Up" track event carrying the source, so every destination counts the signup the same way.
- Add webinar registrants to a remarketing list
Every webinar registration joins a Customer Match audience you can run follow-up campaigns to after the session.
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