> 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/designer/notifications-and-communications/configure-phone-names.md).

# Configure Phone Names

## Overview

When your organization uses multiple phone numbers for patient communication (e.g., different lines for SMS, different regional numbers, or department-specific numbers), you can assign custom labels to each number in the Designer. These labels appear in the Care Portal when staff select a sending line for SMS messages.

***

## Why This Matters

Without labels, phone numbers appear as raw digits in the sending line selector. Custom labels make it immediately clear which number serves which purpose – for example, "Main Clinic Line", "Behavioral Health SMS", or "East Region".

***

## How to Configure

1. In the Designer, navigate to **Phone Names** or **Configure Phone Names**.
2. Locate the phone number you want to label.
3. Enter a **Label** for the number (e.g., "Primary Care SMS").
4. Save and publish.

The label appears in the Care Portal's SMS sending line selector, alongside (or instead of) the raw phone number.

***

## Notes

* Labels are for display purposes only – they do not affect call routing, SMS delivery, or billing.
* If no label is set, the raw phone number is shown in the Care Portal.
* Phone numbers themselves are configured through your communications provider (e.g., Twilio). Labels are applied on top of the existing number configuration.

***

## Publishing

Create a draft in the Designer and publish to apply labels to the Care Portal.


---

# 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/designer/notifications-and-communications/configure-phone-names.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.