# How to Write Better AI Instructions

*Last updated: May 14, 2026*

Good instructions make Aissist more accurate and more consistent.

Weak instructions lead to vague replies, missed steps, and unnecessary escalation.

Use this guide to write instructions that are clear, bounded, and easy to follow.

### Start with one clear objective

State the job in direct language.

Weak instruction:

> Answer customer questions about pricing.

Stronger instruction:

> Provide concise pricing guidance. Do not give exact pricing without required inputs. Escalate when pricing depends on unavailable data.

This works because it defines:

* the task
* the limit
* the escalation trigger

### Define what Aissist should not do

Aissist tries to be helpful. If limits are unclear, it may fill gaps.

Add explicit rules such as:

* do not guess
* do not estimate unavailable values
* do not invent product rules
* escalate when unsure

This is especially important for pricing, policy exceptions, and technical troubleshooting.

### Separate facts from instructions

Put facts where they belong.

Use:

* **Workspace Context** for shared business facts
* **Assets** for reference knowledge
* **Instructions** for behavior rules
* **Sub agents** for workflow-specific logic

For example, do not explain a return policy only in instructions if the policy belongs in an asset.

See [Tune Aissist Behavior](/tutorial/tune-aissist-behavior.md) for how these layers work together.

### Prefer intent over exact phrasing

Do not force one fixed sentence unless the wording must stay exact.

Weak instruction:

> Respond with: "You can order just one item."

Stronger instruction:

> Confirm that the customer can order a single item. Use natural wording that matches the conversation.

This keeps replies flexible without losing the intended message.

### Use step-based workflows

Aissist follows step-by-step logic better than long paragraphs.

Instead of:

> When customers ask about pricing, answer clearly and collect details before escalating.

Write:

#### Pricing request flow

1. Ask for quantity.
2. Ask for ZIP code.
3. Collect any other required input.
4. Escalate if exact pricing still depends on unavailable data.

This reduces ambiguity and keeps behavior consistent.

### Keep troubleshooting sequential

Give one next action at a time.

Do not send several troubleshooting steps in one message.

Use this pattern:

1. diagnose from the current message
2. give one clear next step
3. wait for the result
4. continue only if needed
5. escalate after the defined limit

This keeps the conversation grounded in the current state.

### Define escalation clearly

Do not write vague rules like:

> Escalate if necessary.

Write exact triggers instead:

* required data is missing
* the user asks for a human
* the answer depends on unavailable system access
* the workflow remains unresolved after a defined number of steps

Use **Escalation** in workspace settings to customize global handoff rules.

Use sub agents when only one workflow needs special escalation behavior.

See [Configure Workspace Settings](/tutorial/tune-aissist-behavior/configure-workspace-settings.md) for workspace fields.

### Keep instructions bounded

Avoid open-ended phrasing such as:

* if relevant
* explain thoroughly
* add more details

Use precise constraints instead:

* keep the reply under 3 sentences
* ask one question at a time
* do not expand beyond the defined explanation

Specific constraints make replies more stable.

### Put each rule in the right place

Use the field that matches the job:

* **Instruction** — universal behavior rules
* **Context** — shared business facts
* **Tasks** — what the workspace should accomplish
* **Escalation** — global handoff logic
* **Sub agent Scenario** — when a workflow should trigger
* **Sub agent Instruction** - how the workflow should work
* **Sub agent Task** — what that workflow should achieve
* **Sub agent Summary** — structured notes for the human team
* **Assets** — reference knowledge retrieved only when relevant

If one rule applies only to returns, billing, or tracking, move it into a sub agent.

### Common mistakes

Avoid these patterns:

* mixing facts, tone, and workflow steps in one long paragraph
* leaving unknowns undefined
* forcing rigid wording for every reply
* using instructions where an asset or action is needed
* writing escalation rules without clear triggers

### Best practice

Keep instructions short.

State limits directly.

Use sub agents for workflow logic and assets for knowledge.


---

# 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/how-to-write-better-ai-instructions.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.