Smart Encoding

• GSM-7: Supports 160 characters in the first segment/message (or 153 in concatenated messages);
• UCS-2 (Unicode): Required for special characters, but only supports 70 characters in the first segment/message (or 67 in concatenated messages);

How to Enable

POST /workspaces/{workspaceId}/channels/{channelId}/messages
{
  "receiver": {
    "contacts": [{ "identifierValue": "+1234567890" }]
  },
  "body": {
    "type": "text",
    "text": { "text": "“Hello”! Can’t wait for our meeting!" }
  },
  "meta": {
    "sms": {
      "smartEncoding": true
    }
  }
}

How It Works

1. Transliteration: The system replaces known Unicode characters with GSM-7 equivalents (e.g., “ → " , … → ...)
2. Compatibility Check: After transliteration, the system checks if the result is fully GSM-7 compatible
3. Outcome:
   1. Success: If all characters are now GSM-7-compatible, the transliterated text is used for segment calculation and transmission. The response is "success" in meta.extraInformation.smartEncoded.
   2. Failed: If non-GSM characters remain (e.g., emoji, CJK characters), the original message is sent as Unicode. The response is "failed" in meta.extraInformation.smartEncoded.

Example

Response

{
  "id": "msg-123",
  [...]
  "meta": {
    "extraInformation": {
      "smartEncoded": "success"
    },
    "sms": {
      "smartEncoding": true
    }
  }
}

• success: Transliteration succeeded; message sent as GSM-7;
• failed: Transliteration attempted, but message still contains Unicode; sent as Unicode/UCS-2;

Character Mapping Reference

Limitations

• Emoji: 😀, ❤️, etc. require Unicode;
• CJK characters: Chinese, Japanese, and Korean scripts;
• Arabic, Hebrew, Thai: Scripts not in GSM-7;
• Accented characters not in GSM-7: Characters like ő, ű (only basic accents like é, ü are in GSM-7);