# Online Web Forms

{% hint style="warning" %}
Web forms is a part of the Custom plan. Additional cost might apply.
{% endhint %}

## Overview

You can automatically create support tickets from online web forms. Simply send form submissions to your [Suptask email integration](/integrations-automations-and-workflows/email-ticketing-setup.md), and your team can reply just like any other ticket where the requester will receive the reply via email.

***

### Why Use Web Form to Ticket Integration?

This setup is perfect for capturing:

* Customer inquiries from your website
* Internal requests from your intranet
* Issue reports or feedback submissions

By connecting your form tool (like **Tally Forms**) to Suptask’s email integration, each form submission becomes a trackable, reply-ready support ticket.

***

### What You’ll Need

* An active email integration in Suptask
* A web form tool like Tally, Clickup or Form Craft.
* Access to set up form notifications (we recommend using Tally's "Self email notifications")
* Suptask email integration is required to be enabled in one of your Suptask Inboxes.

***

### Setup Guide&#x20;

This setup guide is using Tally Forms as an example, same setup applies to other form vendors (Formcraft, Clickup etc).&#x20;

Follow these steps to forward form submissions to Suptask:

1. **Create your form** in Tally.\
   Add fields like:
   * **Name**
   * **Email** (this will be used later in Suptask to help set the requester)
   * **Message or Description**
2. **Go to your form’s “Email Notifications” in the forms settings**&#x20;
3. **Enable “Self email notification.”**
4. **The From email field needs to be the same email that you have enabled with the** [**Suptask email integration**](/integrations-automations-and-workflows/email-ticketing-setup.md)
5. Set the **recipient email** to:

   ```
   incoming@suptask-mail.com
   ```
6. **Include the email field** in the notification settings so you can use it in Suptask  to populate the requester’s email.
7. **Ensure your Suptask workspace has** [**email integration** ](/integrations-automations-and-workflows/email-ticketing-setup.md)**enabled.**\
   If it’s not enabled yet, reach out to your Suptask admin or contact support.

<figure><img src="/files/t6ekjABaF7ZP13ET3n9h" alt="" width="563"><figcaption><p>How the email notification can be configured in Tally form<br>in order to capture tickets.</p></figcaption></figure>

#### **Preview of the form:**

<figure><img src="/files/KCFLVpWhYDIN7kSLpUsq" alt="" width="375"><figcaption><p>Preview on how the form can look in Tally when it is ready.</p></figcaption></figure>

***

### What Happens Next?

* Each form submission is sent to `incoming@suptask-mail.com`
* Suptask automatically creates a ticket in your Inbox
* The ticket requester is visible in the email content and can be set so that replies goes to the correct destination.&#x20;
* Your support team can reply directly via Suptask in Slack, just like any other ticket.
* The requester will receive replies back via the set email

***

### Tips

* Use custom fields in your form to capture extra data.
* Tag or route these tickets differently in Suptask using [AI routing](/suptask-ai/ai-email-routing.md)
* You can test the setup by submitting your form and confirming ticket creation in your Suptask inbox.

***

### Need Help?

If you need help setting up email integration or configuring Tally, reach out to our support team. We’re happy to walk you through it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.suptask.com/setup-and-configure/online-web-forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
