About Bulk SMS
Bulk SMS refers to sending the same message to multiple recipients at once, ranging from a few to up to 50,000 recipients
This can include both SMS (text-only) and MMS (multimedia messages containing images, videos, or PDFs). Bulk messages can be sent to various recipient groups, including:
Campaign Members: Individuals associated with specific marketing or communication campaigns. (Up to 50,000 per send)
Recipients from Reports: Data pulled from tabular reports, with specific naming conventions and limitations on the number of rows. (Up to 25,000 per send)
The report must be Tabular.
Report Name must start with ‘[Mogli]’.
The first column must be the ID of the records you’re looking to send to, such as for Contact or Lead. Mogli must be configured on the primary object of the report.
Reach out to our Tech Support team via help@mogli.com if you would like to integrate objects beyond Contact, Lead, or Opportunity.
List View or Mogli-configured Objects: Directly choosing contacts or leads from list views or individually.
Messages can incorporate merge fields for personalization, use pre-defined SMS templates, or include MMS attachments.
MMS Limitations in Bulk
Note that MMS sends have a recipient limit of 2,000 due to Salesforce limitations, and sending GIFs in bulk is generally not supported.
Getting Started
1 | Access the Bulk SMS Interface: Navigate to the 'Bulk SMS Lightning' tab (or 'Bulk SMS' tab for classic interface, though MMS is not supported there). |
|
2 | Add Recipients: In order to add recipients you can do one of the following:
|
|
3 | Compose Your Message:
|
|
4 | Configure Send Settings:
| |
5 | Schedule (Optional): Schedule the message for a later delivery time. | |
6 | Send: Click 'Send' to initiate the bulk message. |
Automating Bulk Messaging
When automating bulk messaging in flow or apex, be sure to populate the following fields on your automated bulk SMS records:
IsBatchTransaction = TRUE
Batch Group ID (a random, unique string), using code such as:
static public String createRandomNumberGroupId() { Blob b = Crypto.GenerateAESKey(128); String h = EncodingUtil.ConvertTohex(b); return(h.SubString(0, 8) + '-' + h.SubString(8, 12) + '-' + h.SubString(12, 16) + '-' + h.SubString(16, 20) + '-' + h.substring(20)); } |
|---|
Managing Scheduled or Sent Messages
Why are my scheduled bulk messages not sending?
This often occurs because the Mogli scheduled jobs are either inactive or are still owned by an inactive user. You must reschedule the jobs under an active user profile.
Why are my scheduled messages stuck in a "Queued" or "Scheduled" status?
This is typically due to a large backlog of Async Tasks building up in the system, which prevents Mogli from processing new sends. To delete async tasks, follow this guide.
What is the purpose of the Batch Group ID?
The Batch Group ID is a unique identifier Mogli uses to group thousands of messages sent at once into a single processing batch. This action significantly optimizes API calls and prevents the system from creating duplicate messages
Modifying/Deleting Scheduled SMS: For a few records, manually edit/delete from the SMS tab. For hundreds, use the 'Mass Delete' button on the Scheduled SMS list view. For many, use Data Loader or Salesforce's Developer Console.
Mass Deleting SMS Records:
In-App Button (up to a few hundred): Enable the 'Mass Delete' button on the SMS list view via Object Manager settings. Select records and click 'Mass Delete'.
Developer Console (up to 10,000 at a time): Use specific Apex code in the Developer Console to delete SMS records based on 'Queued' or 'Scheduled' status. Repeat for more than 10,000 records.
Mass Deleting Async Task Records: If you've deleted SMS records from a bulk send, you must delete associated Async Task records using Apex code in the Developer Console to prevent Mogli from continuing to attempt sending.
For more detailed instructions on Mass deletion of SMS and Async Tasks, check out Mass Deleting SMS records
Considerations & Limitations
Pre-Send Checklist for Bulk Messages
Messages will not be sent to recipients who have the 'Mogli Opt Out' checkbox marked as true on their record.
Confirm all intended recipients have a Mogli Number populated on their records for successful message delivery.
Carbon copy yourself on outbound bulk sends to experience the message exactly as your recipients do.
Managing Message Volume and Processing
For large bulk sends (over 1,000 recipients), allow the current send to process completely before initiating another large send.
Monitor the 'Async Tasks' tab and 'SMS' tab to confirm messages have been sent successfully.
Best Practices for URL Shortening and File Names
URL shorteners like Bitly or Google's Firebase dynamic links increase the likelihood of messages being flagged as SPAM. Consider using Mogli's custom URL shortening feature instead.
When sending MMS, keep MMS file names (JPEG, PNG, PDF, MP4) to 100 characters or less.
Gateway Selection and Send Limits
A single bulk send can go to up to 50,000 recipients when using a campaign or 25,000 when using a report
MMS is limited to 2000 recipients per send
If you’re using Salesforce classic, you’ll use the Bulk SMS tab. Important: MMS is not yet supported in classic. You will not see an Upload button on this tab.


