Log support requests as Zoho CRM cases
Each support request opens a Case in Zoho CRM with subject, priority and description, linked to the contact who reported it.
New submission on your help or support form
Create a Case in Zoho CRM linked to the matching Contact, with subject, priority and description
One-directional. A submission triggers the action — nothing is written back into your form.
Not every team wants a separate help desk product. If your account records already live in Zoho CRM, the Cases module is a reasonable place to run support from — one system, one contact history, and a sales rep who can see that their account raised three tickets last month.
Internal IT teams and managed service providers use this shape most. The request arrives with a subject and a priority the reporter chose, and the Case opens against the person who sent it rather than a nameless queue.
Setting it up
- 1
Publish the help desk form in formformform with Ticket Subject, Priority and Issue Description, and word the Priority options to match the picklist values already in your Zoho CRM Cases layout.
- 2
In Zapier, use the formformform New Submission trigger on this support form, then add a Zoho CRM Find Contact search step keyed on Work Email.
- 3
Switch on "create the record if it doesn't exist" in that search step, so a first-time reporter still produces a Contact instead of failing the run.
- 4
Add the Zoho CRM Create Module Entry action pointed at Cases, and pass the Contact id from the search step into the Case's Contact Name lookup.
- 5
Map Ticket Subject to Case Subject and Issue Description to Description, unedited — the reporter's own wording is what an engineer needs.
- 6
Set Case Origin to Web and Status to New as fixed values in the Zap, so every form-raised case starts in the same place in your views.
- 7
Map Priority through a Zapier lookup table if your form wording and Zoho CRM's picklist do not match character for character.
- 8
Raise a test ticket, check it lands linked to the right Contact and appears in the open cases view, then enable the Zap.
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 | Zoho CRM |
|---|---|
| Ticket Subject | Case Subject — what appears in the queue list |
| Issue Description | Case Description, kept as written by the reporter |
| Priority | Case Priority, matched to your picklist values via a Zapier lookup table |
| Work Email | The lookup key for Find Contact, which supplies the Case's Contact Name |
| Issue Type | Case Type or Category, whichever your layout uses for triage |
| Affected Device or System | A custom field on the Case, so engineers can filter by system |
Variations worth knowing
Add a Zapier path on Priority. Highest and High set an explicit Case Owner and a status of Escalated; everything else takes the default. One form, two routes, and nobody has to watch the queue for the ones that matter.
The Find Contact step returns the Contact's Account Name. Map that into the Case's Account Name field and reporting shifts from person to organisation, which is what a managed service provider needs when renewals come round.
If something isn't arriving
The reporter's work email is not in Zoho CRM, so Find Contact returned nothing and the lookup was left blank. Tick the option to create the contact when the search finds none, and check the form asks for the same address the CRM holds.
Zoho CRM rejects picklist values it does not recognise, and "Urgent" on your form is not "High" in the layout. Either rename the form options to match exactly, or add a Zapier lookup table that translates each one before the Case is created.
Frequently asked questions
Can the person who raised the ticket see its status?
Not through the form. The connection runs one way only — a submission creates the Case, and nothing is written back. Send status updates from Zoho CRM by email, or give reporters a portal login if your edition includes one.
Should I use Cases in Zoho CRM or a dedicated help desk?
Cases work well when the same team sees accounts and tickets and the volume is modest. A dedicated desk product gives you SLAs and threaded replies. If you move, keep the same form and repoint the Zapier action at the new app.
What stops one issue opening several cases?
Each submission creates one Case, so a reporter who submits twice gets two. Add a Zapier Find Case step matching on subject and contact if that happens often, and tell people to reply to the case email rather than filling the form again.
Related automations
- Add newsletter signups to Zoho CRM as tagged contacts
Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from.
- Create a Zoho CRM deal from each quote request
A quote request opens a Deal carrying the service, timeline and stated budget, with the full brief kept as a Note.
- Open a Zoho CRM deal from every demo request
Each demo request opens a Deal at the Qualification stage of your demo pipeline, dated from the buyer's stated timeline.
- Turn contact sales submissions into Zoho CRM leads
Each contact sales submission creates a Lead in Zoho CRM, ready for your assignment rules to hand to a rep.
- Turn webinar registrations into leads with a follow-up task
Each webinar registration creates a Lead stamped with the event as its source, plus a follow-up task dated after the session.
- Add webinar registrants as labelled people
Every webinar registrant becomes a Pipedrive person carrying a registration label you can filter on later.
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