# Quick Start

*Last updated: May 12, 2026*

Set up your first Aissist workspace and go live safely.

This guide covers the shortest path from setup to live conversations.

{% stepper %}
{% step %}

### Create a workspace

[Sign in](https://console.aissist.io/) and create a workspace for one business function.

Add these basics:

* your website
* the main job for the agent
* the support channel you plan to use

Then go to **Workspace → Setting**.

We recommend:

* select a response language or enable **Auto Language**
* give Aissist a name in **Identity** so it can refer to itself naturally

Greeting, escalation, task, and closing behavior can wait.

{% hint style="info" %}
Use one workspace per team or workflow, such as support, sales, or a single store.
{% endhint %}
{% endstep %}

{% step %}

### Add global instruction and context

Go to **Workspace → Instruction** and add behavior rules.

Go to **Workspace → Context** and add business facts.

Keep global instructions short. Put detailed scenario handling instructions in sub agents.

Continue with [Tune Aissist Behavior](/tutorial/tune-aissist-behavior.md) for deeper guidance.
{% endstep %}

{% step %}

### Add assets

Assets give Aissist the knowledge it uses in replies.

You can connect:

* websites
* web pages
* Google Drive files

See [Turn Assets into AI](/tutorial/turn-assets-into-ai.md).
{% endstep %}

{% step %}

### Connect live systems

If you need live data or business actions, add an integration.

Use [Integrations](/integrations.md) to connect systems like Shopify, Supabase, and any RESTful API.

This helps Aissist resolve more issues with live data and real actions.
{% endstep %}

{% step %}

### Create sub agents

Use sub agents for distinct workflows, such as order tracking, returns, or booking.

Each sub agent can:

* define trigger scenarios
* add scenario-specific instructions
* use linked assets and actions
* control response or human handoff behavior

See [Create Sub Agents](/tutorial/create-sub-agents.md).
{% endstep %}

{% step %}

### Test before going live

Validate behavior before you enable production traffic.

Use:

* [Simulator](/tutorial/simulator.md)
* [Asset Debugger](/tutorial/turn-assets-into-ai/asset-debugger.md)
* [Action Debugger](/integrations/action-debugger.md)

Fix missing knowledge, conflicting content, and weak instructions before rollout.
{% endstep %}

{% step %}

### Deploy the gateway

When Aissist is ready, connect it to your support platform.

Use [Deploy Gateway](/tutorial/deploy-gateway.md) to deploy Aissist into your agent platform.
{% endstep %}
{% endstepper %}

### Roll out safely

Start with a small number of conversations or tickets each day.

Then:

1. monitor live sessions and collect feedback
2. refine assets, instructions, and sub agents
3. gradually increase traffic as results improve

Use [Streamline with Human Team](/tutorial/streamline-with-human-team.md) to plan handoff and review.


---

# 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:

```
GET https://doc.aissist.io/tutorial/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.