# Tune Aissist Behavior

*Last updated: May 13, 2026*

Use instructions and context to shape how Aissist responds.

Use the right level for the job:

* **Global** for rules that apply everywhere
* **Session** for guidance tied to a workflow
* **Interaction** for knowledge retrieved only when relevant

### How instruction levels work

Use this model to decide where information belongs.

| **Level**       | **Where to configure** | **When it applies**             | **Best for**                                       |
| --------------- | ---------------------- | ------------------------------- | -------------------------------------------------- |
| **Global**      | Workspace              | Always                          | tone, guardrails, identity, universal rules        |
| **Session**     | Sub agents             | After the workflow is triggered | workflow-specific guidance that should stay active |
| **Interaction** | Assets                 | Only for the current question   | reference knowledge retrieved on demand            |

### Global instructions and context

Global instructions and context live in the workspace.

Use them for information that should influence every conversation.

Examples:

* keep replies concise
* reply in a specific language
* never confirm an appointment directly
* use a specific brand identity or tone

<figure><img src="/files/USgVglxE69OPtu9Ng4ha" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Business name, identity, purpose, and task settings also act as global guidance.
{% endhint %}

### Session instructions and context

Session instructions and context live in sub agents.

Use them for workflow-specific behavior that should stay active once the scenario is detected.

Examples:

* return handling steps
* order tracking workflows
* escalation rules for billing issues
* structured summaries for the human team

{% hint style="info" %}
Session guidance stays active after the sub agent is triggered. It does not disappear after one message.
{% endhint %}

{% hint style="info" %}
Use [Create Sub Agents](/tutorial/create-sub-agents.md) to define workflow-specific instructions, context, summaries, and linked assets or actions.
{% endhint %}

### Interaction context from assets

Assets provide interaction-level context.

This content is retrieved only when it matches the current question.

Use assets for:

* FAQs and policy pages
* product details and help center content
* reference material that should appear only when relevant

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

### What instructions can do

Instructions are best for shaping behavior.

Use them to:

* define tone, style, and response format
* tell Aissist how to act in a given scenario
* guide reasoning order or response flow
* tell Aissist what to prioritize in a reply

### What instructions cannot do

Instructions do not replace assets, sub agents, or integrations.

Do not use them to:

* retrieve live data from systems
* create tags, summaries, or workflow state changes on their own
* keep a conversation open or close it
* run business actions like sending notifications or updating records

Use sub agents and integrations when the workflow needs actions, routing, or structured outputs.

### What context does

Context gives Aissist the information it needs to answer well.

Use context to supply facts, reference material, and workflow details.

Put high-level facts in the workspace. Put workflow-specific details in sub agents. Put reference knowledge in assets.

### Best practice

Keep global instructions short.

Move topic-specific guidance into sub agents.

Use assets for knowledge retrieval, not for universal rules.


---

# Agent Instructions: 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/tune-aissist-behavior.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.