> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/suptask-ai/use-cases-library.md).

# Use Cases Library

Ready-made Assistant setups you can copy into your own Inbox

***

## Assistant use case library

The Assistant library is a collection of ready-made setups for [AI Assistants](https://claude.ai/suptask-ai/ai-assistants.md) - one for each request type that teams handle over and over again. Every entry tells you which connectors to switch on, what to write in the Assistant's instructions, and when it should run.

Copy a template into your Inbox, adjust the names to match your organization, and test it before you deploy. You don't need to write anything from scratch.

{% hint style="warning" %}
Agentic AI Workflows with the AI Assistants are a part of the Custom plan. Contact Suptask to get started.
{% endhint %}

***

### What's in a template

Every use case in the library follows the same four parts, in the same order you meet them in the Assistant editor.

| Part                     | What it covers                                                                                                                            |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Connectors and tools** | The systems the Assistant needs, the individual tools to enable, and whether each one should run automatically or ask for approval first. |
| **Base instructions**    | The Assistant's role, scope and boundaries. Copy this into the **Base Instructions** field.                                               |
| **Workflow tasks**       | The steps it takes, one per task. Only needed for multi-step use cases - many Assistants work well with base instructions alone.          |
| **Activation**           | Whether the Assistant runs on every new ticket, only on specific Forms, or when an agent mentions `@Suptask`.                             |

Templates are a starting point, not a finished configuration. Your group names, Forms and knowledge sources are your own, so read through the instructions and replace anything in `[square brackets]` before you deploy.

***

### Use a template

1. In the Web app, open **Intelligence** and select the Inbox the Assistant should work in.
2. Under **Agentic AI**, open **Connectors** and connect the systems the template needs.
3. Open **Assistants** and add a new Assistant.
4. On **Connectors**, enable the tools listed in the template and set each one to **Off**, **Ask** or **Auto**.
5. On **Tasks & Personality**, paste the base instructions and add the workflow tasks.
6. On **Activation**, choose the triggers from the template.
7. On **Review & Deploy**, check the summary and deploy.

An Assistant stays **Inactive** until you deploy it, so you can build and review the whole setup before it touches a ticket.

***

### Before you deploy

Run through this list for any template you copy:

* Replace every `[placeholder]` with your own group, Form, system or team names.
* Start read-only. Set tools that change data to **Ask** until you trust the results.
* Limit the Assistant to the Forms it was written for, so it doesn't run on unrelated tickets.
* Check that the knowledge it answers from is current - an Assistant repeats whatever your documents say.
* Test on a real ticket in a test Inbox before you point it at your live queue.

***

### Related articles

{% content-ref url="/pages/RHp6timCpwHDqb9OkFNd" %}
[Write instructions for your Assistant](/suptask-ai/use-cases-library/write-instructions-for-your-assistant.md)
{% endcontent-ref %}

{% content-ref url="/pages/EMXzCysY1oz2JPFXI8gH" %}
[AI Assistants](/suptask-ai/ai-assistants.md)
{% endcontent-ref %}