> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shortext.ny-corp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SMS

> Send text messages by SMS under your own Sender ID, and receive delivery receipts and replies.

The SMS channel sends your messages as SMS to your contacts' phones. Your messages are signed with your **Sender ID**, the name shown as the sender on the phone (for example `ACME`), and go through the same messaging API as the other channels.

Shortext opens SMS in **Cameroon** first, then in other African countries.

## Your Sender ID

The Sender ID is the name your contacts see as the sender of your SMS. You only manage this Sender ID: Shortext takes care of the routes to the mobile operators.

A Sender ID can only send to the customers of an operator (for example MTN or Orange) once **that operator has approved it**. Shortext handles the approvals for you, operator by operator.

**1. Request your Sender ID**

From the dashboard, request a Sender ID: the name to display, what you use it for (transactional messages, marketing, one-time codes), the countries you send to and a few sample messages.

**2. Upload your documents**

Upload the documents that prove your company owns the name, including an authorization letter: download the template, sign it and upload it again.

**3. Follow the approvals**

Shortext checks your documents and submits your Sender ID to the operators. You follow the progress operator by operator, and you are notified at each step.

**4. Send**

Your Sender ID is active as soon as a first operator has approved it. A message to a contact whose operator has not approved it yet is refused, with an explicit reason.

Shortext can also give you access to a **shared Sender ID**: a test Sender ID, or a Shortext Sender ID for your announcements. On a shared announcement Sender ID, Shortext reviews the content of your messages before they are sent.

## Send an SMS

SMS uses the same messaging API as the other channels, with a `message` in the [message format](https://docs.shortext.ny-corp.io/api-reference/message-format.md). The SMS channel accepts **text only**:

```json theme={null}
{
  "type": "text",
  "content": { "text": "Your order A-1042 has left our warehouse." }
}
```

Any other type (template, interactive, media, location, contact) is refused.

## What comes back

* **Delivery receipts**: the status of each SMS is updated as the operator reports it (delivered, or not delivered) and pushed by the `message.status` [webhook](https://docs.shortext.ny-corp.io/api-reference/webhooks.md). Receipts can arrive out of order: Shortext keeps the most advanced status.
* **Replies**: when the operator passes them on, your contacts' replies come into the conversation, like on any channel: the Inbox, the agent and the `message.received` webhook. In many countries, replies to an SMS sent under a Sender ID do not reach the sender: do not rely on them.
* **Unsubscribing**: a contact who answers "Stop" is unsubscribed.

## Billing

SMS is billed **per segment**, at a price specific to the SMS channel. See [Balance and wallet movements](https://docs.shortext.ny-corp.io/api-reference/guides/balance.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.