# Improve Workflows with Sub Agents *Last updated: May 14, 2026* Sub agents help you move from broad automation to focused workflows. Use them to improve one scenario at a time until Aissist is ready for broader coverage. See [Create Sub Agents](/tutorial/create-sub-agents.md) for setup details. ### Improve one workflow at a time 1. Review live conversations and group them into repeatable scenarios. 2. Pick one high-volume, low-risk scenario first. 3. Create a sub agent with a clear scenario and concise instructions. 4. Link only the assets and actions needed for that workflow. 5. Choose the right session behavior, such as reply, handoff, or no response after the current step. 6. Test the workflow in narrow traffic and monitor live results. 7. Refine the sub agent, then repeat with the next scenario. {% hint style="info" %} Keep each sub agent narrow. One workflow per sub agent usually works best. {% endhint %} ### Best practices Use sub agents well by following these rules: * move scenario-specific rules out of workspace instructions * link only relevant assets and actions * use handoff when the workflow needs human review or system access * expand gradually after one workflow performs reliably ### Examples These examples show how teams use sub agents to improve accuracy, reduce conflicts, and hand work to humans when needed.
Example: Add contextual instructions for one scenario CityRelay, a property rental business, often receives questions about early check-ins and late check-outs. To handle this, they created a `check_in/checkout_out` sub agent with: * contextual instructions for the check-in and checkout policy * an action to check availability That let Aissist answer these questions more accurately and efficiently.
Example: Resolve conflicting guidance Open Goaaal sells soccer goals and often receives requests for installation manuals. At first, Aissist replied with the wrong behavior. It said it would send a PDF, even though the correct workflow was to share a Google Drive link for the exact product. The problem came from a conflicting workspace instruction that overrode the asset guidance. The fix was: * remove the conflicting global instruction * create an `installation_manual` sub agent * move the correct logic into that sub agent
After that change, Aissist returned the correct product-specific manual link instead. This pattern works well when one workflow needs precise logic that should not affect every conversation.
Example: Hand off to the human team Open Goaaal also needed a safe return handoff flow. Return requests required a return authorization in an internal system that Aissist could not access directly. To handle that, the team created a `return_or_refund` sub agent that: * asks for order number * asks for shipping address * asks for the reason for return * asks for a photo of the current product condition * tell customer the case has been escalated to a special team after the information is collected * stops responding Once the user submits that information, the human team takes over.
For more on handoff design, see [Streamline with Human Team](/tutorial/streamline-with-human-team.md).
### Best practice Start with one repeatable workflow. Test it, review real conversations, and expand only after the workflow is reliable. --- # 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/improve-workflows-with-sub-agents.md?ask= ``` 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.