# Set Up a Contact Form on your own Website with the Planio Help Desk The [Planio Help Desk App](https://plan.io/customer-service-and-help-desk/) in Planio enables you to handle customer inquiries right from within Planio using all the Planio [issue tracking](https://plan.io/task-management/) features you love. Normally, this is done via email. In this guide, however, we will look at setting up a customizable online form on your own website that sends your customer's messages directly to Planio where they'll appear as issues. {{>toc}} ## Benefits - Reply to website inquiries directly from Planio using the [Help Desk App](https://plan.io/customer-service-and-help-desk/). - Don't let inquiries slip through the cracks in your overloaded email inbox. - Work as a team on customer support. - Become more efficient by using auto-replies and Help Desk templates. - No need for server-side scripting to handle the contact form submissions. ## HTML Form You can send HTML form requests directly to Planio, as Planio will accept an unauthenticated POST request with `application/x-www-form-urlencoded` form data. Therefore, we’re going to build a simple form with an action attribute that submits the form to Planio via the HTTP POST method. ~~~html
~~~ You will have to replace `example.plan.io` with your own Planio domain. Then, we’ll add input fields for a name, email, email subject, and the description: ~~~html ~~~ A Planio account can have multiple projects, so we need a way to assign this message to a particular project in Planio. Therefore, we’ll add a hidden input field with the value set to the identifier of the project you want to forward the issue: ~~~html ~~~ *Please note*: The field needs to be set to the project identifier, not the project name (e.g. `help-desk` instead of "Help Desk"). Then, we add a submit button: ~~~html ~~~ ## Add a Honeypot Field Forms are frequently the target of spambots that send messages to any form they can find online. One strategy for dealing with spam bots is to add an additional input field to the form called a honeypot field. Then, you hide the form field using CSS. If that input field is filled out, which spambots usually do, then the message is discarded as spam - hence the name honeypot field. Here’s the honeypot field along with some CSS: ~~~html ~~~ Using a honeypot field is optional but we highly recommend it to avoid spam. ## Submit the form using Ajax After receiving your contact form data, Planio will redirect back to the page it came from. This works nicely in many cases, but you might want to display a short "Thank you" message to your users once the form is submitted instead and make the form appear a little more snappy. Here's one way to achieve that with an Ajax call using jQuery: ~~~html ~~~ ## A Practical Example So, pulling it all together, a full HTML page including our form would look like this: ~~~html Contact us!

Contact us!

Something went wrong. Please try again.

Thank you for getting in touch.

~~~ *You can download the entire HTML page here:* [*contact-us.html*](https://support.plan.io/attachments/download/412799/contact-us.html). When someone fills out this form, the message will show up in Planio as an issue as you can see here: {{figure(A contact form message appears as issue in Planio) ![](email-from-contact-form@2x.png) }} That’s just one of the examples of how you can use the Redmine API at Planio to streamline your processes. You’ll find more examples and documentation, including how to add your own **custom fields** to your contact forms, in our [Redmine API documentation](https://plan.io/api/#issues-via-contact-forms).