Hello! 👋
Message Sent ✓
Delivered ✓✓
200+ Countries
Bulk SMS 📨
API Ready
SMS
Connecting worldwide
Login Sign Up Free
Chat on WhatsApp Send us an Email

FAQs

BulkSMSOnline.com Help Center

You have SMS queries doubts in mind, no worries!! We are here to clear them.

From contact upload to API configuration, we've provided the answers below to address all of your SMS queries. Therefore, explore our frequently asked questions about our BulkSMSOnline platform, integrations and SMS queries below.

Furthermore, if you're interested in more deep guides and tutorials regarding SMS queries, check out our Knowledgebase.

SMS Basics

General questions

SMS stands for Short Message Service. It is a highly effective communication channel where text messages are shared directly from person to person through a mobile network, ensuring immediate reach and high visibility.

An SMS gateway is a robust integration that enables a computer or software system to send and receive SMS messages. It seamlessly routes these messages into global mobile networks, ensuring fast and reliable delivery to handsets worldwide.

Bulk SMS marketing is the strategic use of text messaging to send promotional campaigns, alerts, and updates to a large group of opted-in customers simultaneously. It is one of the most direct marketing channels for reaching customers quickly on their mobile phones.

Yes, we support Unicode SMS. Unicode allows you to send messages in Arabic, Chinese, Cyrillic, Hindi, and many other non-English languages, as well as special symbols and emojis. When a message contains Unicode characters, it is usually encoded as UCS-2, which reduces the number of characters available per SMS part compared with standard GSM text.

We support long SMS messages up to a maximum of 5 SMS parts. A standard GSM message can contain up to 160 characters in one part, while longer GSM messages are split into parts of around 153 characters each. Unicode messages usually allow up to 70 characters in one part, and around 67 characters per part when split. This means the practical maximum is about 765 GSM characters or 335 Unicode characters across 5 parts.

GSM-7 is the standard character encoding used for most English SMS messages. It supports common Latin letters, numbers, and selected symbols. When your message only uses GSM-7 characters, you get the highest SMS character limit. If you include unsupported characters, the message may automatically switch to Unicode encoding.

A Sender ID is the name or number that appears as the sender of the SMS message. It can be an alphanumeric brand name, such as your company name, or a numeric sender depending on the destination country and local operator rules. Sender ID availability and registration requirements may vary by country.

An SMS delivery report, also called a DLR, shows the delivery status of a message after it is submitted to the mobile network. Common statuses include delivered, pending, failed, rejected, or expired. Delivery reports help you track campaign performance and confirm whether messages reached the recipient’s mobile operator or handset.

A concatenated SMS is a long text message that is automatically split into multiple SMS parts and then displayed as one message on the recipient’s phone. Each part is billed as a separate SMS because every part is sent through the mobile network separately.

Yes. For marketing or promotional SMS, you should only send messages to customers who have agreed to receive them. It is also recommended to provide a clear opt-out or unsubscribe option where required. Consent-based messaging improves trust, reduces complaints, and helps protect your sender reputation.

Account & Billing

Payments and account validity

Yes. New accounts come with €1 in testing funds so you can explore the platform, test the sending process, review delivery behavior, and understand how the system works before adding your own balance. During the trial stage, SMS content may be automatically overwritten with our demo content for testing and abuse-prevention purposes. Once you add funds to your account, you can send your own approved SMS content normally.

Trial accounts are mainly for testing the platform flow, delivery process, dashboard, and account features. For this reason, the SMS body may be replaced with our demo content while using the free testing funds. After you add funds to your account, you can use your own SMS text, subject to normal content, compliance, and route acceptance rules.

No. Your BulkSMSOnline account does not expire, so you can keep using it whenever you need to send SMS messages. This gives you flexibility if you send campaigns regularly, seasonally, or only when required. Your account remains available without forcing you into a monthly subscription.

No. We keep the pricing simple and transparent. There are no hidden charges, no setup fees, and no required monthly subscription. You add funds to your account and use them to send SMS messages based on the selected route and message type.

You can add funds from your account billing area using the available payment methods. We support convenient options such as PayPal, Visa, Mastercard, and selected cryptocurrencies including Bitcoin, USDT, and Ethereum. After payment is completed and confirmed, the balance is added to your account so you can start sending SMS messages.

Yes. BulkSMSOnline works on a prepaid pay-as-you-go model. You add balance to your account, then use that balance when sending SMS messages. This is useful for businesses that do not want fixed monthly commitments and prefer to control their SMS spending based on actual usage.

SMS billing is based on message submission and routing through mobile network infrastructure, not only on the final handset result. Mobile operators and upstream providers may charge for the delivery attempt even if the recipient phone is switched off, outside coverage, roaming, blocked, or unable to receive the message. Delivery reports help show the final status, such as delivered, failed, pending, rejected, or expired.

You can check your available balance directly from your account dashboard. Your balance helps you monitor spending, plan campaigns, and top up before sending larger SMS batches. You can also review message history and delivery information to understand how your funds are being used.

Yes. Your account area allows you to review your payment activity, top-ups, and SMS usage history. This helps you track previous payments, monitor campaign costs, and keep records for internal accounting or business reporting.

Yes. You can add more funds whenever you need to send a larger campaign or maintain enough balance for regular SMS traffic. For high-volume sending, it is recommended to top up your account before launching the campaign so messages can be processed smoothly without interruption due to low balance.

Coverage & Support

Reach, help and data safety

BulkSMSOnline provides global SMS coverage, allowing you to reach customers in more than 200 countries through over 1,100 mobile network operators worldwide. This makes it suitable for local campaigns, international alerts, OTP messages, customer notifications, and global business communication from one platform.

Yes, you can send SMS to a wide range of international destinations. Coverage is available for most countries and major mobile networks worldwide. In some destinations, delivery behavior may depend on local operator rules, sender ID restrictions, message content policies, or country-specific telecom regulations.

Our support team is available to help with account setup, campaign sending, billing questions, delivery checks, and API integration guidance. You can contact us through the available support channels such as live chat, email, or phone support, depending on your request and account needs.

Yes. If you want to connect your website, CRM, application, or internal system to BulkSMSOnline, our support team can guide you with API usage, request formatting, delivery report handling, and common integration questions. Developers can use our API options to automate SMS sending and manage messaging workflows more efficiently.

Yes. If you notice delivery issues, our support team can help review the message status, destination number format, route behavior, delivery report, and possible operator-side reasons. Some delivery failures may happen because the recipient phone is offline, the number is invalid, the destination operator blocks certain content, or local telecom rules restrict specific sender IDs or message types.

Yes. We take account security and data protection seriously. Your personal information, uploaded contacts, and group lists are handled with strict security controls to help protect your data from unauthorized access. We also encourage customers to upload only permission-based contact lists and manage their SMS data responsibly.

Yes. You can upload and manage your contact lists inside your account, organize contacts into groups, and use them for SMS campaigns. For best results, make sure your numbers are formatted correctly with the country code and that your list contains only contacts who have agreed to receive your messages.

Sending & Platform

Campaigns, replies and uploads

No. You do not need to install any desktop software. BulkSMSOnline is a browser-based platform, so you can log in from your web browser, upload contacts, create campaigns, manage groups, send messages, and review delivery reports directly from your account. You can also use our Web SMS Platform when you want a simple online dashboard for sending SMS without technical setup.

There is no fixed daily sending limit from our platform side for normal approved usage. You can send small campaigns or high-volume SMS batches based on your account balance, route availability, destination rules, and message compliance. For very large campaigns, we recommend preparing your contact list, checking your balance, and sending through the correct route to avoid delays or rejected messages.

Yes. Our platform supports standard GSM messages, long SMS messages, and Unicode SMS for non-English languages. A normal GSM SMS allows up to 160 characters in one part, while Unicode messages usually allow up to 70 characters in one part. Longer messages are split into multiple SMS parts and reassembled on the recipient’s phone. We support up to 5 SMS parts per message, helping you send longer content while keeping message size controlled.

Customer replies may be supported depending on the sender type, destination country, and route used. Two-way SMS is useful for surveys, confirmations, customer support, and interactive campaigns. If replies are important for your use case, contact our support team before sending so we can guide you on the suitable setup, sender type, and availability for your destination.

You can upload recipient lists using common file formats such as Excel files, CSV files, and TXT files. This makes it easy to import contacts from spreadsheets, CRM exports, or existing customer databases. For better delivery accuracy, we recommend using international number format with the country code and removing invalid, duplicate, or inactive numbers before sending.

Yes, where supported by the destination country and local telecom rules, you can use a custom Sender ID to display your brand name instead of a random number. A branded Sender ID can improve recognition and trust, especially for alerts, OTP messages, reminders, and customer notifications. Some countries require Sender ID registration or may replace unsupported sender names, so availability can vary by destination.

Yes. You can prepare your SMS campaign in advance and schedule it for a later date and time when the feature is available in your account. Scheduling is useful for reminders, promotions, event updates, payment alerts, appointment notifications, and campaigns that need to be sent during a specific business hour or customer time zone.

Yes. If your contact list includes customer details such as name, reference number, appointment date, or other fields, you can use personalization features to make each message more relevant. Personalized SMS can improve engagement because recipients see content that is specific to them instead of a generic message.

Yes. Cleaning your contact list before sending is strongly recommended. Removing duplicate numbers, invalid numbers, landlines, inactive contacts, and incorrectly formatted entries helps reduce wasted SMS attempts and improves campaign quality. Using the correct international format with country code also helps the system route messages more accurately.

Yes. You can send SMS manually from the web portal or automate sending through our API. The web portal is ideal for uploading lists and managing campaigns without coding, while the API is useful for websites, CRMs, applications, OTP systems, booking systems, alerts, and other automated SMS workflows.

Routes & Setup

Plans and onboarding

  • Direct Route: Our premium route option, designed for faster and more stable delivery where supported. It is best for important messages such as OTP codes, account verification, login alerts, payment alerts, booking confirmations, and other time-sensitive notifications.
  • High Quality Route: A balanced option for businesses that need good delivery performance at a more flexible cost. It is suitable for customer notifications, reminders, promotional campaigns, CRM messages, and regular business communication.
  • Wholesale Route: A lower-cost option for larger volume campaigns where price is the main priority and instant delivery is not required. It is commonly used for high-volume promotional SMS, awareness campaigns, and bulk marketing traffic.

The best route depends on your message type, destination country, budget, volume, and required delivery speed. If you are sending OTPs or urgent transactional alerts, the Direct Route is usually the best choice. If you need reliable performance for normal business messages or marketing campaigns, the High Quality Route is a strong option. If your main goal is sending very large promotional volumes at the lowest possible cost, the Wholesale Route may be more suitable.

Yes. You can choose or adjust the route based on your campaign needs, destination, budget, and delivery expectations. Many customers use different routes for different use cases, such as Direct Route for OTP messages and High Quality or Wholesale routes for marketing campaigns. If you are unsure, our support team can help you select the most suitable route before sending.

Getting started is simple:

  1. Click the “Sign up” button on our website.
  2. Enter your account details and create your login credentials.
  3. Verify your email address using the verification link sent to your inbox.
  4. Log in to the dashboard, review the platform, and add funds when you are ready to send your own SMS campaigns.

Sender ID requirements depend on the destination country and local mobile operator rules. Some countries allow dynamic alphanumeric Sender IDs, while others require pre-registration before your brand name can be used. In restricted destinations, unsupported Sender IDs may be replaced, blocked, or delivered differently. If you plan to use a brand Sender ID, it is better to check the destination rules before launching your campaign.

The Direct Route is usually the best option when delivery speed is the highest priority. It is recommended for OTPs, verification codes, banking alerts, security notifications, urgent reminders, and time-sensitive customer messages. Delivery speed can still depend on the destination network, operator filtering, handset availability, and local telecom conditions.

Yes. It is always recommended to send a few test messages before launching a large campaign. Testing helps you confirm message formatting, Sender ID behavior, delivery status, link display, Unicode characters, and the overall user experience on the recipient’s phone. This is especially important when sending to a new country, new network, or new contact list.

API & Integration

Developers and automation

We provide multiple integration options for different technical needs. Developers can use our simple HTTP API for quick URL-based SMS sending, our modern REST API for structured JSON-based integration, and SMPP connectivity for high-volume or enterprise SMS traffic. These options allow you to connect BulkSMSOnline with websites, CRMs, mobile apps, billing systems, OTP systems, booking platforms, and internal business tools.

The HTTP API is ideal when you need a simple and fast way to send SMS from your system using standard web requests. It is commonly used for basic website forms, alerts, reminders, order notifications, and lightweight integrations where you want to trigger SMS sending without building a complex API workflow.

The REST API is recommended for modern applications that need structured requests, clean responses, and easier automation. It is suitable for CRMs, SaaS platforms, OTP systems, customer portals, e-commerce websites, and backend applications that need to send SMS, check delivery status, manage responses, or connect messaging into a larger workflow.

Yes. We support SMPP connectivity for customers who need high-volume SMS sending, persistent connections, and faster message submission. SMPP is commonly used by telecom platforms, aggregators, enterprise systems, and businesses with large or continuous SMS traffic. Availability, throughput, and setup details may depend on your account type, route, destination, and sending requirements.

API access is protected using account credentials, API keys, tokens, or the authentication method provided in your developer settings. This helps ensure that only authorized systems can send SMS from your account. For better security, API credentials should be stored safely on your server side and should never be exposed inside public frontend code, mobile apps, or browser JavaScript.

Yes. API rate limits may apply to protect platform stability, prevent abuse, and keep message submission reliable for all customers. The allowed sending speed can depend on your account, route, destination, traffic type, and approval status. If you need higher throughput for large campaigns, OTP traffic, or enterprise sending, our team can review your requirements and guide you on the best setup.

Yes. Delivery Reports, also called DLRs, allow you to track the status of submitted SMS messages. You can review message status from the dashboard or receive delivery updates through API callbacks. Common delivery statuses may include delivered, pending, failed, rejected, expired, or submitted, depending on the route and the mobile network response.

Yes. You can configure a webhook callback URL to receive automatic delivery updates directly in your application. When the message status changes, our system can send the update to your endpoint so your platform can record delivery results, update customer records, trigger workflows, or display SMS status inside your own dashboard.

Your webhook endpoint should be publicly reachable, stable, and able to accept delivery status updates from our system. We recommend using HTTPS, validating incoming data, responding quickly with a successful HTTP response, and storing each update safely in your database. Your system should also handle duplicate or delayed callbacks because mobile operator delivery updates may arrive at different times.

Yes. API responses are designed to help developers understand whether a request was accepted or rejected. Errors may relate to invalid credentials, missing parameters, incorrect phone number format, insufficient balance, unsupported sender ID, blocked content, route restrictions, or temporary processing issues. These responses help your system detect problems and handle them correctly.

Yes. You can use the API to automate bulk SMS sending from your own system. This is useful for campaign platforms, notification systems, CRMs, e-commerce websites, and applications that need to send messages to many recipients. For large batches, it is important to format numbers correctly, manage rate limits, monitor responses, and review delivery reports.

Yes. Balance-check functionality can help your system monitor available funds before sending campaigns or automated notifications. This is useful for preventing failed submissions caused by low balance and for triggering internal alerts when your account needs a top-up.

MNP and HLR lookup services help identify mobile number details such as number validity, current network, portability information, and routing-related data where available. This can help you clean your database, reduce failed SMS attempts, improve routing decisions, and avoid sending to inactive or incorrectly formatted numbers.

Security & Authentication

2FA and OTP services

SMS OTP, or One-Time Password, helps your business verify that a user has access to the mobile number linked to their account. It adds an extra security step for logins, signups, password resets, payment confirmations, account changes, and sensitive transactions. Instead of relying only on a password, your system sends a temporary code to the customer’s phone, helping reduce unauthorized access and fake account activity.

SMS OTP can be stronger than email-only verification for many authentication flows because it adds a separate mobile-based verification step. Even if a password or email account is compromised, the attacker may still need access to the user’s phone number to complete the login or transaction. However, SMS OTP should still be implemented carefully with expiry times, retry limits, fraud checks, and secure account recovery rules.

OTP messages are usually sent through routes designed for faster delivery, especially when used for login codes, account verification, and transaction confirmation. Delivery speed may depend on the destination country, mobile operator, handset availability, route type, and local filtering rules. For critical OTP traffic, we recommend using the most suitable route for fast and stable delivery.

OTP codes should only remain valid for a short period of time. Many businesses use an expiry window such as a few minutes, depending on the risk level of the action. Short expiry times help reduce the chance of old codes being reused, while still giving the customer enough time to receive and enter the verification code.

Yes. OTP systems should use resend limits, verification attempt limits, cooldown periods, and rate limits to prevent abuse. This helps protect your users from brute-force attempts and helps protect your business from unnecessary SMS costs caused by repeated code requests, fake signups, or SMS pumping attacks.

Yes. You can integrate SMS OTP sending into your website, mobile app, CRM, SaaS platform, or backend system using our API options. This allows your system to automatically send verification codes for signup, login, password reset, payment confirmation, booking confirmation, or account security checks.

For better OTP security, use short code expiry, limit resend attempts, block repeated failed attempts, monitor unusual traffic patterns, and avoid showing whether a phone number is registered or not. It is also important to protect your API credentials, validate phone numbers before sending, and use fraud controls to reduce fake requests and SMS pumping risks.
Ready to send better SMS campaigns?

Expand your business today!

Try It Now For Free