> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/admin/apis-and-integrations/communication-center-how-to-turn-on-your-communication-methods.md).

# How to Turn On Communication Methods

The Communication Center in Welkin allows administrators to enable various communication methods for their environment.

To turn on communication methods:

* Log into Admin
* Click on 'Communication Center' or 'Settings' in the left vertical menu
* Look for communication methods options (SMS, Email, Phone, etc.)
* Toggle each method you wish to enable
* Configure the settings for each method (phone numbers, email addresses, etc.)
* Click 'Save'

Available communication methods may include:

* SMS (Text messaging)
* Email
* Phone calls
* Push notifications
* In-app messaging

Once enabled, users in the Care portal will be able to use these communication methods to contact patients and colleagues.

**Note:** Some communication methods may require additional configuration or third-party integrations to work properly.


---

# 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://docs.welkinhealth.com/admin/apis-and-integrations/communication-center-how-to-turn-on-your-communication-methods.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.