Skip to content
logo logoSelf Service
Sign In Sign Up
  • Home
  • Knowledgebase
Back

Mobile Commons: Standard CRM Integrations: The Basics

  • PDF
  • Print
  • Copy To Clipboard
  • Collapse All Expand All

Environment

Mobile Commons

Resolution Summary

Provided instruction for Standard CRM Integrations: The Basics

Details

With Mobile Commons, you can effortlessly sync information between your CRM database and Mobile Commons. Profile info (such as name, email, mobile number, and address) is synchronized in real-time between the two systems. For almost all of our syncs to correctly update your CRM records from Mobile Commons we require a profile's email address.  When you are ready to set up your sync, please reach out to your Mobile Strategist to get started. If you do not know who your Mobile Strategist is please email support and they will get you in touch with your Mobile Strategist. 

Most out of the box syncs at Mobile Commons operate in a similar manner. Mobile Commons will receive any updated records from the CRM during an overnight sync. There are also intraday syncs that will update any opt-outs from Mobile Commons, these run every five minutes. 

We support:

  • ActionKit
  • Action Network
  • BSD Tools
  • Salsa
  • Blackbaud Luminate
  • Nation Builder
  • Salesforce

Image

Here’s how it works: When a new user opts in, or an existing user adds a mobile number, we update both databases.

If you have a Conservative sync enabled we will only take action for those records which have an opt-in status demarcated in your CRM. If you have a Liberal sync enabled we will sync both ways. Please check your sync's documentation page for exactly how that sync works.

Path 1: User texts to your organization

  • Our system compares the information in the text against your database.
  • If the user’s record is found in your database we will update it with the mobile number, and update Mobile Commons with any additional information (e.g. 
name & address).
  • If the user’s record is not found in your database we will add the subscriber. Some syncs additionally support an automated email going out to new database members.

Path 2: The user opts in through your existing CRM

  • Each night, we import all new records in your CRM which have a valid mobile number. They are then set as a deferred subscription until we begin processing their welcome messages/opt-in path subscriptions the next day at 12pm ET. They will not be shown as an "Active Subscriber" until they are subscribed to an opt-in path.
  • These people are opted in for text alerts when they receive their welcome text the next day.These messages will begin sending at 12pm ET the next day. These messages are only sent during a 12-5pm safe window in each timezone. This is based off the timezone in that user's profile. 
  • You can choose to opt‐in ALL constituents with a mobile number, or just users 
who check a “Send Text Alerts” box. 
 

Once synced, profiles will display the constituent id, or record number from the CRM. You can use this to identify records across both of your systems easily.

Constituent_ID.jpg


Mobile Commons processes all updates, every day

  • We pull in all recent updates from your CRM and process them nightly.
    • For example, if an existing constituent provides their home address, this will be pulled into Mobile Commons, allowing your organization to do geographic targeting with your mobile list. 


Nobody gets messages they don’t ask for

  • We set a flag in your CRM to indicate whether or not a user is opted in to mobile.
  • This field is updated immediately when the user opts-­‐in and again when they 
opt-­‐out by texting STOP. 

Data Sync Sub-Tab

Ask your mobile strategist about setting up an integration. After setting it up, they will work with you to test it out. Once the integration has been created, you can click on any of the links under the “Integration Actions” menu to do the following:

  • Configure Integration: Change any of the credentials for your CRM system.
  • Edit Field Mappings: Map from Mobile Commons fields to your CRM system’s fields, if they do not match with the API field name. The fields must match the variable names in the API/data export
  • Edit Campaign Mappings: Use campaign mappings to synchronize different mobile campaigns with different CRM campaignsor groups. For example, if someone texts CAT, they can automatically be put in your "Cat Lovers" group. If they text DOG, they will be added to the "Dog Lovers" group. This mapping happens in both directions: different web forms send supporters different welcome text messages depending on their areas of interest.
  • Synchronization Report: link to a detailed report of the daily overnight sync.  See how many profiles were synced and link directly to the profiles themselves in Mobile Commons. 
  • Deactivate Integration: You can deactivate the integration at any time – for example, if you are switching to another CRM, you need a temporary shutoff, or any other reason

Mobile Commons provides an out-of-the-box data sync with the following CRM and Email Platforms. Click on the name of the platform to read more about the integration, and requirements for setup:

  • ActionKit
  • Action Network
  • BSD Tools
  • Salsa
  • Blackbaud Luminate
  • Nation Builder
  • Salesforce


Resolution Category

Question: Product How-To / Training

Keywords: integration, setup, salsa

Solution to Copy:

Copy to Clipboard

Failed to download PDF file.

Problem creating pdf file for the solution: 201123135132607
Close

Acknowledged.

Thank you for acknowledging that you have read and understood this solution.

Failure.

Unable to acknowlege. An error occurred.
Knowledge
  • Knowledgebase
Upland RightAnswers | Self Service - 2024R2
© Fri Jul 10 03:13:47 EDT 2026 Upland Software, Inc. All Rights Reserved