> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/getting-started.md).

# Getting Started

## Overview

We have designed Contact Center to be a simple as possible to setup. 

* [ ] Enable the Contact Center [Service](/definitions/contact-center-service.md) for your organization (creating a New [Organization](/definitions/contact-center-organization.md))
* [ ] Grant Contact Center service permissions to interact with your Microsoft Teams tenant
* [ ] Configure your Organization's Contact Center settings

{% hint style="info" %}
A free 30 day full featured trial is included in the initial setup.
{% endhint %}

{% embed url="<https://youtu.be/IOTOEJhi2Kg>" %}

## Enabling the Service for Your Organization

&#x20;Browse to <https://cc.landis.cloud/account/organization-signup>

Select Sign in with Microsoft button. We recommend using a Microsoft 365 Global Administrator account.

| Field                     | Description                                                                                                                     |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Organization Name         | This will be the short name for your organization and cannot be changed. It cannot include spaces.                              |
| Organization Display Name | This will be a longer and more descriptive name for your organization.                                                          |
| Admin Email               | This will be populated automatically.                                                                                           |
| Region                    | Choose your preferred region for hosting your contact center organization. This decision is final and cannot be modified later. |

Click Submit.

{% hint style="info" %}
Creating a new service for your organization should just take a few seconds.
{% endhint %}

When the service for your organization is created, sign into the service portal to continue.&#x20;

## Granting Permissions to Microsoft 365 Services

### Grant Teams/Azure Permissions

To grant contact center the ability to interact with the organization's Teams and Azure tenant, sign in to the portal and navigate to Administration | Settings.  Select the first Grant Permission button.  The requested permissions will be listed when granting consent. Other permissions are options and may be required depending on the feature. See [Integration Permissions](/appendix/integration-permissions.md)

{% hint style="info" %}
Verify that you are signed into the correct Microsoft 365 tenant before granting permissions.
{% endhint %}

## Configure for Your Organization

Your are now ready to configure some contact center specific settings. See [Setup](/setup.md)

{% hint style="info" %}
To speed up getting started, your contact center will have preconfigured wrap-up questions, wall boards, user roles and so on.&#x20;
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cc.docs.landis.cloud/getting-started.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 `build a script that syncs our docs to a CMS` 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.