> 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/tutorial/onboarding-analysis.md).

# Onboarding Analysis

Run Aissist's onboarding analysis - connect your help desk read-only and get a report of your volume, the resolution Aissist would reach, handoffs, topics and complaints.

*Last updated: October 25, 2026*

Onboarding is where every Aissist project starts. This page walks through it, explains the analysis of your past conversations, and shows how to read the report and act on it.

### What onboarding does

Onboarding starts from your business domain and offers two paths:

* **Analyse my current support**: connect your help desk and get a report on your support conversations. The report is shown on screen, saved, and emailed to you.
* **Create a workspace**: draft an AI agent workspace from your website, and from your help desk if you connect it. See [Create a Workspace](https://doc.aissist.io/tutorial/create-workspace.md).

You can run the analysis first and then create a workspace from it. That is the recommended order when you have a help desk: the analysis tells you what your customers come for before you build anything.

### Start onboarding

{% stepper %}
{% step %}

### Enter your business domain

New accounts are asked **What would you like to do first?** right after sign-up. Otherwise, open the workspace menu at the top of the console and choose **Create New Workspace**.

Type your website's domain, such as `yourcompany.com`, and click **Continue**. If you signed up with a business email, the domain is filled in for you.

If your website is published in several languages, choose the main one. The report and the draft are written in it. You can change it later on the next screen.
{% endstep %}

{% step %}

### Choose a path

On **What would you like to do?**, choose **Analyse my current support**.
{% endstep %}

{% step %}

### Connect your help desk

On **Connect your help desk**, pick your help desk. You can:

* choose a connector you already have and click **Use this one**, or
* click **Connect a new one** and fill in the form: sign in with the help desk in a pop-up, or enter an API key, then click **Connect and test**.

The connection is tested before you can continue. A connector made here is an ordinary connector of your project: your gateway, actions and assets can use it later. See [Connectors](https://doc.aissist.io/capabilities/connectors.md).

{% hint style="info" %}
The analysis is read-only. Aissist never replies, edits, tags or changes anything in your help desk. Conversations are not stored: only the summary analysis is saved, to your reports. When you use an API key, a key from a read-only agent is the safest choice, because a key carries its owner's permissions.
{% endhint %}
{% endstep %}

{% step %}

### Choose inboxes or groups

Pick the inboxes, groups or teams your support team works from (the name follows your help desk). Keep them all ticked for a random sample across everything, or tick only some to analyse those alone. Each one shows its conversations in the last 90 days when the help desk reports it.

Click **Start analysis**.
{% endstep %}

{% step %}

### Wait for the report

The running page shows each step as it happens: reading your website, measuring your total volume, importing and reading conversations, finding the main topics, measuring first contact resolution, and writing the report.

This usually takes 5 to 20 minutes, depending on your help desk. If you leave the page, the analysis keeps running and the report is emailed to you when it is ready. **Cancel analysis** stops it, and nothing is saved or emailed.
{% endstep %}
{% endstepper %}

### What the report shows

**Your support analysis** has five sections. Each one has its key figures, a one-line summary, a table, and a short explanation of how it was counted.

| Section                                   | What it tells you                                                                                                                                                                                                                                                       |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Volume**                                | Conversations and messages per month, by channel. Counted from your help desk, not guessed.                                                                                                                                                                             |
| **Resolution and cost with Aissist**      | The share of conversations Aissist would resolve without a person, as an estimate with a range, by kind of request (simple questions, status and lookups, action requests, diagnosis and troubleshooting, exceptions needing a person), and the estimated monthly cost. |
| **Handoffs and first contact resolution** | How many conversations were handed over and why, how many were settled by the first response, and how long customers waited after a handoff.                                                                                                                            |
| **Main topics**                           | What customers come for, each topic with its share of traffic, first contact resolution, estimated resolution with Aissist, and inferred NPS and CSAT.                                                                                                                  |
| **What customers complain about**         | The share of conversations with a complaint, the main complaint themes, and action items that would remove each cause.                                                                                                                                                  |

A summary at the end lists what was analysed (how many conversations, from which help desk, inboxes or groups, and dates) and one takeaway per section.

{% hint style="warning" %}
The analysis is an estimate from a sample of conversations in the inboxes or groups you selected. Actual results can differ widely, so it must not be used for contract binding.
{% endhint %}

Use the buttons at the top of the report:

* **Download PDF**: the same report as a PDF.
* **Create a workspace from this analysis**: go straight to drafting a workspace, with your domain and help desk kept.
* **Restart**: run another analysis or pick the other path.

If the email did not go out, the report says why, with a **Resend** button.

### How to act on it

**Start with the topics.** The biggest topics are your first sub-agents. A workspace drafted from the analysis proposes sub-agents from the main topics for you.

**Read why conversations were handed over.** Each reason points to a different fix:

| Reason                                                                  | What to do                                                                                                                                                                      |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Missing knowledge                                                       | Add the article or page that answers it. See [Add Assets](https://doc.aissist.io/tutorial/add-assets.md).                                                                       |
| Needs a lookup or action                                                | Connect the system and add the action, such as an order lookup. See [Add Actions](https://doc.aissist.io/tutorial/add-actions.md).                                              |
| Policy exception, needs approval                                        | Write the policy into the instruction, or decide who may approve what.                                                                                                          |
| Customer asked for a person, technical or complex, complaint or emotion | Keep a person in the loop: set escalation and a handover rule to the right team. See [Escalation and Handover](https://doc.aissist.io/capabilities/escalation-and-handover.md). |

When the analysis finds handed-over conversations that a page on your website or help center already answers, the handoff summary says so. Add that site as an asset so Aissist can answer those on the first reply. See [Add Assets](https://doc.aissist.io/tutorial/add-assets.md).

**Work the complaints.** The action items under each complaint theme are often outside support: a delay, a charge, a product issue. Share them with the team that owns the cause.

**Compare with the estimate later.** Once live, track real resolution in the console. See [Success Metrics](https://doc.aissist.io/success-metrics.md).

### Do it with Ask Engine

The analysis and the workspace draft are both run by Ask Engine. When you create a workspace within 30 days of analysing the same help desk, the draft reuses that analysis instead of reading your conversations again.

Once your workspace is live, keep asking the same questions of your real traffic in **Ask**:

> What are the most common issues in the recent conversations? List suggestions if available

> List all the primary reasons for escalation for recent conversations, and identify opportunities to reduce AI escalation.

Ask Engine reads your conversations and escalation reasons and answers with counts and examples. See [Ask Engine](https://doc.aissist.io/capabilities/ask.md).

### Best practice

* Keep all inboxes or groups ticked unless some are clearly out of scope, such as an internal or spam queue.
* Connect with a read-only account or key.
* Build first for the topics with the largest share and the highest estimated resolution.
* Treat the figures as a starting estimate, not a promise. Measure the real result after go-live.

### Related

* [Create a Workspace](https://doc.aissist.io/tutorial/create-workspace.md)
* [Connectors](https://doc.aissist.io/capabilities/connectors.md)
* [Sub Agents](https://doc.aissist.io/capabilities/sub-agents.md)
