> 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.md).

# Tutorial

The recommended path from sign-up to a live Aissist AI agent - onboarding, workspace, assets, actions, sub-agents, testing and deployment, step by step in the console.

*Last updated: October 25, 2026*

These pages take you from sign-up to a live AI agent, step by step in the [Aissist console](https://console.aissist.io/). Follow them in order the first time. Each page links to its capability page when you want the concepts behind the steps.

### Recommended path

1. [Quick Start](/tutorial/quick-start.md): the whole path on one page, with a pre-launch checklist.
2. [Onboarding Analysis](/tutorial/onboarding-analysis.md): connect your help desk and see what your customers ask, how your team resolves it, and what Aissist would resolve.
3. [Create a Workspace](/tutorial/create-workspace.md): draft the agent from your website and help desk, then set its character, instructions, greeting and escalation.
4. [Add Assets](/tutorial/add-assets.md): give the agent the knowledge it answers from - your website, web pages and Google files.
5. [Add Actions](/tutorial/add-actions.md): connect your systems through a connector, then let the agent look things up and get things done.
6. [Add Sub Agents](/tutorial/add-sub-agents.md): handle each scenario - returns, order tracking, billing - with its own instructions, assets and actions.
7. [Try](/tutorial/try.md): test conversations, read what shaped each reply, and fix what is off.
8. [Deploy](/tutorial/deploy.md): put the workspace to work in your help desk.

### Deploy to your help desk

After the shared steps in [Deploy](/tutorial/deploy.md), follow the page for your help desk:

* [Intercom](/tutorial/deploy/intercom.md)
* [Zendesk](/tutorial/deploy/zendesk.md), tickets and messaging
* [Front](/tutorial/deploy/front.md)
* [Gorgias](/tutorial/deploy/gorgias.md)
* [HubSpot](/tutorial/deploy/hubspot.md)
* [Freshdesk Omni](/tutorial/deploy/freshdesk-omni.md)
* [Kustomer](/tutorial/deploy/kustomer.md)
* [Salesforce](/tutorial/deploy/salesforce.md)
* [WATI](/tutorial/deploy/wati.md)
* [Chatwoot](/tutorial/deploy/chatwoot.md)

### Do it with Ask Engine

Ask Engine (**Ask** in the console sidebar) works alongside every step. Several create pages are Ask Engine itself: you describe what you want in your own words, Ask Engine drafts it from what your workspace already knows, and you review the draft before anything is created.

> How do I hand over refund requests to my billing team?

> Add the page <https://example.com/returns-policy> for the Returns sub-agent

Ask Engine answers product questions from this documentation, and questions about your own workspace from its own data. See [Ask Engine](/capabilities/ask.md).

{% hint style="info" %}
Start with one workflow. Test it. Then expand to more scenarios.
{% endhint %}

### Best practice

* Run the onboarding analysis first if you have a help desk: it tells you which topics to build for.
* Build one workflow end to end - knowledge, action, sub-agent - before adding the next.
* Test every change in **Try** before it reaches customers.
* Go live on one inbox or group first, watch the results, then widen.

### Related

* [Capabilities](/capabilities.md)
* [Success Metrics](/success-metrics.md)
* [FAQ](/faq.md)