> 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/platform-administration/provisioning/provisioning/setting-up-a-contact-center.md).

# Set up a Contact Center (UCC) in OnePortal

Create a Unified Contact Center (UCC) in OnePortal under an existing Service and connect its prepared SharePoint site.

Set up a Unified Contact Center (UCC) in OnePortal after the customer's Service exists.

{% hint style="warning" %}
Before making production provisioning changes, confirm any service-impact planning requirements through the current delivery/support process.
{% endhint %}

## Prerequisites

* A Service exists for the customer.
* The Contact Center name, display name, and main phone number are known.
* The SharePoint UCC site is prepared or ready to connect.
* The required features and integrations are known.
* The administrator understands which features can be combined for this Contact Center.

For SharePoint UCC site setup, see [Configure SharePoint UCC sites](/set-up-dialogue-cloud-neo/prerequisites/configure-sharepoint-sites.md).

## Set up the Contact Center

1. In OnePortal, select the customer.
2. Open **Contact Centers**.
3. Select **Create New**.
4. Select the region and Service deployment where the Contact Center must be created.
5. Enter the Contact Center technical name.
6. Enter the Contact Center display name.
7. Enter the main phone number in E.164 format.
8. Complete the SharePoint connection details for the UCC site.
9. Select only the features and integrations approved for this Contact Center.
10. Add endpoint details where they are part of the provisioning request.
11. Review the request.
12. Select **Save**.

Track the request until the Contact Center is provisioned.

## Contact Center fields

| Field or area               | Use                                                                                                  |
| --------------------------- | ---------------------------------------------------------------------------------------------------- |
| Region                      | Selects the datacenter region for the Service deployment.                                            |
| Service deployment          | Selects the Service under which the Contact Center is created.                                       |
| Contact Center name         | Technical Contact Center name. Use lower-case characters, numbers, and hyphens.                      |
| Contact Center display name | Friendly name shown in agent or caller-facing contexts where applicable.                             |
| Line URI                    | Main phone number for the Contact Center in E.164 format.                                            |
| SharePoint details          | Connects the Contact Center to the SharePoint UCC site.                                              |
| Features and integrations   | Enables approved capabilities such as WebAgent, CRM Service, or Text Channels at provisioning level. |
| Endpoints                   | Adds voice endpoints for the Contact Center.                                                         |

## SharePoint connection

Use the SharePoint connection method approved for the customer environment. Where certificate-based access is available, use the current certificate-based setup guidance.

For SharePoint setup details, see [Create UCC Site](/set-up-dialogue-cloud-neo/prerequisites/configure-sharepoint-sites/create-ucc-site.md).

## Feature selection

Select features with care. Some features can require additional licensing, and not every feature or integration can be combined in a single Contact Center.

Use this page only for provisioning-level feature selection. Configure the feature itself in its dedicated administration page:

* [WebAgent](/channels-integrations/webagent.md)
* [CRM Service](/channels-integrations/crm-service.md)
* [Text channels](/channels-integrations/text-channels.md)

## View request status

After saving the request, use OnePortal request status to follow provisioning progress. Wait for completion before making dependent changes.

For request search, filters, and follow-up actions, see [View requests](/platform-administration/provisioning/provisioning/view-requests.md).

For viewing and editing Contact Center details, see [View and edit Contact Centers (UCCs)](/onboard-or-upgrade/onboard-new-customer/view-all-uccs.md).

## Verification

1. Confirm that the Contact Center appears under the intended Service.
2. Confirm that the request completed successfully.
3. Confirm that the SharePoint UCC site connection is valid.
4. Confirm that approved features and integrations are shown for the Contact Center.
5. Confirm that endpoint information is correct.
6. Confirm through the current delivery/support process whether any service-impact planning is required before the Contact Center is used in production.

## Continue

After provisioning is complete, continue in the native configuration space:

{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6" %}
[Contact center configuration](https://atlas.anywhere.now/contact-center-configuration/)
{% endcontent-ref %}

Then connect the required customer entry points and external systems in Channels & integrations, and validate the user journeys in Use:

{% content-ref url="/spaces/iTek8gfJMjuAJhfqvtuU" %}
[Channels & integrations](https://atlas.anywhere.now/channels-integrations/)
{% endcontent-ref %}

{% content-ref url="/spaces/kDTnqL8OqnJFQgFg9eQ6" %}
[Use the apps](https://atlas.anywhere.now/use/)
{% 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/platform-administration/provisioning/provisioning/setting-up-a-contact-center.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.