Mogli SMS & WhatsApp Communication - Messaging Functionality
Mogli does not store client Salesforce data externally to Salesforce. All client data lives solely in the client’s Salesforce instance itself.
Mogli does store the Sending Gateway (sending phone number of the client) and messaging provider details on its AWS server.
In order to send/receive messages, some data must be processed by Mogli’s system before it is sent to Mogli’s messaging partners.
When an SMS is sent, the following message data is processed in AWS prior to being sent onto Mogli’s messaging partner.
Sending Gateway (sending phone number of the client)
Receiving phone number (who they are sending the message to)
Message text
ID of the Salesforce record the message was sent from (such as a Contact, Opportunity, or other object record)
ID of SMS record in Salesforce
Mogli does not store this information after processing with the exception of the Sending Gateway and Salesforce ID of the SMS record - as this is needed to write back to the record with the delivery status and other responses from the messaging partner. Mogli’s logs store the batch group id, the SMS record id, the provider message id, and timestamps for status changes.
Mogli does not store the raw recipient phone number after processing. However, to support essential services which includes delivery verification, and integration with external platforms, we retain a cryptographic hash of the receiving number. This one-way hash allows Mogli to uniquely identify and correlate records for troubleshooting and reporting purposes without ever storing or exposing the readable recipient phone number at rest.
No client data is saved in Mogli systems.
Once a message is sent onto Mogli’s messaging partner, that messaging partner saves the following data in order to send the message through to carriers (such as Verizon and AT&T):
Sending Gateway (sending phone number of the client)
Receiving phone number (who they are sending the message to)
Message text
Messaging Partners do save this data long-term.
Mogli SMS & WhatsApp Communication - One-Off Reporting Requests
From time to time a Mogli client may request usage logs from one of our messaging partners. In this case both aggregate and detailed message data is pulled onto Mogli’s AWS servers. The detailed data includes:
Sending Gateway (sending phone number of the client)
Message Segment Count
Messaging provider data such as:
provider message id
timestamps for status changes
Id of the Brand and Campaign sending the message
The message body and receiving phone number (who they are sending the message to) are NOT retrieved.
This data is cached while processing and then deleted automatically after 7 days.
Mogli URL & URL Pro
When using Mogli URL, the shortened URLs themselves and the domain information are stored on Mogli’s AWS server.
When using Mogli URL Pro (which allows for unique link tracking by recipient), then - additionally - the IP Address, Domain information, and Browser data for the click are stored so that this can be written back to the client Salesforce instance.
Mogli Scheduler
When using Mogli Scheduler, Mogli stores Guest information and the User's Calendar Data (specifically the available / unavailable date/times; the details of the calendar events are not stored). Agreement to store this data is included in the Terms of Use provided to both the User (when logging into https://app.mogli.com/sign_in) and the Guest when booking a calendar event.
Client Provided Access to Client Data
During onboarding and from time to time during a contract term, a client may be asked to provide Salesforce Subscriber login access to a Mogli employee to assist in configuring or troubleshooting.
Salesforce Subscriber login access has security measures built in such as the inability to import or export data. Clients may choose to remove access at any time. Mogli does not recommend that clients provision user licenses to Mogli staff, but use the subscriber login access whenever possible.
Additionally, it is possible to review all changes made by Mogli users logged into your system via Subscriber login access through the Setup Audit Trail function in Salesforce.