How JumpstartMD Achieved SMS Compliance Across 14 California Clinics Through a Custom HubSpot Preference Center

Where JumpstartMD's SMS System Fell Short

1. Global, all-or-nothing SMS opt-out.

HubSpot's native SMS subscription model treated every text message as one category, with no distinction between marketing and operational content. Any patient who replied STOP to a promotion was unsubscribed from appointment and telehealth reminders as well.

2. Two legacy opt-out categories at risk of being lost.

Salesforce Marketing Cloud had tracked "Marketing Only" and "All SMS" opt-outs as separate lists for years. Migrating that history into HubSpot's single opt-out model would have erased the distinction the organization had already established with its patients.

4. Confusing native subscription language.

HubSpot's default SMS and email subscription checkboxes read in a way where a checked box meant opting out, not confirming consent. Left as-is, that wording created real risk of patients misunderstanding their own preference settings.

5. No property to represent operational consent.

Nothing in JumpstartMD's HubSpot environment distinguished an operational SMS opt-in from a marketing one before this project began. Every downstream workflow that needed to protect appointment reminders had no field to reference.

6. Inconsistent mobile phone data.

A meaningful share of contact records carried mobile numbers in formats HubSpot could not reliably send to. Every one of those records represented a patient who could silently stop receiving reminders without anyone noticing until a missed appointment.

7. Unclear SMS sending capability.

JumpstartMD's team had been told HubSpot did not support shortcode SMS sending, information that later proved incomplete once a beta became available. Scoping decisions about the broader SMS build depended on getting that capability question resolved first.

How Campaign Creators Engineered Two-Tier SMS Consent Inside HubSpot

Campaign Creators sequenced the build around data before automation: consent properties and Salesforce synchronization came first, and the patient-facing preference center and workflows followed once that foundation was in place.

Consent on Standard Contact Properties

Campaign Creators represented SMS consent using standard HubSpot contact properties, not a custom object: Marketing SMS Opt-In, Operational SMS opt-in, and a multi-checkbox SMS Subscription Type Opt-Out property. Keeping consent on the standard Contact object means JumpstartMD's team administers SMS preferences through the same record view used for every other patient property, with no separate object schema to maintain.

A Salesforce Formula Field to Clean Mobile Numbers

HubSpot's native Salesforce integration carries the new properties in both directions, alongside a Salesforce formula field, PhoneCleanedUp__c, built to standardize mobile numbers before HubSpot syncs them into its Mobile Phone property. The field-level mapping between the two systems keeps a phone number reformatted once in Salesforce, then reliably usable everywhere HubSpot needs to send an SMS.

Two Imports to Preserve Two Opt-Out Categories

Legacy Marketing Cloud opt-out history moved into HubSpot through two separate CSV imports, one for contacts who had opted out of marketing SMS specifically and one for contacts who had opted out of all SMS. Sequencing the migration this way preserved a distinction JumpstartMD had already established with patients, ahead of any new consent logic going live.

Five Properties Mapped to Two Teams

The property set came from mapping what each team actually needed day to day: marketing needed to know who could receive promotions, operations needed to know who could receive appointment reminders, and both needed a record of why a given phone number had or had not been reformatted. That produced five properties: Marketing SMS Opt-In, Operational SMS opt-in, SMS Subscription Type Opt-Out, Date Phone Number Reformatted, and Number Reformatting Skipping Reason.

Three Active Lists for Marketing and Operations

This engagement did not call for new association labels between contacts and other object types; the contact record structure itself did not change. What Campaign Creators built was list-based segmentation: three active lists, SMS Opt-Outs: Marketing Only, SMS Opt-Outs: Operational Only, and Total SMS Opt-Outs, so marketing and operations staff can each filter to the segment relevant to its own sends without a change to record-level permissions.

Seven Workflows Keeping HubSpot and Salesforce in Sync

Seven workflows keep HubSpot's native SMS subscription types, the new consent properties, and the mirrored Salesforce fields synchronized in both directions. Concrete examples:

• A contact whose SMS Subscription Type Opt-Out property shows both categories opted out, or whose Salesforce record shows All SMS Opt-Out = Yes, is enrolled in HubSpot's native global SMS opt-out.
• A contact who replies STOP and triggers HubSpot's native global opt-out has that status synced back to Salesforce's All SMS Opt-Out field.
• A contact's marketing SMS subscription status syncs to the Marketing SMS Opt-In property, and the property syncs back to the subscription, in both directions.
• The same two-way sync runs for operational SMS opt-outs.
• A contact marked Marketing SMS Opt-In = Yes has their cleaned-up Salesforce phone number copied into HubSpot's Mobile Phone property automatically.

Reviewed and Approved Before Activation

Every new property and the preference-center form were documented in plain terms tied to JumpstartMD's own patient-communication language, not generic platform terminology. Before any workflow went live, Campaign Creators routed the completed build back to JumpstartMD's team for review and sign-off, so activation followed a deliberate final check, not an automatic release.

Impact: A Consent Model Built to Extend Without Rebuilding

SMS consent management at JumpstartMD is built entirely from standard HubSpot contact properties that any admin on the team can inspect and extend directly, with the property set and the Salesforce field mapping already documented. Extending the model to a new consent category means adding one more property and one more workflow pair, not re-architecting the system that already exists.

Solve SMS Compliance and Patient Communication Risk With Campaign Creators

Healthcare organizations that communicate by SMS carry a specific risk: a single, undifferentiated opt-out setting can silence the reminders patients depend on at the same time it respects their marketing preferences. Closing that gap requires a data model built around the distinction from the start, not a workaround layered on top of a platform default.

Campaign Creators builds SMS consent systems, HubSpot-Salesforce integrations, and patient-communication architecture designed to hold up under real compliance requirements, not just pass an initial review.

Talk to a HubSpot expert to see how Campaign Creators can build a compliant SMS consent system around your existing HubSpot and Salesforce environment.