> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/capabilities/session-insight.md).

# Session Insight

Session Insight reads every conversation as it closes, extracts the information you define, and writes it to your help desk, so tickets are always up to date without anyone filling them in.

*Last updated: November 7, 2026*

Session Insight reads every conversation when it closes, extracts the information you ask for, and **writes it to your help desk**. Contact reason, product, order number, sentiment, whether the issue was solved: it is filled in on the ticket automatically, on every ticket, and kept up to date when a ticket is reopened and closed again.

This is where its value lies: your help desk always holds complete, current information, without your team typing it in and without anyone forgetting.

### Why it matters

* **Help desk data you can trust.** Every closed ticket gets the same fields, filled the same way. No more empty or inconsistent fields that depend on who handled the ticket.
* **No work for your team.** Agents stop spending the end of every ticket on wrap-up forms. Conversations the AI handled get filled in too.
* **Always current.** When a ticket is reopened and closed again, it is read again and its fields are updated to match what happened.
* **Better reports, everywhere.** Your help desk's own views, reports, routing and automations run on these fields, so they all improve at once.
* **Issues and opportunities surface.** Extract product defects, feature requests or sales leads, and find them with a help desk filter.

### How it works

Session Insight is built on **analysis sets**, each a command that says what to extract:

* **Name** and **Description** - the description says which conversations the set is for, such as "for all support tickets" or "for sales conversations". When a conversation closes, the AI applies the set that best matches it.
* **Instruction** - what to do, for example "analyze the conversation and extract the information in the provided schema".
* **JSON Schema** - the fields to extract. Each field has a name, a type (text, number, whole number or yes/no) and a description of what it holds.

When a conversation closes:

1. The whole conversation is read.
2. The best-matching set extracts its fields.
3. The values are written to the ticket's fields in your help desk.

The result goes only to the help desk. Nothing is sent to the customer.

### Writing to your help desk

The values are written to fields of the same name on the ticket or conversation:

| Help desk | Fields updated          |
| --------- | ----------------------- |
| Zendesk   | Ticket fields           |
| Intercom  | Conversation attributes |
| Freshdesk | Ticket fields           |
| Gorgias   | Ticket fields           |

Front, Kustomer and Salesforce do not write fields from Session Insight yet.

Each field name in the schema must match the field's name in your help desk exactly. If a field accepts only values from a list, such as a dropdown, put the full list of allowed values in the field's description, so the AI picks one of them.

### Set it up

1. In your help desk, create the fields you want filled, such as **Contact reason**, **Product** and **Resolved**.
2. Go to **Insight → Session Insight** and turn it on.
3. Click **Add Command**. Name it, describe which conversations it is for, write the instruction, and add one schema field per help desk field, with the same names.
4. Check that **Automatically** is on under **How Session Insight Runs**.

To try a command before waiting for a conversation to close, open it and copy the in-note command shown at the bottom, `// <command id>`. Paste it into the internal note of a conversation to run it on that one. See [In-note Commands](https://doc.aissist.io/capabilities/in-note-command.md).

Session Insight is not available on the free plan.

### Check against your own documents

If your project has [Insight Assets](https://doc.aissist.io/capabilities/insight-assets.md), such as your categories, product list or wrap-up guidelines, Session Insight uses them when it extracts. For each conversation it looks up what the fields need to know and fills them in line with your own definitions.

### Best practice

* **Start with the fields your reports already need**, such as contact reason and product, and add more once those are reliable.
* **Describe each field the way you would brief a new agent:** what it means, and when to leave it empty.
* **List the allowed values for every dropdown field.** A value that is not in the list cannot be saved.
* **Keep one set per kind of conversation**, such as support and sales, with a clear description so the right one is picked.
* **Use your help desk's views and reports** on these fields to find trends, and update the set when you need something new.

### Related

* [In-note Commands](https://doc.aissist.io/capabilities/in-note-command.md)
* [Insight Assets](https://doc.aissist.io/capabilities/insight-assets.md)
* [Agent Insight](https://doc.aissist.io/capabilities/agent-insight.md)
* [Weekly Reports and Alerts](https://doc.aissist.io/capabilities/weekly-reports.md)
