> For the complete documentation index, see [llms.txt](https://docs.wrangle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wrangle.io/tickets/ai-powered-ticketing/ai-ticket-deflection.md).

# AI Ticket Deflection

<figure><img src="/files/SrXSOt1pm199oGivKsdT" alt=""><figcaption></figcaption></figure>

### How it works

First, add links to public-facing documents to your inbox, [connect to Notion](/integrations/notion.md), or upload PDF documents if you prefer to work with private documentation.\
\
These documents contain answers to common questions you get in this inbox; for example, documentation for HR inboxes might include benefits information, your employee handbook, and instructions for accessing your company's HR portal.\
\
Wrangle's AI reads your documentation and looks for an answer whenever new questions are submitted to your intake channel.\
\
If Wrangle finds an answer, it will reply to the request with a summary of its findings, links to the relevant documentation, and the option to either close the issue or open a ticket.

If Wrangle doesn't find an answer, it will automatically open a ticket.

{% hint style="info" %}
**Measuring performance:**  See how your AI Ticket Deflection is working — including outcome breakdowns, which knowledge base sources are being used, and response quality ratings — in the [AI Deflection reports](/reporting/ticket-reporting/ai-deflection-reports.md).
{% endhint %}

#### Requirements for ticket deflection

Ticket deflection is part of the Scale plan. **Contact us** at <sales@wrangle.io>, or reach out to us over live chat [here](https://slack.wrangle.io/support) to discuss adding it to your Wrangle account.

#### Required Form Fields and AI Ticket Deflection

If your inbox has required form fields, Wrangle will send the user a prompt asking them to fill out the form.  Once the user has filled out the required fields, Wrangle can attempt to deflect a ticket with an AI response.  Your user's required form field answers are not used in the deflection attempt, but are preserved in case a ticket needs to be created. &#x20;

### Document links

You may use public-facing URLs (such as <https://wrangle.apidocumentation.com/>) for AI ticket deflection. Wrangle will automatically scan your content (every 24 hours) for updates, so we recommend you use this option when possible.&#x20;

#### How link following works

When you add a public URL to AI Ticket Deflection (like your help center or documentation), Wrangle doesn't just read that single page. It automatically discovers and indexes up to 50 additional pages linked from your original URL.

**Example:**

* You add: `yourcompany.com/help`
* AITD indexes that page, plus follows links to pages like:
  * `yourcompany.com/help/billing`
  * `yourcompany.com/help/setup`
  * `yourcompany.com/help/troubleshooting`
  * (up to 50 linked pages total)

### Document uploads

If you have your documentation in a private knowledge base or wiki, you'll first need to export any relevant articles or pages as PDFs. If your knowledge tool does not include an export-to-PDF option, you can copy and paste the page contents to a Google Doc or Word document, then save that as a PDF.&#x20;

Once your PDFs are ready, navigate to your Inbox Settings, open the AI Ticket Deflection tab, then click Add Documents. You can add up to 100 documents, as long as none of them exceed 10MB. If you need to edit a document, you can delete it from your inbox and upload the updated version.

### How tickets work with deflection enabled

Once ticket deflection is enabled and your help documents have been uploaded or linked to Wrangle, Wrangle's AI will start attempting to answer questions as they come in.

When Wrangle finds a match in your documentation, it will reply to the requester's message with both a summary of its answer, as well as links to the corresponding documentation. It'll also ask the requester whether their question has been answered, or if they'd like to open a ticket.

<figure><img src="/files/N3Q1pe99xJm6FzAXFFmb" alt="" width="563"><figcaption><p>Wrangle's AI answering an incoming question</p></figcaption></figure>

If the requester selects "Yes, this answered my question" Wrangle will not open a ticket. If the requester selects "No, start a ticket" Wrangle will open a ticket directly within the thread.&#x20;

<figure><img src="/files/UyLQqPxCvAPy8Gp54RFW" alt="" width="494"><figcaption><p>Wrangle's AI can't find an answer, so it opens a ticket</p></figcaption></figure>

{% hint style="info" %}
Want to customize the tone of the Wrangle bot's responses, or how short or long they are?  Check out [Customize tone & verbosity](/tickets/ai-powered-ticketing/customize-tone-and-verbosity.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.wrangle.io/tickets/ai-powered-ticketing/ai-ticket-deflection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
