How to turn website contact form messages into help desk tickets

Turn website contact form messages into help desk tickets with a native form, webhook or forwarding, and make sure every reply reaches the customer's...

A website contact form on a laptop beside a help desk ticket queue on a second monitor

Quick Answer

Send each contact form submission into your help desk through its native form or a webhook, so the ticket opens under the customer's email address. Forward the notification email only when its reply-to is the submitter's address. Then answer a test message, on Help Scout's free plan or any help desk, and confirm the reply lands in the customer's inbox.

Did this answer your question?
Three things small support teams believe about contact form tickets. Myth or fact?
Call each one, then see how other readers called it.
1 Forwarding the form's notification email to your help desk means replies reach the customer.
2 The help desk's spam filter is enough, so the form needs no protection of its own.
3 A small team can route form messages into a help desk without paying for one.
A website contact form on a laptop beside a help desk ticket queue on a second monitor

A contact form submission arriving as a help desk ticket

How do I send website contact form messages to my help desk?

Send each submission into the help desk through its native form, an incoming webhook, or a forwarded notification email, then confirm the customer becomes the ticket requester instead of your website.

The three routes differ on two points: who the ticket belongs to, and where spam gets stopped. A native help desk form creates the ticket with the submitter as the requester. A webhook is an HTTP POST from your form to an address the help desk gives you, and it works only when you map the email field. Email forwarding is the easiest route to set up and the easiest to break, because the notification often arrives from your website's own address. In my view, a webhook is worth the extra setup whenever your form plugin offers one, because the requester then comes from a field you control rather than from whatever address the notification happens to use.

What you need

  • A help desk with a support email address, an embeddable form or an incoming webhook URL
  • Your website form, with separate name, email, subject and message fields
  • One dropdown field for the request category
  • A spam control: a hidden honeypot field or your form host's spam filter
  • Two email addresses you control, for testing

Check the help desk's terms first if your form collects health details. When Zazachat checked Help Scout's own pages on Oct 29, 2026, Help Scout signed a HIPAA BAA, with HIPAA support only on the Pro plan. To price a help desk for your team size before you connect anything, use the help desk cost calculator or compare published help desk prices.

Steps

  1. Choose the route. Use the help desk's own form if it offers one. Use a webhook if your form plugin supports it. Forward email only when neither exists.
  2. Map each field. Send subject to the ticket title, message to the ticket body, and email to the requester. For a webhook, set the method to POST and the format to form data.
  3. Add a category field. Zendesk's own guidance recommends putting a custom field such as Product on the support request form, so customers pick the category themselves.
  4. Turn on spam filtering before the form sends anything to the help desk.
  5. Connect the form. Paste the embed code or the webhook URL, or set the notification address to your help desk's support address.
  6. Check the reply-to. Open a forwarded ticket and confirm the requester is the person who filled in the form.
  7. Test the full loop. Submit from both test addresses, reply from the help desk, then answer that reply. All three messages should sit in one ticket.
  8. Watch the form channel. InvGate recommends breaking ticket volume down by channel and setting alert thresholds for abnormal increases. A sudden jump from the form usually means spam or duplicates.

Common mistakes

  • Your website shows up as the customer. Set the notification's reply-to to the submitter's email field.
  • Spam opens tickets. Filter on the form side, before the help desk ever sees the message.
  • One message creates two tickets. Turn off the email notification once the webhook or native form is live.

Frequently asked questions about contact form tickets

Why do replies go to my website's address instead of the customer?

The notification comes from your form host, so the help desk treats that host as the customer. The fix is the reply-to address: the header that tells email where answers should go. Set it to the submitter's email field, or switch to a webhook that maps the email field straight to the requester.

Why am I getting duplicate tickets from one form submission?

Two routes are live at once, usually a webhook plus the old email notification. Turn one off. InvGate also recommends tracking ticket volume by channel and by hour, day and week, which makes a doubled form channel easy to spot.

Can an AI support agent answer form tickets, and how is it billed?

Check that your help desk's AI support agent covers the form channel, not only email. Billing units differ: across the 41 support tools Zazachat tracks, Help Scout's pricing page, checked Oct 29, 2026, bills $0.75 per AI Answers resolution, while Freshdesk's pricing page, checked in October 2026, includes 500 AI agent sessions once per account, then $49 per 100. Compare each vendor in its own unit before you switch it on.

Written by

Michael Kansky

Connect on LinkedIn