> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/getting-started-with-recart/phone-numbers/alphanumeric-sender-ids.md).

# Alphanumeric Sender IDs

Explains alphanumeric sender IDs, which show your brand name as the sender, and how registration works in different countries.

An alphanumeric sender ID shows your brand name as the sender instead of a phone number, for example **NORTHWIND**. It's the most common way to text subscribers outside the US and Canada. It isn't available for the US or Canada.

### How it works

* **One-way:** subscribers can't reply to a brand name. Replies like STOP or HELP don't reach you, so subscribers unsubscribe through the link in your messages. See [One-way vs Two-way Messaging](https://help.recart.com/getting-started-with-recart/phone-numbers/one-way-vs-two-way-messaging.md).
* **Double opt-in by code:** subscribers can't reply YES to confirm, but they can still confirm with the one-time code Recart texts them, which they enter in your popup. See [SMS Opt-in Types](https://help.recart.com/sms/subscribers-and-lists/sms-opt-in-types.md).
* **No replies:** [keyword replies](https://help.recart.com/sms/automated-flows/automated-flows-keyword-reply.md) and SMS keyword opt-ins don't work.

### Choosing your sender ID

* 3 to 11 characters.
* At least one letter. Letters and numbers only, with no special characters like @ or #.
* Use your brand name. Generic names like "Info", "SMS" or "Support" are often blocked by carriers.
* Some carriers protect well-known brand names. If yours is protected, you may need to show you're allowed to use it.

### Registration

Some countries only deliver texts from a brand name that's been registered with the carriers first. Messages from an unregistered name may be blocked or show a warning, like "Unverified" or "Likely Scam".

* **What you'll usually need:** an official business registry document showing your business name, registration number and address. Some countries also ask for ID from the person authorizing the request, or a letter of authorization if that person isn't on the registry document.
* **Countries that require registration** include Australia (about a week), Spain (up to 4 weeks) and Ireland.
* **Countries that don't** for most brand names include the UK, France, Germany and Portugal.
* Contact Support with the countries you want to text. We prepare and submit the registration with you.

If you have any questions, do not hesitate to [contact the Recart Support team.](https://help.recart.com/contact-recart-support.md) We'd be happy to help!


---

# 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://help.recart.com/getting-started-with-recart/phone-numbers/alphanumeric-sender-ids.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.
