> 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/latest-news/introducing-shorter-sms-links.md). # Introducing Shorter SMS Links Announces shorter branded SMS links using a 7-character hash, saving characters and reducing message segments. Save Characters, Reduce Costs — Automatically We've made a behind-the-scenes improvement to how we generate shortened URLs in SMS messages. All branded short links now use a **7-character hash** instead of the previous 10-character format — saving you **3 characters per URL** in every message you send. ### Why this matters Those 3 characters might not sound like much, but they add up quickly when you're sending thousands of messages: * **Fewer SMS segments** — Some messages that would have needed 2 segments now fit into 1, cutting your cost in half for those sends * **More room for your message** — Extra space to add personality, urgency, or detail without bumping into the next segment * **Lower costs** — Fewer segments mean lower SMS costs, especially as carrier fees continue to rise For example, a message that was previously 162 characters (2 segments) might now be 159 characters (1 segment) thanks to the shorter URL. ### What you need to know This feature is already live on your account — there's nothing you need to turn on or configure. Every SMS link you send moving forward automatically uses the shorter format. **One small note:** If you open older campaigns in the editor, you might notice the segment count looks different than when you originally sent it. This is just a display quirk — your actual delivery data and reporting remain 100% accurate. If you have any questions, do not hesitate to [contact the Recart Support team.](/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/latest-news/introducing-shorter-sms-links.md?ask=&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.