> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/channels-integrations/dialogue-ai-assist/configure-dialogue-ai-assist-profiles.md).

# Configure Dialogue AI Assist profiles

Configure Deepdesk profiles, assistant assignments, and profile matching rules for Dialogue AI Assist.

Use Deepdesk profiles to assign assistants to conversations. Profiles combine assistant assignments with profile configuration rules that determine when a profile is assigned to a conversation.

## Before you start

Complete the relevant setup before assigning a profile:

* [Configure Dialogue AI Assist](/channels-integrations/dialogue-ai-assist/configure-dialogue-ai-assist.md)
* [Manage Dialogue AI Assist users](/channels-integrations/dialogue-ai-assist/manage-dialogue-ai-assist-users.md)
* [Manage Dialogue AI Assist assistants](/channels-integrations/dialogue-ai-assist/manage-dialogue-ai-assist-assistants.md)
* [Manage Dialogue AI Assist Knowledge Bases](/channels-integrations/dialogue-ai-assist/manage-dialogue-ai-assist-knowledge-bases.md)
* For voice flows, [integrate Dialogue AI Assist with Dialogue Studio](/channels-integrations/dialogue-studio-integrations/integrate-dialogue-ai-assist-with-dialogue-studio.md).

Assistant assignment visibility is available under **Triggers** on an assistant. Use **Triggers** to review where assistants are used and how they are made available:

* **Event Based Assistant Assignments**
* **On-Demand Assistant Assignments**
* **Linked Assistants**

## Open profile settings

1. In the Deepdesk admin portal, go to **Admin Settings** > **Profile**.
2. Open the profile that you want to configure.
3. Review the profile heading and profile name.

Profile settings contain:

* **Knowledge assistant**
* **Event Based Assistants**
* **On-Demand Assistants**
* **Profile configuration**
* **Recommendation Engine**
* **Delete Profile**

## Understand Dialogue Studio context and profile matching

For voice conversations that use Dialogue Studio Dialogue AI Assist nodes, the node sends key-value tags as conversation context. **Profile configuration** evaluates those received values with JSON Logic and assigns the profile when the rule matches.

Configure the tags sent by Dialogue Studio in the Dialogue Studio Dialogue AI Assist node setup. Configure the matching JSON Logic rule in the Deepdesk profile. The profile page evaluates incoming values and does not configure the tags sent by Dialogue Studio.

## Configure the knowledge assistant

Use **Knowledge assistant** in profile settings when a profile needs a dedicated knowledge-backed assistant. The dropdown placeholder is **Select a knowledge assistant**.

Configure the underlying Knowledge Base from **Admin Settings** > **Knowledge Base**, then attach it to the relevant assistant from **Behavior** > **Knowledge** where available. For Knowledge Base guidance, see [Manage Dialogue AI Assist Knowledge Bases](/channels-integrations/dialogue-ai-assist/manage-dialogue-ai-assist-knowledge-bases.md).

## Configure event-based assistants

**Event Based Assistants** rows combine an assistant selection with an event selection. Assistants can be assigned to these events:

| Event                        | Trigger                                                                                        |
| ---------------------------- | ---------------------------------------------------------------------------------------------- |
| **Conversation accepted**    | Triggered when an agent accepts a conversation.                                                |
| **Conversation new message** | Triggered upon receiving a new message from either the customer or the agent.                  |
| **Conversation ended**       | Triggered when the conversation ends, either through closure, transfer, or customer departure. |

Use event-based assignments when the assistant should run automatically at a specific moment in the conversation. For example, assign a summarizing assistant to **Conversation ended** when the assistant should prepare a summary after the interaction ends.

Enable **Include transcript** in the assistant **Settings** when the assistant requires the conversation transcript. Your AnywhereNow representative may provide recommended assistant setups for the organization.

## Configure on-demand assistants

**On-Demand Assistants** are available for agents to start when needed. The table contains **Assistant Name**, **Button Label**, and **Pinned**.

1. Select **Add Assistant**.
2. Choose an assistant.
3. Optionally enter **Button Label**.
4. Configure **Pinned**.
5. Select **Add**.

On-demand assignments include:

| Field            | Description                                                                          |
| ---------------- | ------------------------------------------------------------------------------------ |
| **Pinned**       | Keeps the assistant prominently available to the agent when supported by the client. |
| **Button Label** | Defines the label shown to the agent for the on-demand assistant.                    |

## Configure profile matching

**Profile configuration** specifies the rules that trigger the assignment of a profile to a conversation. Use the JSON Logic editor to configure the rule. The editor includes **View**, **Edit**, **JSON**, and **Save** controls.

For example, if a Dialogue Studio Dialogue AI Assist node sends a tag with key `profile` and value `support`, the profile can match that value with this JSON Logic rule:

```json
{
  "==": [
    {
      "var": "profile"
    },
    "support"
  ]
}
```

{% hint style="warning" %}
Profiles must be mutually exclusive. Overlapping rules across profiles can cause unpredictable behavior. Only users with deployment permissions can edit this field.
{% endhint %}

When the profile configuration is published, the page shows **This profile configuration is published.**

## Review the recommendation engine setting

**Recommendation Engine** shows whether recommendation engine functionality is enabled for the profile. Contact support to enable or disable it.

## Delete a profile

**Delete Profile** permanently removes all settings associated with the profile.

{% hint style="danger" %}
Deleting a profile is permanent. Before deleting a profile, confirm that its knowledge assistant, event-based assistants, on-demand assistants, and profile configuration rules are no longer required.
{% endhint %}

## Validate and continue

1. Confirm the intended assistants and Knowledge Base are assigned to the profile.
2. Confirm the profile configuration is published.
3. Run a controlled conversation through the configured WebAgent scenario and confirm that the expected profile and assistants are presented.

After validation, continue to [Use Dialogue AI Assist](/use/handle-conversations/dialogue-ai-assist.md) for agent tasks.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/channels-integrations/dialogue-ai-assist/configure-dialogue-ai-assist-profiles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.