Bulk SMS service in Bangladesh, built for every operator

GotiSMS is a bulk SMS platform focused on one thing: getting your messages onto Bangladeshi mobile phones. Every operator in the country is covered, so you never need separate accounts for different networks.

• Masking SMS shows your brand name (up to 11 letters) as the sender. Read more on masking SMS.
• Non-masking SMS comes from a regular number and is the most economical route. See non-masking SMS.
• Transactional and OTP messages can go out at any time of day, with no sending window.
• Promotional campaigns are sent between 09:00 and 21:00 Bangladesh time, after the exact text is approved by the operators.
• Bangla Unicode works out of the box, and the compose screen counts characters and SMS parts as you type.

Everything is managed from one dashboard: contacts and groups, Excel/CSV upload, templates, drafts, scheduling, campaign delivery reports, team members with roles, sign-in history and API keys.

GotiSMS uses a prepaid wallet in Taka (BDT). You top up, send, and each SMS part is deducted from your balance. The rates below are indicative starting prices; your final rate depends on traffic volume, route and operator mix.

Messages are billed per part, so a long message or a Bangla message that runs into two parts costs two SMS. Top up online with bKash, or pay by bank transfer, cash or manual Send Money and upload proof for our staff to verify. Full details are on the pricing page and in our bulk SMS price guide.

Getting started takes a few minutes and needs no paperwork for non-masking SMS.

1. Create your account at gotisms.com/register. Every account gets a default non-masking sender, so you can send straight away once you have balance.
2. Top up your wallet with bKash, or by bank transfer, cash or Send Money with proof.
3. Add your contacts one by one, or upload an Excel or CSV file and organise them into groups.
4. Compose and send, or schedule the message for later. Watch delivery results on the Campaigns page.

If you want your brand name to appear as the sender, request a masking sender ID from the dashboard. It goes through approval before you can use it. Developers can skip the dashboard and go straight to the SMS API.

SMS still reaches people that apps and email miss, including feature-phone users and customers with patchy data. Common uses include:

• E-commerce: order confirmations, delivery updates, cash-on-delivery reminders and OTP at checkout.
• Banks and MFS: transaction alerts, login codes and security notices, sent any time as transactional or OTP traffic.
• Schools, colleges and coaching centres: attendance alerts, exam results, fee reminders and closure notices to guardians.
• Hospitals and clinics: appointment reminders, report-ready notices and doctor schedules.
• Real estate: site-visit reminders, payment schedules and project updates to buyers.
• Travel and transport: booking confirmations, ticket details and schedule changes.
• Political campaigns and NGOs: awareness and outreach messages, sent within operator and regulatory rules on content and timing.

For promotional content, keep it relevant and timely; our SMS marketing tips cover what works.

Bangla text is sent as Unicode, which fits fewer characters per SMS than English:

One emoji or any non-GSM character switches the whole message to Unicode, even if the rest is English. Because billing is per part, this matters for cost. The compose screen shows a live counter of characters and parts, so you always know what you will be charged before you press send. Our guide to Bangla Unicode character limits explains the details with examples.

Marketing and operations teams usually work in the dashboard. You can send one-off messages, run campaigns to contact groups, save templates and drafts, schedule sends and read delivery reports. Invite team members with roles so each person only sees what they need, and review sign-in history for peace of mind.

Developers connect through a straightforward REST/JSON API. A single request can carry up to 1,000 recipients, an Idempotency-Key header makes retries safe, and API keys can be locked to an IP allow-list. Transactional and OTP messages go through POST /api/messages/send; promotional campaigns are submitted for approval through a separate endpoint.

Read the SMS API overview or jump straight to the API documentation.