> 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/set-up-dialogue-cloud-neo/initial-setup.md).

# Setup overview

Initial setup guide for Dialogue Cloud Neo — covers prerequisites, configuration, and telephone connection for both Connect and Unify deployment models.

Use this overview to plan a new Dialogue Cloud Neo deployment or complete the setup work associated with an existing-customer upgrade.

{% hint style="info" %}
**Dialogue Cloud Neo** is a cloud-native contact center platform built on Microsoft 365, Microsoft Teams, and Azure. It supports multiple deployment models, including **Connect** and **Unify**, which differ in how PSTN calls reach Dialogue Cloud. If you haven't confirmed your deployment model with your AnywhereNow representative, start with the decision guide before proceeding.
{% endhint %}

***

## Understand your deployment model

{% content-ref url="/pages/JEf6uXOW079nXK5TCODE" %}
[Choose a deployment model](/set-up-dialogue-cloud-neo/connect-vs-unify.md)
{% endcontent-ref %}

***

## Plan one model-aware journey

The setup work is not one universal linear checklist. Choose the customer path and deployment model first, then coordinate shared, conditional, and model-specific work. Tasks may run in parallel unless an individual guide identifies a dependency.

| Stage                 | What to do                                                                                                                                                                                                     | Where to start                                                                                                                                                |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Choose the path    | Confirm whether this is a new deployment or an existing-customer upgrade, and confirm the Connect or Unify model.                                                                                              | [Choose a deployment model](/set-up-dialogue-cloud-neo/connect-vs-unify.md)                                                                                   |
| 2. Plan               | Review the design and limits that apply to the agreed deployment.                                                                                                                                              | [Design, planning, and limits](/set-up-dialogue-cloud-neo/design-planning-limits.md)                                                                          |
| 3. Prepare            | Use the prerequisite chooser to identify applicable Microsoft Graph, Azure SQL, authentication, Secure Vault, SharePoint, Teams, and channel work. Coordinate independent tasks in parallel where appropriate. | [Prepare the environment](/set-up-dialogue-cloud-neo/prerequisites.md)                                                                                        |
| 4. Onboard or upgrade | Follow only the customer path in scope.                                                                                                                                                                        | [Onboard a new customer](/onboard-or-upgrade/onboard-new-customer.md) or [upgrade an existing customer](/onboard-or-upgrade/neo-update-existing-customers.md) |
| 5. Connect telephony  | Follow the guide for the confirmed model. Coordinate its timing with onboarding where the guide identifies a dependency.                                                                                       | [Connect model: Direct Routing](/connect-telephony/direct-routing.md) or [Unify model](/connect-telephony/unify-model.md)                                     |

{% hint style="info" %}
The overview shows the journey, not additional product requirements. Use the prerequisite and model-specific pages to decide what applies. Return here after completing a branch to choose the next outstanding task.
{% endhint %}

***

## What's next?

After the applicable setup branches are complete, choose the Build & manage destination that matches the next task:

| If you need to...                                                                  | Go to                                                                                    |
| ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Provision or manage Services and Contact Centers                                   | [Provisioning](/platform-administration/provisioning/provisioning.md)                    |
| Configure people, queues, routing, reusable assets, callflows, or outbound dialing | [Contact center configuration](https://atlas.anywhere.now/contact-center-configuration/) |
| Connect channels, providers, CRM, CTI, workforce management, or other integrations | [Channels & integrations](https://atlas.anywhere.now/channels-integrations/)             |

When the first handling path is ready, continue to [Use the apps](https://atlas.anywhere.now/use/) for the applicable user validation task.


---

# 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/set-up-dialogue-cloud-neo/initial-setup.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.