> For the complete documentation index, see [llms.txt](https://daisychain.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daisychain.gitbook.io/help/texting/understanding-sms-segments.md).

# Understanding SMS Segments

A standard SMS message segment can have 160 "basic characters" -- which includes all [standard letters and numbers](https://en.wikipedia.org/wiki/GSM_03.38#GSM_7-bit_default_alphabet_and_extension_table_of_3GPP_TS_23.038_.2F_GSM_03.38). There are also "special characters" (like certain accented letters) might actually use up multiple characters in your segment. Emojis use a lot of characters, and change the number of characters allowed per segment in those messages to 70 instead of 160. Finally, if your message contains more than a single segment, subsequent segments have a limit of 153 characters. We know, it's a bit confusing.

**Daisychain will automatically do a few things to try to help with SMS segments:**

1. We will convert your outgoing multi-segment SMS message to an MMS message (which can contain 1600 plaintext characters) if it will save you money.
2. We will ensure that any multi-segment messages you send will be encoded in a way that most recipients with modern cell phones will receive them as a single message.​
3. We will automatically combine any incoming multi-segment messages that you might receive into a single message, for easy readability.
4. When you create an [SMS campaign](https://help.daisychain.app/campaigns/campaigns), the message preview will display the number of segments in your message.

If you want to calculate exactly how many segments a message will use (including lots of nerdy details), you can use our [text message segment checker.](https://twiliodeved.github.io/message-segment-calculator/)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://daisychain.gitbook.io/help/texting/understanding-sms-segments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.