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

# Provisioning

Provision OnePortal services, Contact Centers, and reusable configurations for Dialogue Cloud Neo.

Use OnePortal to provision the Service and Contact Center structure and manage reusable configurations for a Dialogue Cloud Neo customer.

This section is for administrators who set up generic OnePortal provisioning. Customer-specific Dialogue Cloud Neo onboarding remains under [Initial Setup](/onboard-or-upgrade/onboard-new-customer.md).

## Provisioning model

| Item                 | Use                                                                                                                                    |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Service              | Cloud service container that hosts one or more Contact Centers for a customer.                                                         |
| Contact Center / UCC | Unified Contact Center created under a Service. It contains the customer-facing contact-center configuration, features, and endpoints. |

Every customer needs at least one Service and one Contact Center. Contact Centers on the same Service share service-level web services for the customer environment.

## Provisioning tasks

{% content-ref url="/pages/O4brD2Tne91tpaMZLFKi" %}
[Set up a Service](/platform-administration/provisioning/provisioning/setting-up-a-service.md)
{% endcontent-ref %}

{% content-ref url="/pages/PBJV1Og31zGTsAoq3Stp" %}
[Set up a Contact Center (UCC) in OnePortal](/platform-administration/provisioning/provisioning/setting-up-a-contact-center.md)
{% endcontent-ref %}

{% content-ref url="/pages/umXOwB9lcOelTVeme0bf" %}
[Manage Services](/platform-administration/provisioning/provisioning/manage-services.md)
{% endcontent-ref %}

{% content-ref url="/pages/sMXOes1uMMZLPre2awP6" %}
[View requests](/platform-administration/provisioning/provisioning/view-requests.md)
{% endcontent-ref %}

## Configuration tasks

Use [Configurations](/platform-administration/provisioning/provisioning/configurations.md) for Dialogue Studio, SBC configurations, AnywhereNow Authentication, and Secure Vault. Keep customer-device SBC technical setup in Connect telephony.

## Related setup

For the full Dialogue Cloud Neo onboarding journey, see [Onboard a new customer for Dialogue Cloud Neo](/onboard-or-upgrade/onboard-new-customer.md).

After the Service and Contact Center are provisioned, continue to [Contact center configuration](https://atlas.anywhere.now/contact-center-configuration/) to add people, queues, routing, reusable assets, and callflows.


---

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