> 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/text-channels/generic-dialogue-provider.md).

# Configure Generic Dialogue Provider

Configure Generic Dialogue Provider as a text-channel integration.

Configure Generic Dialogue Provider when a custom text-channel integration must send dialogues to WebAgent.

This page covers administration enablement and provider setup context. For API implementation, use the [Generic Dialogue Provider API](/developer-docs/generic-dialogue-provider.md).

## Prerequisites

* The [shared omnichannel licensing prerequisites](/channels-integrations/text-channels.md#licensing-prerequisites) are confirmed.
* Dialogue Manager is configured for text-channel handling.
* Generic Dialogue Provider is enabled for the environment.
* The integration owner has the provider identifier and attachment requirements.
* The UCC has the skills and agent assignments required for generic dialogues.
* API developers have access to the [Generic Dialogue Provider API documentation](/developer-docs/generic-dialogue-provider.md).

## Configure provider settings

| Setting              | Use                                           | Value guidance                                         |
| -------------------- | --------------------------------------------- | ------------------------------------------------------ |
| Provider identifier  | Identifies the custom provider configuration  | Use the identifier approved for the integration.       |
| Attachment settings  | Controls attachment handling for the provider | Enable only when the integration supports attachments. |
| Plugin settings      | Stores provider-level configuration           | Use values supplied for the environment.               |
| Plugin flow settings | Controls routing and dialogue flow behavior   | Use values approved for the UCC.                       |

## Configure admin enablement

1. Request Generic Dialogue Provider enablement through the current delivery/support process for the environment.
2. Confirm that the provider settings are provisioned for the target UCC.
3. Configure the provider settings through the active Admin Portal / ListsPlugin-backed configuration flow, delivery-owned configuration record, or YAML/service configuration for the environment.
4. Add the provider endpoint to the relevant ListsPlugin endpoint configuration.
5. Create or confirm the generic dialogue skill.
6. Assign the skill to the agents who handle generic dialogues.
7. Continue with the [Generic Dialogue Provider API implementation quickstart](/developer-docs/generic-dialogue-provider.md#implementation-quickstart).

## Validate Generic Dialogue Provider

1. Send a test dialogue through the custom provider integration.
2. Confirm that the dialogue appears in WebAgent.
3. Reply from WebAgent.
4. Confirm that the integration receives the reply through the API implementation.

Then validate the agent workflow in [Handle generic dialogues](/use/handle-conversations/webagent/handle-generic-dialogues.md).


---

# 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/text-channels/generic-dialogue-provider.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.