> 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/webagent.md).

# Configure WebAgent

Configure shared WebAgent administration settings before adding CRM, CTI, or text-channel integrations.

Use these pages to configure shared WebAgent administration settings for a Dialogue Cloud Neo environment. CTI-plugin setup, CRM Service setup, text-channel provider setup, and API/provider-specific configuration belong in their own sections.

## What belongs here

This section covers shared WebAgent settings that apply before or alongside channel-specific integration work:

* Microsoft Entra ID and OpenID Connect sign-in for WebAgent
* WebAgentService connections configured per UCC
* central storage for WebAgent user settings
* WebAgent contact search behavior
* consultative skill-transfer routing through searchable Departments, contacts, or endpoints
* generic WebAgent UI behavior and outbound calling controls

{% hint style="info" %}
WebAgent uses environment-specific client IDs, issuer URLs, and service endpoints. Use the values supplied for your environment instead of copying values from another tenant or UCC.
{% endhint %}

## What belongs elsewhere

Use the integration-specific sections for settings that are not shared WebAgent administration:

* CTI plugin setup for embedding WebAgent in a CRM or desktop environment
* CRM Service configuration for CRM data lookup and screen-pop behavior
* cross-integration phone-number formatting and normalization
* text-channel provider setup for email, WebChat, WhatsApp, SMS, and generic dialogue handling
* API reference material for custom integrations
* end-user WebAgent sign-in and daily-use guidance

## WebAgent administration tasks

{% content-ref url="/pages/EUByVeL58Obm4NknvmZP" %}
[Configure WebAgent feature availability](/channels-integrations/webagent/configure-webagent-feature-availability.md)
{% endcontent-ref %}

{% content-ref url="/pages/jTnBmJydcN0RqZdT8doo" %}
[Configure WebAgent sign-in](/channels-integrations/webagent/configure-webagent-sign-in.md)
{% endcontent-ref %}

{% content-ref url="/pages/uz9Z3Gah15r867xD0ZLz" %}
[Configure WebAgent service settings](/channels-integrations/webagent/configure-webagent-service-settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/3PepbDyOIz0O42BQQvbU" %}
[WebAgent contact search](/channels-integrations/webagent/webagent-contact-search.md)
{% endcontent-ref %}

{% content-ref url="/pages/o5HlxZBeCcnGi3pB5cp6" %}
[Configure consultative skill transfer for WebAgent](/channels-integrations/webagent/configure-webagent-consultative-skill-transfer.md)
{% endcontent-ref %}

{% content-ref url="/pages/kKTO1ChSSrgeTZu5SOkE" %}
[Configure WebAgent user settings storage](/channels-integrations/webagent/configure-webagent-user-settings-storage.md)
{% endcontent-ref %}

{% content-ref url="/pages/LEoSIp7TJjdX8cwGyB4w" %}
[Configure WebAgent UI and call controls](/channels-integrations/webagent/configure-webagent-ui-and-call-controls.md)
{% endcontent-ref %}

For phone-number behavior that spans WebAgent, CRM Service, CTI plugins, and callback, see **Phone-number formatting and normalization**.

{% content-ref url="/pages/SVfbm8qnN8jL96ZNBHiv" %}
[Phone-number formatting and normalization](/channels-integrations/setting-up-integrations/phone-number-formatting-and-normalization.md)
{% endcontent-ref %}


---

# 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/webagent.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.