Multi-language Texting Overview

You can use ThruText to send messages in multiple languages and with special characters so you can reach people in the language they are most comfortable using. This is especially helpful when your campaign includes bilingual contacts or communities that primarily communicate in another language.

You may also want to translate the ThruText interface into a language you are more comfortable reading. For example, your volunteers might prefer to see the ThruText screens in Spanish while they are sending messages.

In this guide, you will learn how to:

• Send messages in another language using ThruText.
• Translate the ThruText interface using browser tools.
• Follow best practices for multilingual texting and special characters.
• Manage message length and costs for multilingual campaigns.

TABLE OF CONTENTS

• Send Messages in Another Language
• Translate the ThruText Interface
  • Use the Google Translate Browser Extension
• Best Practices for Multilingual Texting
• Manage Message Length and Costs

Send Messages in Another Language

You can send messages in another language by using a keyboard set to that language or by copying and pasting your message from another source.

ThruText supports messages that use:

• Non-English languages (for example, Spanish, French, or Korean).
• Non-Latin character sets (for example, Arabic or Chinese).
• Special characters such as accents or punctuation used in other languages.

To send a message in another language:

1. Set your device or browser keyboard to the language you want to use, or prepare your message in another tool (such as a translation tool or word processor).
2. In ThruText, open the initial message or reply message textbox.
3. Type your message with the selected keyboard, or copy and paste the translated message into the message field.
4. Review the text carefully to confirm that it appears correctly before sending.

Automated translation tools can be helpful, but they are not always accurate. When possible, have a fluent speaker review your script before sending.

Translate the ThruText Interface

If you or your volunteers prefer to read the ThruText interface in another language, you can use browser translation tools to translate the page text.

A common tool used for translation is Google Translate’s website tool. However, because ThruText requires a login, attempting to translate a ThruText page using the website tool will result in an error. Instead, we recommend using the Google Translate browser extension, which will work even when you are logged in.

Use the Google Translate Browser Extension

To translate a ThruText page, you can also use the Google Translate browser extension. This extension works while you are logged in to ThruText.

1. In Google Chrome, install the Google Translate extension from the Chrome Web Store.
2. Open ThruText and sign in.
3. When you are on any page in the app, click the Google Translate extension icon in the Chrome toolbar.
4. Click Translate This Page.
5. Select your preferred language. The ThruText interface will be translated into that language.

This is an example of what the page would look like:

Best Practices for Multilingual Texting

Here are some other best practices when texting in multiple languages or with alternate characters:

• Confirm language preference when possible: Be careful about assuming you know which language your audience speaks. Unless you are sure they have chosen a preference for that language (for example, by checking a box on a form), consider including a short phrase that lets them know you can communicate in another language as well.
  • For example, a Spanish-language text might end with: “If you prefer English, let us know.”
  • An English-language text to someone who might prefer Spanish might include: “¿Prefieres español?”
• Be prepared to re-send messages in the preferred language: If a contact indicates they prefer another language, be ready to re-send the original message in that language, ideally using a recommended reply.
• Avoid sending the full message twice in different languages: Some organizations send the entire message in both languages, but this can make messages long and harder to read. Long messages can also affect deliverability and increase costs, especially when special characters are involved. See our guide Text Messaging Best Practices, for more details on this guidance. 
• Keep an eye on script length: It can be harder to keep scripts within a reasonable one to two SMS segments when using special character sets. Special characters can change how your message is encoded, which can increase the number of segments needed. See our guide, Text Message Encoding, for details on special characters. 
• Capture language preference when it supports your goals: Depending on your long-term goals, you may want to add a survey question or field in your data collection process that captures each contact’s language preference. This allows you to target future campaigns more effectively.

Manage Message Length and Costs

Some languages include special characters that can change the text message encoding of your message. This can result in a dramatic increase in the segments of your SMS message, leading to increased costs and lower deliverability.

MMS messages allow up to 1,600 characters and are always counted as one segment, regardless of encoding. Use MMS for longer or multilingual messages to avoid increased segment charges.

When planning your multilingual messaging strategy:

• Consider using MMS for longer scripts or when you need to include multiple languages in one message.
• Test your scripts with sample contacts to confirm how many segments they use before launching a large campaign.
• Monitor deliverability and costs over time and adjust your approach if you see higher segment counts for multilingual campaigns.