USSD BenchUSSD and SMS workbench

USSD and SMS workbench

Fit the menu before the gateway cuts it

Write your USSD menu or SMS content once in each language and let the formatter handle the rest. It automatically replaces invalid or unsupported characters that could disrupt USSD or SMS delivery, selects the appropriate encoding for each language, accurately paginates content according to network rules, and can automatically add navigation options such as Back and Next links. USSD Bench - The Complete Toolkit for USSD Menu Preparation

The numbers that matter

USSD GSM-7
182
septets per page
USSD Latin-1
160
characters per page
USSD UCS-2
80
characters per page
SMS GSM-7
160 / 153
single / part
SMS Latin-1
140 / 134
single / part
SMS UCS-2
70 / 67
single / part
USSDUSSD formatterInput, encoding, pagination, alignment, and an optional character review, for every language.
  1. 1Input
  2. 2Encoding
  3. 3Pagination
  4. 4Alignment
  5. 5Character Review
SMSSMS formatterInput, encoding, and segment counts with a preview, for every language.
  1. 1Input
  2. 2Encoding
  3. 3Segments

What 160 octets means

A MAP USSD string is specified at up to 160 octets. With the GSM 7-bit alphabet those octets pack to 182 septets. Latin-1 fits 160 characters and UCS-2 fits 80. That 182 is a packing result, not a promise that every network will accept 182 characters of menu text, so Characters per Page stays editable for each language.

One encoding per language

English usually stays in GSM-7, French or Spanish with ê or á needs Latin-1, and Arabic, Urdu, or Hindi needs UCS-2. Each language is detected on its own text, after the smart characters a phone or a Mac adds have been replaced, and you can override it.

What stays on this device

The text is kept in this browser tab for the visit. Formatting does not upload it. Ads are off. There is no account and no saved menu on a server.