> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/sms/getting-started/quick-start-guide-sms.md).

# Quick start guide (SMS)

{% embed url="<https://www.youtube.com/watch?v=39wxKQZpndk>" %}

{% embed url="<https://www.youtube.com/watch?v=an7lV4WtZ14>" %}

To get started with sending SMS messages, follow the below steps:\
\
**Step 1:** [**Create**](https://app.clickatell.com/sign-up/create-account?intent_type=SMS&_gl=1*1ubje1z*_gcl_au*MjkxNzc2NDAyLjE3Nzg0OTUwOTkuMTk5MTA0NzgyOS4xNzgyNzE2NjA4LjE3ODI3MTY2MDc.*_ga*MTYyNjkzMjMwLjE3Mzg5MjA3NDI.*_ga_VQEX92MWS1*czE3ODI5MTAwMzEkbzMzMSRnMSR0MTc4MjkxMjI2MSRqNjAkbDAkaDA.&_ga=2.21677243.128726484.1782716461-162693230.1738920742) **and access your account.**&#x20;

Register for a free Clickatell account, verify it, and log in to access your workspace.&#x20;

**Step 2:** **Activate SMS and configure your setup.**

Activate SMS, create a new setup, and configure your messaging type and sender details.&#x20;

<figure><img src="https://3260069161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4IuWpxq11GnZijbn0y1v%2Fuploads%2Fb8HiN6W9HUPHHLBRubLG%2Fimage.png?alt=media&amp;token=195eb832-db08-4a03-b83b-ab9be12c2dce" alt=""><figcaption></figcaption></figure>

**Step 3: Generate your API key.**

Create an SMS API integration and generate your API key for authentication.&#x20;

**Step 4: Test your integration (Sandbox).**

Add test numbers, send test messages, and validate responses before going live.&#x20;

**Step 5: Send and manage SMS messages.**

Send SMS messages via API or your workspace and choose between priority or standard delivery.&#x20;

{% hint style="info" %}
Message length depends on encoding (160 characters standard, \~70 for Unicode).

&#x20;Ensure compliance with the [regulations](https://www.clickatell.com/sms-country-regulations/) of the country that you are sending SMS messages to.&#x20;
{% endhint %}

{% hint style="info" %}
If you plan on using a **US Long Number**, please refer to the [10DLC](/sms/10dlc-regulations-us/what-is-10dlc.md) section of this guide.
{% endhint %}

{% hint style="info" %}
Helpful Resources:\
[SMS API Explained](https://www.clickatell.com/products/sms-platform/#step-1)

[SMS FAQs](https://www.clickatell.com/help-center/sms/general-sms/)

[Developer Documentation](https://help.clickatell.com/developers-documentation)

[SMS Pricing](https://www.clickatell.com/pricing-and-coverage/message-pricing/)

{% endhint %}


---

# 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.clickatell.com/sms/getting-started/quick-start-guide-sms.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.
