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

# Connect Pia SmartForms to Thread Triage Agent

> Integrate Pia SmartForms with Thread so users can launch onboarding, password reset, and access request workflows from an Open Form button in chat.

### Integrating Thread with Pia (SmartForms)

#### Overview

This integration connects **Thread** with **Pia** to automate complex workflows directly within the chat interface. By linking these platforms, you can trigger Pia **SmartForms** (such as User Onboarding, Password Resets, or Access Requests) immediately when a user expresses a specific intent.

**What the user sees:** Instead of being redirected to a portal, the user receives an interactive **"Open Form"** button directly in the chat. When clicked, a branded form appears over the chat window, allowing them to submit data instantly.

Once a SmartForm is sent, the Triage Agent stays active and follows up automatically based on the form outcome — confirming submission, handling cancellations, and closing or escalating the ticket based on your intent configuration.

#### Prerequisites

Before you begin, ensure the following are in place:

* **PSA Connection:** Your PSA (Autotask, ConnectWise, or Halo) must be successfully connected and active in **Pia → Integrations**.
* **Admin Access:** You will need administrator access to both Thread and PIA to exchange API keys.
* **Microsoft Graph:** The specific client must have authorized the Microsoft Graph API within PIA.

Please contact your Pia Customer Success Manager if you do not see these options available in your Pia Workspace.

### Configuration guide

<Steps>
  <Step title="Connect Thread to Pia">
    To establish a secure connection, you will need to copy distinct keys between the two platforms. Open two tabs: one for **Thread Admin** and one for **Pia**.

    1. Navigate to **Thread → Admin → Integrations → Pia**.
    2. Navigate to **PIA → SmartForms → Integrations**.
    3. **Exchange the Keys:**
       * **From Pia to Thread:** Copy the **"Thread App API secret"** from Pia and paste it into the **"API secret key"** field in Thread.
       * **From Thread to Pia:** Copy the **"Thread embed key"** from Thread and paste it into the **"Embed key"** field in Pia.
  </Step>

  <Step title="Configure SmartForms in Pia">
    For a form to appear in Thread, it must be properly configured on the Pia side first.

    * **Create:** Ensure the SmartForm exists inside Pia.
    * **Enable:** Verify the form is enabled for the specific client you are testing.
    * **Assign:** Assign the form to the necessary PSA company (if applicable).
  </Step>

  <Step title="Link Intent in Thread">
    Once connected, you need to tell Thread when to show the form.

    1. Go to the **Thread** dashboard.
    2. Select or create the **Intent** (e.g., "New User Onboarding").
    3. In the intent settings, enable the option to use a **Pia SmartForm**.
    4. Select the specific SmartForm you configured in Step 2.

    **Configure Post-Form Agent Behavior (Optional)**

    Once you have selected a SmartForm, two new optional fields appear to control what the Triage Agent does after the form is completed.

    **External Reply**

    A free-form prompt field that instructs the agent what to say to the contact after the form is submitted or canceled. Use conditional language to cover both outcomes. Example:

    > *"If the form was submitted successfully: confirm the submission and let the contact know the team is on it. If the form was canceled or there was an error: apologize and let them know a technician will follow up shortly."*

    Leave this field empty to use a default confirmation message.

    **Resolution checkbox — "Close the request if the contact confirms"**

    * **Checked:** After the form is submitted, the agent asks the contact whether their issue is resolved. If they confirm, the ticket closes automatically. If they say no, the agent escalates to a technician.
    * **Unchecked:** The agent confirms the form submission and escalates to a technician automatically without waiting for contact confirmation.

    <Note>
      Both fields are optional. Existing Pia intents work without any changes — the agent will stay active by default after a form is sent.
    </Note>
  </Step>
</Steps>

#### Testing and validation

##### Test internally before rolling out

We recommend testing the flow internally before rolling it out to production.

<Steps>
  <Step title="Trigger the flow">
    Open the chat window and type a phrase matching your intent (e.g., "I want to onboard a new user").
  </Step>

  <Step title="Verify the prompt">
    The bot should respond with a card containing an **"Open Form"** button.
  </Step>

  <Step title="Check the form">
    Click the button. A pop-up form (branded with the client's logo, if set) should appear requesting details like Name, Start Date, and Job Title.
  </Step>

  <Step title="Submit and verify">
    Fill out the form and click **Send**. Confirm that:

    * The form iframe closes automatically after submission.
    * The agent sends a follow-up message in chat confirming the form was submitted (using your External Reply prompt if configured, or a default message if not).
    * If the resolution checkbox is checked: the agent asks the contact whether their issue is resolved. Confirming closes the ticket. Denying escalates to a technician.
    * If the resolution checkbox is not checked: the agent confirms the submission and escalates to a technician automatically.
    * The data is correctly written back to your PSA.
  </Step>

  <Step title="Cancel and verify">
    Close the form without submitting. Confirm that:

    * The form iframe closes automatically.
    * The agent acknowledges the cancellation in chat and escalates to a technician.
  </Step>
</Steps>

#### Post-form agent behavior

After a Pia SmartForm link is sent to the contact, the Triage Agent stays active and responds based on what happens next.

|                                        |                                                                                                                                                                                   |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scenario                               | What the agent does                                                                                                                                                               |
| Form submitted                         | Sends a confirmation message (using your External Reply prompt or a default). Closes ticket if contact confirms (checkbox checked) or escalates to tech (checkbox unchecked).     |
| Form canceled or error                 | Acknowledges the outcome and escalates to a technician for review.                                                                                                                |
| Contact messages while form is pending | Normal triage continues. The form stays open in the background and the agent handles the new message as usual.                                                                    |
| No action taken                        | Agent enters listening mode based on your standard triage timeout settings. A single check-in is sent. If still no response, the Reminder Agent takes over on its normal cadence. |

### Getting started with Pia intents

Below are common PIA/Thread intent descriptions that work well to get you started.

<AccordionGroup>
  <Accordion title="Change calendar permission">
    When the request strongly indicates a user wishes to add, remove, or change another users access to their Microsoft email calendar or outlook calendar, immediately acknowledge the request and inform the user that the Change Calendar Permissions form will be launched. Do not ask any additional questions before triggering the Pia Smartform.
  </Accordion>

  <Accordion title="Setup or remove out of office - SmartForm">
    When the request strongly indicates a user wishes to setup or remove an out of office (ooo) message for their email, immediately acknowledge the request and inform the user that an Out of Office form will be launched. Do not ask any additional questions before triggering the Pia Smartform.
  </Accordion>

  <Accordion title="Grant or remove email access">
    When the request strongly indicates a user wishes to grant or remove another user's access to their email or shared mailbox, immediately acknowledge the request and inform the user that the Grant or Remove Email Access form will be launched. Do not ask any additional questions before triggering the Pia Smartform.
  </Accordion>

  <Accordion title="Forwarding rule">
    When the request strongly indicates a user wishes to add or remove a rule to redirect incoming emails to a specific person, immediately acknowledge the request and inform the user that the Mail Forwarding Rule form will be launched. Do not ask any additional questions before triggering the Pia Smartform.
  </Accordion>

  <Accordion title="Lockout request">
    When the request strongly indicates a user needs to unlock their account due to entering their password incorrectly too many times, immediately acknowledge the request and inform the user that the Account Locked Out form will be launched. Do not ask any additional questions before triggering the Pia Smartform.
  </Accordion>

  <Accordion title="Reset password">
    When the request strongly indicates a user needs their password reset, immediately acknowledge the request and inform the user that the password reset form will be launched. Do not ask for a user's name or password. That information will be asked when the user fills out the Pia SmartForm. Do not ask any additional questions before triggering the Pia Smartform.
  </Accordion>

  <Accordion title="Onboarding">
    When the request strongly indicates a brand-new employee requiring full onboarding, immediately acknowledge the request and inform the user that the onboarding form will be launched. Do not ask any additional setup questions before triggering the Pia SmartForm.
  </Accordion>

  <Accordion title="Offboarding">
    When the request strongly indicates user offboarding, immediately acknowledge the request and inform the user that the offboarding form will be launched. Do not ask any additional setup questions before triggering the Pia SmartForm
  </Accordion>
</AccordionGroup>


## Related topics

- [Smart Dispatch](/skill-library/scheduling-and-dispatch/smart-dispatch.md)
- [Ticket Triage](/skill-library/triage-and-routing/ticket-triage.md)
- [Backup Failure Triage](/skill-library/devices-and-infrastructure/backup-failure-triage.md)