Quick answer
HubSpot SMS requires the SMS add-on and an in-app 10DLC registration: you submit brand details, HubSpot files with The Campaign Registry, and a dedicated number is provisioned. Consent is managed through HubSpot subscription types, which track status but do not capture the evidence a TCPA defense requires.
HubSpot brought SMS into Marketing Hub as a first-class channel: workflows can text leads, and subscription types govern who is eligible. The 10DLC registration flow is built into setup.
HubSpot's consent model is genuinely better than most: subscription types, legal basis tracking, GDPR tooling. But its records remain CRM properties, editable by workflows and imports, with no archived form language or session evidence behind them.
How SMS Works in HubSpot
With the SMS add-on, HubSpot provisions a dedicated number and sends through its own carrier connections. Eligibility is governed by an SMS subscription type: contacts must be opted in to receive marketing texts.
Consent enters through HubSpot forms with a consent checkbox, chat flows, imports, or workflow property updates. The registration you complete during setup files your brand and campaign with TCR through HubSpot's provider.
How to Set Up 10DLC for HubSpot
- 1
Buy the SMS add-on and open registration
SMS lives behind an add-on for Marketing Hub Pro and Enterprise. Setup walks you into the 10DLC business registration form.
- 2
Submit brand and campaign details accurately
Legal entity name, EIN, website, and message samples. HubSpot files with TCR; approval commonly lands within 1-7 business days, with rejections almost always traced to legal-name or EIN mismatches.
- 3
Create an SMS subscription type and consent path
Add an SMS-specific subscription type, attach it to forms with an unchecked consent checkbox, and write the full disclosure into the form's consent text.
- 4
Gate every SMS workflow on subscription status
Workflow enrollment must check the SMS subscription, not a free-form property. Imports and integrations that set properties directly are how revoked or never-consented contacts get texted.
Where HubSpot Setups Fail TCPA Review
Carrier approval is step one. These are the consent gaps that turn into demand letters.
Subscription status is a property that workflows, imports, and API calls can flip without evidence
HubSpot form consent text is editable history: past versions are not archived against past submissions
No session replay or point-in-time proof exists for any opt-in
Cross-object syncs (Salesforce, ecommerce) routinely write consent fields they cannot substantiate
How OptInFix Closes the Gaps on HubSpot
Evidence-first capture, HubSpot sync second
Collect opt-ins on an OptInFix form, then sync the contact and consent status into HubSpot via webhook. The vaulted evidence outlives any property change.
Opt-in URL for the registration form
HubSpot's 10DLC registration asks how you collect consent; your hosted OptInFix page is a reviewer-ready answer.
Audit trail that survives admins
Append-only records with timestamps, IP, geolocation, and form versions, publicly verifiable by consent ID when a carrier or plaintiff asks.
10DLC for HubSpot: Frequently Asked Questions
Does HubSpot file 10DLC registration?
Yes. During SMS setup HubSpot collects your business details and files brand and campaign registration with The Campaign Registry through its carrier provider.
Are HubSpot subscription types enough for TCPA compliance?
They are necessary but not sufficient. Subscription types enforce eligibility, but they are editable properties without archived consent language or session evidence, which is what defends you in a dispute.
Can workflows text contacts who never opted in?
Yes, if a workflow or import sets the subscription property directly. Locking SMS sends behind genuine form-sourced consent and auditing property changes prevents this failure mode.
Which HubSpot tiers support SMS?
SMS is an add-on for Marketing Hub Professional and Enterprise in supported regions, with 10DLC registration required before US sending.