> 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/onboard-or-upgrade/onboard-new-customer/view-all-uccs.md).
# View and edit Contact Centers (UCCs)
View, edit, and manage Unified Contact Centers (UCCs) in OnePortal — endpoints configuration, SharePoint credentials, connection-type changes, and UCC deletion.
Use OnePortal to find, inspect, and edit the Unified Contact Centers (UCCs) delivered to your customer. From this view you can add and edit endpoints, replace SharePoint credentials, change connection types, and delete UCCs.
This page applies to **both** the Unify and Connect deployment models. The Endpoints Configuration procedure below is the procedure referenced from **Step 6** of [Onboard a new customer for Dialogue Cloud Neo](/onboard-or-upgrade/onboard-new-customer.md) for Connect customers; Unify customers can also use it for additional endpoint management after initial onboarding.
{% hint style="warning" %}
**Service restart required.** A service restart — which interrupts every UCC on that service — is required after most edit actions on this page. Plan endpoint and credential changes during a maintenance window.
{% endhint %}
***
## Prerequisites
* A **Service** already exists in OnePortal (created via Step 3 of the new customer onboarding flow).
* A **UCC** has been provisioned on that service.
* The signed-in OnePortal user has **partner-admin** or **customer-admin** rights on the customer tenant.
* For endpoint changes that introduce new phone numbers: phone numbers are already available in the customer's Teams tenant (Calling Plan, Operator Connect, or Direct Routing). See the prerequisites in [Onboard a new customer](/onboard-or-upgrade/onboard-new-customer.md#prerequisites).
***
## View and search UCCs
### Search for and select a UCC
1. Select your customer name.
2. Select **Contact Centers**.
3. (Optional) Filter on part of the UCC name.
4. Select the desired UCC.
The configuration details for that UCC open in the expanded panel on the right.
### Contact Center Details panel
The panel has four panes:
| Pane | Contents |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Identity and Actions | UCC name and status (online / offline) and two drop-down menus for UCC-specific settings (not service-level). |
| Contact Center Information | Snapshot of the global configuration metrics and standards for this UCC. |
| Active Features | Overview of activated features and integrations. **Add Feature** opens a menu to add more. |
| Endpoints | List of configured PSTN endpoints with Display Name and LineURI (phone number). Add, edit, and delete endpoints here. |
## After the UCC exists
After the Service and UCC are visible in OnePortal, continue with the Administration pages that turn the provisioned contact center into a working route for callers or messages.
1. Review the contact-center settings and endpoint assumptions.
{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/GPmS80qb4nnck1OqlN4w" %}
[Service and Contact Center Settings](/contact-center-configuration/service-and-contact-center-settings.md)
{% endcontent-ref %}
2. Configure people, skills, queues, and routing rules.
{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/qws5JKHo8p4uIh5RxAd7" %}
[Configure skills and routing criteria](/contact-center-configuration/queues/skills-and-routing-criteria.md)
{% endcontent-ref %}
{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/pKLzVJPFD6Ky9I5oRtyR" %}
[Configure queue routing rules](/contact-center-configuration/queues/configure-queue-routing-rules.md)
{% endcontent-ref %}
3. Choose the first branch to validate: voice routing, a Dialogue Studio callflow, or a WebAgent/text-channel path.
{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/ZO573ktrsGDDLCZRkVy3" %}
[Route Calls and Queue Messages](/contact-center-configuration/building-your-callflow/route-calls-and-queue-messages.md)
{% endcontent-ref %}
{% content-ref url="/spaces/iTek8gfJMjuAJhfqvtuU" %}
[Channels & integrations](https://atlas.anywhere.now/channels-integrations/)
{% endcontent-ref %}
Use this handoff before changing production endpoints or routing. Most UCC endpoint edits require a Service restart, so plan the first validation path and rollback owner before production traffic depends on the route.
***
## Action buttons
Each UCC exposes three action buttons: **Change**, **Replace**, and **Delete**.
Change
Use **Change** to switch the SharePoint connection type:
* **SharePoint Connection Type** — change from Client ID + Client Secret to AppOnly + Certificate, or the other way around.
A dialog appears in which you enter the details for the alternative connection method.
{% hint style="info" %}
Where the dialog asks for the **Site Collection URL**, provide the **UCC Site URL** — that is the value OnePortal checks.
{% endhint %}
#### From Client ID + Client Secret to AppOnly + Certificate (Dialogue Cloud Enterprise App)
{% hint style="warning" %}
**Service restart required** after this action. Plan carefully.
{% endhint %}
Replace
{% hint style="info" %}
A service restart is **not** required when you replace an existing Client ID or Client Secret if the current secret has not yet expired. A service restart **is** required when you replace an expired Client Secret, because the refreshed authentication token will have expired as well.
{% endhint %}
**Replace** has three sub-actions, the last of which has two further sub-items:
| Sub-action | What it changes |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| SharePoint Credentials | Submit a new Client ID and/or Client Secret for this single UCC. |
| SharePoint Site URL | Provide a new site URL. |
| Connection string | Provide a new SQL CDR Database connection string for either the **Universal Time Line Service** or the **Call Property Service**. |
{% hint style="info" %}
The connection string for the **Core UCC service** is changed through the SharePoint Ucc.Creator interface, not here.
{% endhint %}
{% hint style="info" %}
When you update the **Call Property Service** connection string, the value `Authentication="Active Directory Password"` may need to be entered without quotes — that is, `Authentication=Active Directory Password`.
{% endhint %}
{% hint style="warning" %}
**Service restart required** after these actions. Plan carefully.
{% endhint %}
Delete
**Delete** removes the entire UCC after a confirmation prompt.
{% hint style="warning" %}
**Service restart required** after this action. Plan carefully.
{% endhint %}
***
## Edit a UCC
You can update various aspects of a UCC — display name, phone number, additional endpoints, additional features — or delete the UCC.
{% hint style="warning" %}
**Service restart required** after editing one or more UCC **endpoints**, so the endpoint is properly registered in Dialogue Cloud and on the PSTN. Specifically when you:
* Add a phone number or display name to an existing endpoint.
* Change a phone number or display name on an existing endpoint.
* Add a new endpoint (with or without a phone number or display name).
* Delete an additional endpoint.
{% endhint %}
### Add features
In the **Active Features** pane, the **Add Features** button lets you add features to this UCC.
When **WebAgent for Omnichannel Communication** is selected (may require additional licenses), you can also select a Dialogue Manager Integration.
***
## Endpoints configuration
The Endpoints Configuration table below applies to both the Unify and Connect models. On the Connect model, this is the procedure referenced from **Step 6** of [Onboard a new customer](/onboard-or-upgrade/onboard-new-customer.md) — the endpoint LineURI you assign here is the public number presented and routed via the customer SBC + Direct Routing setup.
{% hint style="warning" %}
**Service restart required** after editing one or more UCC **endpoints**, so the endpoint is properly registered in Dialogue Cloud and on the PSTN. Specifically when you:
* Add a phone number or display name to an existing endpoint.
* Change a phone number or display name on an existing endpoint.
* Add a new endpoint (with or without a phone number or display name).
* Delete an additional endpoint.
{% endhint %}
### Add an additional endpoint
To add an additional endpoint, provide:
| Field | Description | Format / constraints |
| -------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| **Name** | Technical suffix appended to the main endpoint name. | At least 4 characters. Alphanumeric and hyphens only. See note below for the resulting full technical name. |
| **Display Name** | Human-readable label shown in OnePortal and (where applicable) in Teams. | Free text; keep concise. |
| **LineURI** (phone number) | The endpoint phone number. | E.164 format. For example, `+31123456789`. |
{% hint style="info" %}
**Resulting full technical name.** The endpoint **Name** is appended to the main endpoint technical name. For example:
* If the **main** endpoint technical name is `ucc-tech-6y5tr`
* And the **additional** endpoint **Name** is `vip-be-support`
* The full technical name of the additional endpoint becomes `ucc-tech-6y5tr_vip-be-support`.
{% endhint %}
After entering the values, select **Create endpoint**. The endpoint is created on this UCC; progress is shown in the status menu.
{% hint style="info" %}
**Bulk endpoint creation is not supported in OnePortal.** It was supported in the legacy Partner Portal but is not yet re-implemented in OnePortal. Plan multi-endpoint creation explicitly, one endpoint at a time.
{% endhint %}
### Edit an additional endpoint
After an additional endpoint is created, you can:
* **Edit** the **Display Name**.
* **Edit** the **LineURI**.
* **Delete** the additional endpoint.
***
## Delete a UCC
At the top right of the screen you can also choose to delete the UCC.
{% hint style="danger" %}
**Production impact.** The UCC is in production. Confirm with the customer before you proceed. Deletion cannot be undone from this surface.
{% endhint %}
{% hint style="warning" %}
**Service restart required** after deleting a UCC from a service, so the endpoint(s) are properly unregistered from Dialogue Cloud and the PSTN.
{% endhint %}
---
# 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/onboard-or-upgrade/onboard-new-customer/view-all-uccs.md?ask=&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.