Plan requirement
| Subscription | Any plan |
| Access | Admin |
Yes, in three ways. Zendesk's own answer names the Web Widget (Classic) and the messaging Web Widget as the ready-made options, a custom HTML form posting through the API as the built one, and third-party apps from the Marketplace as a route it does not support.
Which should you pick?
The widget, for most sites. The Classic widget's contact form is on by default and asks for name, email address and a description of the problem. It handles identity, attachments and validation, the customer stays on your page, and it takes minutes.
The link is underrated. Sending people to your help centre's request form means they see the articles on the way, and a share of them never submit because they found the answer. That is the outcome you wanted.
Your own form, when it has to sit inside an existing flow, look exactly like your site, or collect something the standard form cannot. That is real, and it is a build with an owner and a maintenance cost.
Check the fields first: the Classic widget takes no Regex, Date or Multi-select custom field, and no system field such as Priority.
What does a custom form need?
You map your fields to Zendesk's and post the request through the API. The prerequisite people miss is that the person filling it in is not signed in, so anonymous submission has to be allowed: the setting is Anybody can submit tickets. With it off, a form that looks correct gets rejected.
Whatever you choose, ask for less: every field is a reason to give up. Say on the form when they will hear back, and test it on a phone.
Comments
0 comments
Article is closed for comments.