# Teams Workspace

## Feature Overview

The Management view provides a comprehensive environment for organizing your support structure, where you can create specialized agent teams based on expertise, assign agents to these teams with defined scopes, configure intelligent routing rules across WebChat and WhatsApp channels, establish private supervisor communication channels for internal assistance, automate customer interactions with customizable greeting and reminder messages, and access detailed conversation archives for ongoing quality assurance and training purposes.

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

To properly configure your conversation routing system, follow these next steps:

1. #### [Configure SCAI bots in the Messaging Portal ](#id-1.-configure-scai-bots-in-the-messaging-portal)
2. [Configure source channels to track origin and set up routing](#id-2.-setting-up-a-new-source)
3. [Create Agents](#id-3.-create-agents)
4. [Create Teams](#id-4.-create-teams)
5. [Assign agents to teams](#id-5.-assign-agents-to-teams)

### 1. Configure SCAI bots in the Messaging Portal&#x20;

The first step to create a functional conversational loop is to register your bot configurations inside the **Messaging Portal** (it is the only time you would need to enter the portal).

To register a new bot, enter your SCAI portal and gather the different key values that characterize your bot, use the table below to find the corresponding values:

<table><thead><tr><th width="207">Variable</th><th width="357.800048828125">Description</th><th>Note</th></tr></thead><tbody><tr><td><strong>Organization Variables</strong></td><td></td><td></td></tr><tr><td>Organization name</td><td>Name of the organization in EVA</td><td></td></tr><tr><td>Organization keycloack url</td><td><p>Obtain by pressing F12 during login; looks like: </p><p>https://keycloak-americas-admin.eva.bot</p></td><td>https prefix required</td></tr><tr><td>Organization uuid</td><td>Found in the URL after logging into EVA</td><td></td></tr><tr><td><strong>Environment Variables</strong></td><td></td><td></td></tr><tr><td>Environment client ID</td><td>Found in the "Environments" section in EVA</td><td></td></tr><tr><td><p>Environment Secret </p><p>(SCAI Secret key)</p></td><td>Provided when the organization is created. Request from NTT team</td><td></td></tr><tr><td>Environment API key</td><td>Visible in the environment under the top key labeled "API key" when in the environment site</td><td></td></tr><tr><td>Environment uui</td><td>Indicated in the environment selector table as "environment key"</td><td></td></tr><tr><td>Envirnment instance</td><td>Request from NTT team<br>Example: api-americas-instance1.eva.bot</td><td>https prefix NOT required</td></tr><tr><td><strong>Bot Variables</strong></td><td></td><td></td></tr><tr><td>Bot uuid</td><td>Found within the bot's URL</td><td></td></tr><tr><td>channel uuid</td><td>Found in the bot's integrations section labeled as channel UUID</td><td></td></tr></tbody></table>

Once you have located the different values for your bot, proceed to enter the portal URL, and open the "EVA configurations" section under the "Administration" category from the left-side menu:

{% embed url="<https://americas-msg.syntphony.com/>" %}

From this section, you will be able to create a new bot register by pressing the "New configuration" button:

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

Now you can register your bot in the form that appears (only starred inputs are needed):

<figure><img src="/files/ImPKabhFGBzCI8742Gq6" alt="" width="375"><figcaption></figcaption></figure>

Now that you registered your bot on the portal, you will be able to select it as a destination for a newly created **Source** inside the Console control panel.

### 2. Setting Up a New Source

In the context of managing communication channels, it is essential to set up routing rules. Begin by setting up **Sources** to route the conversations from an origin channel to a selected bot:

* **Enter name and description.**
* **Identify Channels**: Choose the source of incoming communication, such as WebChat or WhatsApp.
* **Select the Source routing (WebChat)**: For WebChat sources, select an available bot to route the WebChat to when the users contact your WebChat.

<figure><img src="/files/HbUmkAA1FAGx9sMBLXaQ" alt="" width="224"><figcaption></figcaption></figure>

* **Select the Source routing (WhatsApp)**: For WhatsApp sources, select an available phone as the origin and a Bot for routing the users.

<figure><img src="/files/H6SfNwSuz8BW3zZLvQBU" alt="" width="223"><figcaption></figcaption></figure>

By clicking in you newly created webchat Source, you will be able to visualize the scripting code needed for creating the widget in a website. If you select instead a Whatsapp Source you will be able to check the properties from the routing.

<figure><img src="/files/TyPhnRzmwJaoZKY5Ns2o" alt="" width="375"><figcaption></figcaption></figure>

### 3. Create agents

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

When adding a new agent, a password creation email will be sent on behalf of the SCAI service to the agent, for the corresponding organization of the company account.

Once a password is created for the organization, the agent may use their credentials to enter the Live Agent Console

### 4. Create Teams

After the routing configuration, you can now establish the organizational structure that will handle the messages coming in by creating teams. To add a new team, populate the pop-up modal with the required information:

* Team's name and description
* Desired Source

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

Think of specialized teams based on expertise areas, product knowledge, places, or language capabilities.

{% hint style="warning" %}
If a source has generated any traffic, it cannot be edited to preserve tracking data integrity.
{% endhint %}

{% hint style="warning" %}
To preserve data referencing integrity, created entities (Sources, Teams, Agents) may be disabled, but never eliminated completely.
{% endhint %}

### 5.  Assign Agents to Teams

Finally, add agents to one or multiple teams based on their skills and training.&#x20;

To add a new agent, populate the pop-up modal with the required information:

* Agent's name and email.
* Define the role according to its capabilities within each team. [**See table of roles and permissions**](/user-guide/console-roles.md)
* Assign to one or more teams according to their skills and training

Every time a new agent is registered, an email is sent to the email address with a link to create its own credentials to access the SCAI service and later on to the platform.

Once an Agent has been created, you can freely assign it to different teams by editing their properties.


---

# 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://docs.conversational-ai.syntphony.com/user-guide/teams-workspace.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.