> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thena.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Forms

> Define what information is collected when a ticket is created.

Forms in Thena allow teams to define what information is collected when a ticket is created. From capturing customer inputs to internal triage details, Forms help ensure every ticket starts with the right context.

## What are forms

<Card>
  <p>Forms are customizable layouts used to collect structured data from users—whether customers, agents, or teammates. Each form consists of one or more fields, and you can define who can view, edit, or be required to fill them.</p>

  <p className="mt-4">Forms are used:</p>

  <ul className="mt-4 ml-6 space-y-2">
    <li>During ticket creation (web, Slack, chat, or API).</li>
    <li>To control what appears in the ticket view.</li>
    <li>To guide agents and customers through dynamic data capture.</li>
    <li>To power downstream automation, workflows, and analytics.</li>
  </ul>
</Card>

## Fields in forms

<Card>
  <p>Before creating a form, you need fields.</p>

  <h3 className="mt-4 font-medium">Standard fields (built-in by Thena)</h3>

  <ul className="mt-2 ml-6 space-y-2">
    <li>Requester (mandatory)</li>
    <li>Title (mandatory)</li>
    <li>Status</li>
    <li>Assignee</li>
    <li>Account</li>
  </ul>

  <p className="mt-2">These are common across all tickets.</p>

  <h3 className="mt-4 font-medium">Custom fields (user-defined)</h3>
  <p className="mt-2">You can define custom fields to match your specific workflow:</p>

  <ul className="mt-2 ml-6 space-y-2">
    <li>Text inputs</li>
    <li>Dropdowns</li>
    <li>Date pickers</li>
    <li>Multi-selects</li>
    <li>Toggles</li>
    <li>Cascading fields based on logic</li>
  </ul>

  <div className="mt-4 border-t pt-4">
    <p>For detailed information on standard fields and how to create custom fields, see the <a href="/guides/ticketing/ticket-fields">Ticket fields</a> guide.</p>
  </div>
</Card>

## How to create a form

<Steps>
  <Step title="Go to settings">
    Navigate to Settings → Forms.
  </Step>

  <Step title="Create form">
    Click "Create form".
  </Step>

  <Step title="Enter basic info">
    <ul className="ml-6 space-y-2">
      <li>Name your form.</li>
      <li>Give a description.</li>
    </ul>
  </Step>

  <Step title="Add fields">
    <ul className="ml-6 space-y-2">
      <li>Requester and Title are mandatory.</li>
      <li>Add any standard or custom fields needed for your workflow.</li>
      <li>Use drag-and-drop to reorder.</li>
    </ul>
  </Step>

  <Step title="Set field properties">
    For each field, configure:

    <ul className="mt-2 ml-6 space-y-2">
      <li>Visible in customer portal</li>
      <li>Editable by requester</li>
      <li>Required on creation</li>
      <li>Required on close</li>
    </ul>
  </Step>

  <Step title="Set conditions (optional)">
    <ul className="ml-6 space-y-2">
      <li>Add logic to dynamically show or hide fields.</li>
      <li>Example: Show "Escalation reason" if Priority = High.</li>
      <li>Conditions override default field settings.</li>
    </ul>
  </Step>

  <Step title="Preview and save">
    <ul className="ml-6 space-y-2">
      <li>Instantly toggle between Agent view and Requester view.</li>
      <li>Once saved, the form becomes selectable during ticket creation.</li>
    </ul>
  </Step>
</Steps>

<Frame caption="Creating a new form with field configuration options.">
  <img src="https://mintcdn.com/thena-840ce5ec/qw0IBJ-u1Oc1t24_/images/docs/Create-form.webp?fit=max&auto=format&n=qw0IBJ-u1Oc1t24_&q=85&s=03796e1fb729dd9a6b2a6116918b9bf0" alt="Form creation interface" width="7680" height="4800" data-path="images/docs/Create-form.webp" />
</Frame>

## Where forms are used

<CardGroup cols={3}>
  <Card title="Thena" icon="browser">
    Agents can choose team and form at ticket creation.
  </Card>

  <Card title="Customer portal" icon="user-group">
    Form is shown as per visibility rules.
  </Card>

  <Card title="Slack" icon="slack">
    Slack modal opens if enabled.
  </Card>

  <Card title="Web chat" icon="message">
    Form questions embedded in chat.
  </Card>

  <Card title="API" icon="code">
    Submit structured form data programmatically.
  </Card>
</CardGroup>

## What happens after a form is used

<Card>
  <p>Forms unify the ticket creation experience—no matter where it starts.</p>

  <p className="mt-4">Once a ticket is created with a form:</p>

  <ul className="mt-2 ml-6 space-y-2">
    <li>The form appears on the right-hand panel of the ticket.</li>
    <li>Agents can view or switch forms.</li>
    <li>Fields reflect form-level visibility, permissions, and logic.</li>
    <li>Customers can update editable fields via the customer portal.</li>
    <li>All updates sync in real time and are fully auditable.</li>
  </ul>
</Card>

## Best practices

<AccordionGroup>
  <Accordion title="Standardization" icon="layer-group">
    <ul className="ml-6 space-y-2">
      <li>Use forms to enforce consistent ticket intake across teams.</li>
      <li>Create templates for common ticket types.</li>
      <li>Establish naming conventions for fields and forms.</li>
    </ul>
  </Accordion>

  <Accordion title="Clarity" icon="lightbulb">
    <ul className="ml-6 space-y-2">
      <li>Use field descriptions to guide users.</li>
      <li>Keep forms as short as possible while capturing necessary information.</li>
      <li>Group related fields together for better user experience.</li>
    </ul>
  </Accordion>

  <Accordion title="Personalization" icon="user-gear">
    <ul className="ml-6 space-y-2">
      <li>Use conditional fields to show relevant fields based on input.</li>
      <li>Create team-specific forms (e.g., Customer Support vs IT).</li>
      <li>Regularly review and prune unused fields/forms.</li>
    </ul>
  </Accordion>

  <Accordion title="Insights" icon="chart-line">
    <ul className="ml-6 space-y-2">
      <li>Align forms with the metrics you want to report on.</li>
      <li>Include fields that will help with categorization and analysis.</li>
      <li>Consider how form data will be used in dashboards and reports.</li>
    </ul>
  </Accordion>
</AccordionGroup>

## Example use cases

<Tabs>
  <Tab title="Customer support">
    <ul className="ml-6 space-y-2">
      <li>Product version</li>
      <li>Type of issue (bug, feature request, feedback)</li>
      <li>Customer segment</li>
      <li>Steps to reproduce</li>
      <li>Urgency level</li>
      <li>Preferred contact time</li>
    </ul>
  </Tab>

  <Tab title="IT support">
    <ul className="ml-6 space-y-2">
      <li>Device or asset ID</li>
      <li>Affected system or app</li>
      <li>Error message or code</li>
      <li>Is this blocking work? (Yes/No)</li>
      <li>Location (onsite or remote)</li>
      <li>Desired resolution time</li>
    </ul>
  </Tab>
</Tabs>

Forms in Thena are your system of record for clean, contextual, and actionable support data—across every channel and every team. Whether you're scaling customer operations or managing internal IT requests, Forms give you structure, clarity, and measurable insight.