SMS from A to Z: a practical guide

SMS stands for Short Message Service: text messages sent to a mobile number through mobile networks. Recipients normally do not need to install a separate messaging app to read an ordinary SMS. Businesses use it for concise updates, reminders and marketing with the appropriate recipient permission.

This guide explains the main terms and choices before you send. The more detailed business SMS service guide explains how to choose a setup and complete your first send.

How does SMS differ from MMS and messaging apps?

An ordinary SMS contains text and can include a web link. MMS is a different message type that can carry multimedia. Messaging apps and RCS have their own device, service and availability requirements. Do not assume that a feature in one channel exists in another. MMS is not a standard Intellipush service.

For more detail than short text can provide, a message can lead to a relevant web page. A link does not make the content private: Intellipush file links are public to anyone who has the link, although they can be revoked. Sensitive information belongs in a service with appropriate access controls, not in the SMS or a publicly accessible file.

How can a business send SMS?

With browser-based sending from a computer, a person selects recipients, writes the message and chooses its timing. This suits a single update or a prepared contact list. Software does not need to be installed on each computer.

An SMS API lets another system create a message automatically when something happens. A booking system might request a reminder, or an online shop an order confirmation. Your organisation or developer defines the event and tests the integration. API access does not itself provide a ready-made connection to every system.

Recipients and sender identity are separate choices

A recipient is identified by a mobile number and the correct country code. Keep numbers current, remove duplicates and preserve opt-outs when reimporting lists. You are responsible for having an appropriate purpose and basis for contacting people.

The sender is the name or number shown to the recipient. A name can identify the business, but does not automatically support replies. Replies, keywords and receiving numbers depend on the agreed setup, account and destination. The sender guide explains the choices.

Characters, segments and cost

What looks like one text on a handset can be several SMS segments when sent. Standard GSM-7 encoding normally allows 160 characters in one segment and 153 per part when joined. Unicode-based encoding normally allows 70 in one and 67 per joined part. Some characters occupy more than one character position or code unit.

Check the final wording rather than estimating from its appearance. Recipient count, segments and destination all affect cost. Read about message length and encoding and use the pricing page for payment models and indicative examples. One SMS credit does not necessarily mean one complete message.

Created, sent and delivered are different things

A successful creation means the service has registered a message for further processing. An available delivery status describes a later technical outcome. Neither creation nor a delivery report is a read receipt.

A handset without coverage, an incorrect number or destination-specific sender rules can affect the result. Do not rely on an undocumented guarantee or resend automatically without investigating the first attempt. The troubleshooting guide distinguishes request failures from later delivery failures.