# Streamline with human team

While we strive for full automation, there are instances where Aissistant may not be able to address every customer query. This could be due to the complexity of the queries, limited access to your internal systems, or the preference to have certain sensitive tasks, like refunds, handled by human agents. In these situations, smart tags can be used to seamlessly transition tasks from Aissistant to your human team. Below are couple different methods to do so.

### Method 1. Suspend the Sub Agent

A straightforward approach to handing off tasks to the human team involves employing the post-action feature in the sub agent. For instance, the return\_or\_refund sub agent comes with contextual instructions that prompt the user to provide their order number, shipping address, reason for return, and a photo showing the product's current state. This sub agent is set up with the post-action 'suspend afterwards,' ensuring that Aissistant halts any further responses. Once the user submits the requested information, a human agent can step in to handle the return process.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FsYMM7YkKAPvwK80eV7iI%2FScreenshot%202025-04-25%20at%204.44.44%20PM.png?alt=media&#x26;token=d8e168ae-784e-4b54-9f6d-f7316343127f" alt=""><figcaption></figcaption></figure>

### Method 2. Notification/Assignment on tag

An alternative straightforward approach involves setting up a rule within your agent platform. This rule would trigger a notification or an assignment to a human agent whenever a message is sent that includes either the sys\_human\_follow\_up or sys\_human\_help tag.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FfqsaRPnXlf1f1cxKa5Fd%2FScreenshot%202024-03-08%20at%204.03.57%20PM.png?alt=media&#x26;token=3859dbfa-279e-4aa0-b760-11d86c98f66b" alt=""><figcaption></figcaption></figure>

### Method 3. Dedicated inbox

Alternatively, utilizing predefined tags like sys\_human\_help and sys\_human\_follow\_up is another effective method for alerting human agents to take action. We recommend our users to take this method.

In the following example, we'll use [FrontApp](https://www.notion.so/FrontApp-c0490fc1118b467da519c6467334b10b?pvs=21) as a sample gateway to illustrate the development of an efficient handoff procedure and the method for receiving explicit notifications from Aissistant about tasks necessitating human intervention. Other gateways may have similar mechanism.

#### Step 1: Create an empty inbox

Initially, it's essential to establish a shared, empty inbox. This inbox won't be linked to any message channels; instead, it will exclusively house messages that Aissistant has tagged as requiring follow-up by a human agent.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2Fe6y7smlfHnu7EVXHGB8s%2Fempty_inbox.png?alt=media&#x26;token=ebd296ad-225e-4ecc-b526-5e1609fce40a" alt=""><figcaption></figcaption></figure>

#### Step 2: Create a rule to move tagged conversation

Aissistant includes predefined tags such as sys\_human\_help and sys\_human\_follow\_up for immediate notifications, but you also have the flexibility to create custom tags tailored to your specific requirements. The sys\_human\_help tag is used when Aissistant lacks the information needed to respond to a query, while sys\_human\_follow\_up is employed when Aissistant recognizes a user's request but cannot execute the related task, necessitating human intervention.

In FrontApp, you have the ability to set up a rule that relocates messages to the inbox you previously established. This happens whenever a message is tagged with sys\_human\_help, sys\_human\_follow\_up, or any other custom tags you've designated as indicators for the necessity of human intervention.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FuERAHtozqaZ6LqNaQJoK%2Fhuman_help_rule.png?alt=media&#x26;token=7f024771-0575-4b93-81ee-ac74115ad99c" alt=""><figcaption></figcaption></figure>

#### Step 3: Human team follow up from the inbox

Once the previous rule is in motion, all messages flagged for human attention will be redirected to the specified inbox. The human team can then address these messages directly from that inbox. The image below illustrates a message that has been transferred to an inbox, awaiting follow-up by the human team.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2Fb1bVT2lOpkfZ6c5HWgdJ%2Fhuman_followup.png?alt=media&#x26;token=9fde861c-78af-4596-8ad5-db47a5716e3b" alt=""><figcaption></figcaption></figure>

### Method 4. Shared view

Certain agent platforms, such as Gorgias, do not feature inboxes but instead offer views. In such scenarios, we can establish a shared view for tags that may necessitate assistance from a human agent. Then, the human agent can review this shared view and proceed to engage with customers.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FVG4UN15NmBve3RJwqtIt%2Fgorgias_shared_view.png?alt=media&#x26;token=9947fc72-8323-4589-8cae-a34f44b25940" alt=""><figcaption></figcaption></figure>


---

# 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/streamline-with-human-team.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.