# Encoding setting

Messages sent via the service SMSC may consist of Latin and Cyrillic letters, as well as include special characters (Russian and Latin letters with diacritical marks, letters of the Greek and other alphabets, specific punctuation marks, as well as non-printing characters). When sending messages, it is recommended to use the settings tabled below.

| **Text** | **Data coding** | **Encoding**          | **Message length** |
| -------- | --------------- | --------------------- | ------------------ |
| Cyrillic | 0x08            | UTF-16ВE (big endian) | 70 characters      |
| Latin    | 0x00            | ASCII-8               | 160 characters     |

:warning:**IMPORTANT**

Be careful about using the following characters in SMS:

£,¥,è,é,ù,ì,ò,Ç,Ø,ø,Å,å,Δ,Φ,Γ,Λ,Ω,Π,Ψ,Σ,Θ,Ξ,Æ,æ,ß,É,¤,¡,Ä,Ö,Ñ,Ü,§ ¿,ä,ö,ñ,ü,à,

NUL,SOH,STX,ETX,EOT,ENQ,ACK,BEL,BS,TAB,VT,SO,SI,DLE,DC1,DC2,DC3,DC4,

NAK,SYN,ETB,CAN,EM,SUB,FS,GS,RS,US,\`,DEL.

**Operators may not support these characters or convert messages to Unicode due to their platform or specification, thereby increasing the number of message parts charged.**


---

# Agent Instructions: 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:

```
GET https://smsc.revicom.ltd/how-to-work-with-smsc/encoding-setting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.