Send a single SMS in seconds

How sending a single SMS works

Open Send SMS in the dashboard, choose a sender, enter the recipient’s mobile number and type your message. As you type, the composer shows the number of characters, whether the message is GSM-7 or Unicode, and how many SMS parts it will use. Before you confirm, you see the cost of the message based on your account’s price per part.

When you send, the message is saved first and then handed to a background processor that submits it to the SMS provider. You can follow its status in your delivery reports — from queued, to submitted, to delivered or failed.

Bangladeshi numbers in any common format

You can type the number the way your customer gave it to you. Numbers such as 01712345678, +8801712345678 and 8801712345678 — and numbers written with Bangla digits — are normalised to the international format +8801XXXXXXXXX. Numbers that are not valid Bangladeshi mobile numbers are rejected before anything is charged.

Choose how your message appears

If you have an approved masking sender ID, the recipient sees your brand name as the sender. If not, you can send straight away with a non-masking sender number provided by the platform. Only approved sender IDs appear in the sender list, so you cannot accidentally send under a name that has not been reviewed.

Message length, encoding and cost

SMS is billed per part. A message written only with standard GSM-7 characters fits 160 characters in a single SMS, or 153 characters per part when it is longer. A message that contains Bangla text, emoji or other characters outside GSM-7 is sent as Unicode, which fits 70 characters in a single SMS or 67 per part.

The composer counts this for you, including characters such as € or { } that take two positions in GSM-7. If a single curly quote or emoji switches your message to Unicode, the counter tells you which characters caused it, so you can decide whether to keep them.

• Cost = number of SMS parts × your price per part (see Pricing for current rates).
• Funds are reserved when the message is queued and charged only when the provider accepts it.
• If a message fails or is rejected, it is not charged and the reservation is released.

Send a single SMS from your own software

Everything you can do in the dashboard for a single message is also available through the REST API. Your website, app or internal tools call POST /api/v1/sms with the recipient, the message and the sender, and receive a message ID straight away. Send an Idempotency-Key header with each request so that a network retry never sends the same SMS twice.

You can then check the message’s status with GET /api/v1/sms/{id}, or receive status updates automatically through a signed webhook.

Built so a message is never sent twice by mistake

Every message is stored before it is sent. If the connection to the SMS provider times out and the outcome is unclear, SMSGELY marks the message as unknown and checks with the provider instead of sending it again. Your customer does not receive a duplicate, and you are only charged once the provider confirms it accepted the message.