> 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/instructions-assets-and-sub-agents.md).

# Instructions, Assets, and Sub Agents

*Last updated: May 14, 2026*

Use this model to decide where information belongs in Aissist.

Aissist uses three layers of guidance:

* **Instructions** for global behavior
* **Sub agents** for workflow-specific handling
* **Assets** for interaction-level knowledge

Each layer has a different job.

This is the simplified version of the global, session, and interaction model in [Tune Aissist Behavior](/tutorial/tune-aissist-behavior.md).

### Instructions

Instructions are the global rules for your workspace.

They shape how Aissist behaves in every conversation.

Use instructions for things like:

* tone and writing style
* escalation rules
* broad response requirements

Keep them short and always relevant.

See [Tune Aissist Behavior](/tutorial/tune-aissist-behavior.md) for more guidance.

### Sub Agents

Sub agents define how Aissist handles specific scenarios.

They apply only when a matching scenario is detected.

Use sub agents for:

* returns
* order tracking
* sales qualification

Sub agents can also:

* add contextual instructions, context, task, summary, and acknowledgement
* link specific assets or actions
* control reply, handoff, no response, or close behavior

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

### Assets

Assets are the knowledge sources Aissist searches during a conversation.

They can include help center pages, websites, policies, and documents.

When a user asks a question, Aissist retrieves relevant asset content only when it matches the current question.

Use assets for:

* policy and product information
* operational details
* reference material the agent should cite or follow

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

### How they work together

These layers work together like this:

1. **Instructions** set the global behavior for the workspace.
2. **Sub agents** add workflow-specific logic after a matching scenario is triggered.
3. **Assets** provide interaction-level knowledge when relevant to the current question.

In practice, a sub agent can also link the assets or actions needed for that workflow.

This keeps responses consistent, relevant, and focused.

### Best practice

Use each layer for the right job:

* put broad rules in **Instructions**
* put workflow logic in **Sub Agents**
* put knowledge in **Assets**

Avoid putting everything in one place.

That makes the agent easier to manage and more accurate over time.