How to Set Up DLR Through Web Notification in BulkSMSOnline
DLR Through Web Notification allows your system to receive SMS delivery report updates from BulkSMSOnline through a callback URL. This is useful for businesses and developers who want to track SMS delivery status automatically instead of checking reports manually from the dashboard.
DLR stands for Delivery Report. It helps you understand the delivery status of your SMS messages after they are submitted to the mobile network. Depending on the destination country, route, and network support, DLR updates may help you track whether a message is delivered, pending, failed, rejected, expired, or still being processed.
What Is DLR Through Web Notification?
DLR Through Web Notification is a webhook-style delivery report setting. When enabled, BulkSMSOnline can send delivery status updates to the DLR URL you configure in your account settings.
This feature is helpful if you use SMS for:
- OTP and verification codes
- Transaction alerts
- Payment notifications
- Booking confirmations
- Delivery updates
- Customer alerts
- API-based SMS sending
- Automated CRM or application notifications
For developer documentation, API sending, delivery reports, and webhook callbacks, visit the BulkSMSOnline Developers page.
Why Use DLR Web Notification?
Using DLR Through Web Notification can help your system receive delivery status updates automatically. This is especially useful when your business sends high volumes of SMS or needs to update customer records, order status, OTP logs, or campaign reports in real time.
DLR web notification can help you:
- Track SMS delivery status automatically.
- Update your CRM, website, application, or internal system.
- Reduce manual checking from the dashboard.
- Monitor OTP, alert, and transactional message performance.
- Improve campaign reporting and delivery analysis.
- Investigate failed or pending SMS messages more easily.
How to Set Up DLR Through Web Notification
To configure DLR Through Web Notification in your BulkSMSOnline account, follow the steps below:
- Log in to your BulkSMSOnline account dashboard.
- Click your account name or username at the top-right corner of the screen.
- From the dropdown menu, click Settings.
- Scroll to the DLR Through Web Notification section.
- Enter or paste your DLR callback URL into the DLR URL field.
- Check that the URL is correct and accessible from your server.
- Click Save to apply and store your DLR web notification settings.
You can access the SMS platform here: BulkSMSOnline Login.
Step 1: Log In to Your Account
First, log in to your BulkSMSOnline account using your registered username and password.
After logging in, you will be redirected to your dashboard. From there, you can manage your SMS campaigns, API settings, account settings, reports, billing details, and delivery tracking options.
Step 2: Open the Settings Page
Once you are inside your dashboard, look at the top-right corner of the screen and click your account name or username.
A dropdown menu will appear. Click Settings to open your account settings page.
Step 3: Find the DLR Through Web Notification Section
On the settings page, scroll until you find the DLR Through Web Notification section.
This section is where you can add the callback URL that will receive SMS delivery report updates from BulkSMSOnline.
Step 4: Enter Your DLR Callback URL
In the DLR URL field, enter or paste your callback URL. This should be a valid web address from your server or application where you want to receive delivery report notifications.
Example format:
https://yourdomain.com/dlr-callback
Make sure your URL is active, reachable, and configured to receive delivery report requests. If your server blocks incoming requests or the URL is incorrect, DLR notifications may not be received successfully.
Step 5: Save Your DLR Settings
After entering your DLR URL, click the Save button.
Your DLR Through Web Notification setting will now be stored in your BulkSMSOnline account. Future delivery report updates may be sent to the callback URL based on your route, destination, and delivery report availability.
Recommended DLR URL Requirements
Before saving your DLR URL, make sure it is properly prepared. A good DLR callback URL should:
- Use a valid and working HTTPS URL where possible.
- Be hosted on a reliable server.
- Be accessible publicly from the internet.
- Be able to receive incoming webhook or callback requests.
- Respond quickly to incoming requests.
- Log received delivery report data for troubleshooting.
- Avoid redirect loops, expired links, or blocked firewall rules.
Important Notes About Delivery Reports
Delivery reports may depend on the destination country, mobile network, selected route, and operator support. In some cases, delivery report visibility may vary depending on the SMS route used for the campaign.
For important traffic such as OTP, login codes, payment alerts, and urgent notifications, choosing the right route is important. You can learn more about route options here:
Using DLR Web Notification With SMS API
DLR Through Web Notification is especially useful for businesses using SMS API integration. If your website, CRM, app, billing system, or backend service sends SMS automatically, DLR callbacks can help your system track delivery results programmatically.
You can use DLR notifications for:
- Updating OTP delivery status
- Tracking customer notification results
- Updating CRM message logs
- Monitoring transactional SMS
- Recording failed or pending messages
- Improving reporting for automated SMS workflows
For API documentation, REST API, HTTP API, SMPP, delivery reports, and webhook callbacks, visit:
Using DLR Reports With the Web SMS Platform
If you send SMS manually from the dashboard, you can also monitor delivery activity from your account reports where available. DLR web notification is mainly useful when you want delivery updates sent to your own system automatically.
To learn more about dashboard-based SMS sending, visit:
Common DLR Statuses
DLR status names may vary depending on the route, destination, and network response. Common delivery report statuses may include:
- Delivered: The message was delivered successfully where confirmation is available.
- Pending: The message is still being processed or waiting for final status.
- Failed: The message could not be delivered.
- Rejected: The message was rejected by the system, route, or network.
- Expired: The message was not delivered within the allowed delivery period.
- Queued: The message is waiting to be processed.
If you need help understanding a specific DLR status, contact BulkSMSOnline support with the message ID, destination country, sending time, sender ID, and delivery status.
Testing Your DLR Web Notification
After saving your DLR URL, it is recommended to send a small test SMS campaign before using the setting for large-volume SMS traffic.
When testing, check the following:
- The SMS message is submitted successfully.
- Your callback URL receives the delivery report notification.
- Your server logs the incoming request.
- Your system stores the message status correctly.
- Your application can handle repeated or delayed delivery updates.
Testing helps confirm that your DLR notification setup works correctly before you rely on it for production SMS traffic.
DLR Web Notification Best Practices
To improve reliability, follow these best practices when setting up your DLR callback URL:
- Use HTTPS for better security.
- Keep your callback endpoint stable and always available.
- Log every incoming DLR request for future troubleshooting.
- Store message IDs so you can match delivery reports with sent SMS records.
- Do not expose sensitive credentials in your callback URL.
- Make sure your server can handle repeated requests safely.
- Use proper validation and security checks on your webhook endpoint.
- Test the callback URL before sending large campaigns.
Troubleshooting DLR Web Notification Issues
If your DLR web notification is not working, check the following:
- Make sure the DLR URL was saved correctly in your account settings.
- Confirm that the callback URL is active and publicly accessible.
- Check whether your server firewall is blocking incoming requests.
- Review your server logs to see if any DLR requests were received.
- Make sure your endpoint can handle the request format.
- Check whether the selected SMS route supports delivery reports.
- Confirm whether the destination country and network provide DLR visibility.
- Send a small test SMS and monitor the callback result.
When Should You Contact Support?
You should contact BulkSMSOnline support if:
- You saved the DLR URL but no callback is received.
- Your delivery reports are missing or unclear.
- Your message status remains pending for too long.
- You need help checking a specific message ID.
- You are unsure whether your selected route supports DLR.
- You need help with API, webhook, or delivery report setup.
For faster assistance, prepare the following details before contacting support:
- Your BulkSMSOnline username
- Your registered email address
- Message ID, if available
- Destination country
- Recipient number, if needed for checking
- Sender ID used
- Sending date and time
- DLR status shown in your dashboard or system
- Your callback URL, if relevant
Need Help With DLR Through Web Notification?
If you need help setting up DLR Through Web Notification, understanding delivery reports, checking callback issues, or integrating SMS API delivery reports into your system, visit the BulkSMSOnline Help Center.
For account-specific support, contact the BulkSMSOnline team through the official contact page:
Related Resources
- BulkSMSOnline Homepage
- BulkSMSOnline Login
- BulkSMSOnline Developers
- Send Bulk SMS Online
- Web SMS Platform
- SMS Routing
- Bulk SMS Pricing
- Help Center
- FAQs
- Contact Us
Frequently Asked Questions
What is DLR Through Web Notification?
DLR Through Web Notification is a delivery report callback setting that allows BulkSMSOnline to send SMS delivery status updates to your configured web URL.
Where can I set up my DLR URL?
Log in to your BulkSMSOnline account, click your account name, open Settings, find the DLR Through Web Notification section, enter your DLR URL, and click Save.
What is a DLR URL?
A DLR URL is the web address on your server or application where delivery report notifications are sent.
Do I need a developer to set up DLR Web Notification?
If you only need to paste an existing callback URL, you may not need a developer. However, if you need to create the callback endpoint, store delivery statuses, or connect DLR updates to your system, a developer is recommended.
Why am I not receiving DLR callbacks?
This may happen if the callback URL is incorrect, your server is blocking requests, the endpoint is unavailable, the selected route does not support DLR, or the destination network does not provide full delivery report visibility.
Can I use DLR Web Notification with SMS API?
Yes. DLR Web Notification is useful for API users who want delivery report updates sent automatically to their own system.
Are delivery reports available for every country?
Delivery report availability may depend on the destination country, mobile network, and selected SMS route. Some destinations or routes may provide different levels of delivery visibility.
Should my DLR URL use HTTPS?
Using HTTPS is recommended because it provides better security and helps protect delivery report data during transmission.