> For the complete documentation index, see [llms.txt](https://docs.miatel.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miatel.com/docs/sms/sender-id/types-of-sender-id.md).

# Types of Sender ID

## **Alphanumeric Sender ID**

Alphanumeric Sender ID is unique combinations of alphabetic characters and numbers utilized to represent your business identity. In certain regions, it's necessary to pre-register alphanumeric sender IDs with local carriers. Refer to our comprehensive [list of country-specific requirements](/docs/sms/sender-id/alphanumeric-sender-id-availability-and-registration.md) for Sender IDs for precise guidelines.

{% hint style="info" %}
Alphanumeric Sender ID can extend up to 11 characters in length. \
It accept a variety of characters, including both uppercase and lowercase ASCII letters and digits from 0 through 9. However, it cannot consist solely of numerals.
{% endhint %}

## **Short Code Sender ID**

A short code sender ID is a phone number consisting of three to six characters utilized for sending and receiving SMS messages. There are no limitations on the number of SMS messages you can dispatch per day using a short code sender ID, enabling large-scale communication with your customer base.

## **Long Code Sender ID**

A Long Code Sender ID is a standard phone number used to send and receive voice calls and SMS messages. These phone numbers are commonly referred to as "long codes" (10-digit numbers in many countries) when differentiating them from SMS short codes (5-6 digit numbers).

## Examples

| Sender     | Type         |
| ---------- | ------------ |
| Miatel     | Alphanumeric |
| 67788      | Short Code   |
| 6596997788 | Long Code    |


---

# 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.miatel.com/docs/sms/sender-id/types-of-sender-id.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.