> 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/maintenance-mode-applications/snapper/manage-snapper-uccs.md).

# Manage Snapper UCCs

Add extra UCCs to Snapper and configure UCC autodiscovery.

Use UCC configuration to connect Snapper to one or more UCCs. Snapper can use UCC autodiscovery so that one configured UCC can fill in additional UCCs automatically.

{% hint style="warning" %}
Some UCC configuration references use **UCC Host** and others use **UCC Url**. For install and settings-reference contexts, prefer **UCC Host**. When adding an extra UCC, use the label shown in the product UI and the environment-provided value.
{% endhint %}

## Add an extra UCC

1. Start Snapper.
2. Open **Settings**.
3. Open **UCC Config**.
4. Select **Add UCC**.
5. Fill in the UCC fields. Most fields are prefilled from the current UCC.
6. Enter the UCC name. This is the UCC Application ID from the UCC settings page.
7. Enter the server host or URL value supplied for the UCC.
8. Select **Save**.

## UCC configuration settings

| Setting               | Description                                                                                           |
| --------------------- | ----------------------------------------------------------------------------------------------------- |
| UCC Name              | Name of the UCC. Example: `UCC_Support`.                                                              |
| UCC Host              | FQDN or host value for the UCC server. Prefer this label for install and settings-reference contexts. |
| Secure                | Toggle between HTTP and HTTPS.                                                                        |
| Autodiscover          | Use this host to autodiscover more UCCs.                                                              |
| Dashboard hub         | URL of the Dashboard Hub.                                                                             |
| Attendant hub         | URL of the Attendant Hub.                                                                             |
| Call property service | URL of CallPropertyService for screen recording location.                                             |
| DCI skill             | Skill used for Direct Call Interceptor.                                                               |

## Advanced service defaults

The following defaults are advanced setup reference values. Treat them as configuration patterns, not customer-specific service URLs.

| Advanced setting      | Default pattern                          |
| --------------------- | ---------------------------------------- |
| Dashboard service     | `[Secure][UCC Host]/DashboardService`    |
| Attendant service     | `[Secure][UCC Host]/AttendantService`    |
| Call property service | `[Secure][UCC Host]/CallPropertyService` |

## Verify UCC configuration

1. Restart Snapper if required.
2. Open Snapper.
3. Confirm that the expected UCC is available.
4. If autodiscovery is enabled, confirm that the expected additional UCCs appear.


---

# 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/maintenance-mode-applications/snapper/manage-snapper-uccs.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.