HubSpot SMS Integration for Reminders & Replies

• HubSpot offers SMS add-ons for marketing and transactional texts through Twilio. Registration and carrier approval are required before sending.

• You can send SMS through HubSpot add-ons, marketplace apps, or custom integrations. Each handles sending numbers and consent records differently.

• Build reminder workflows around the meeting start time, not the booking date. Always test rescheduling.

• HubSpot delays texts scheduled between 8 PM and 8 AM in the contact's local time.

• You can manage SMS replies in HubSpot Inbox, but cannot start texts from CRM records or Help Desk.

• Use an optional, unchecked consent checkbox with required disclosures, and sync STOP replies with the contact's SMS status in HubSpot.

First, what do you get without installing anything? HubSpot sells SMS as add-ons. One is for marketing texts, and one is for transactional texts. Both send through Twilio, from a number HubSpot sets up for you.

HubSpot describes transactional texts as time-sensitive messages to customers, such as one about a recent purchase or an upcoming contract renewal. (Source: "Set up SMS messaging for transactional communications")

The marketing add-on details come from HubSpot's separate setup page. (Source: "Set up SMS messaging")

Now the fine print, because this is where teams get surprised. You can send only from US-based numbers. Each account gets one marketing number and one transactional number. Sole proprietors are out, since HubSpot doesn't support SMS for them. And after you submit your business details, carrier approval can take a few more weeks on top of the number wait.

So which route is right? There are three, and they differ most in two things: which number sends the text, and where the consent record lives.

Many HubSpot SMS integrations exist because teams need a route that HubSpot's add-ons don't give them. Whichever you pick, a HubSpot text integration lives or dies on four details: the number it sends from, how opt-ins are stored, what it writes back to the record, and who sees the replies.

Here's the short version. Start a workflow when a meeting is booked. Copy the meeting's start time onto the contact. Wait until reminder time, check the meeting still stands, then send the text. HubSpot's meetings tool schedules reminder emails, but its help center describes no text reminders. So the text needs a workflow and an SMS sender.

1. Check the basics. You need a registered SMS number or an SMS app, an opted-in contact, and a phone number with a country code. Workflows text the Mobile Phone Number property, and fall back to Phone Number if it is empty. (Source: "Send automated SMS messages using workflows")

2. Create a contact-based workflow that starts on the Meeting booked event. Limit it to one scheduling page and turn on re-enrollment, so a customer who books again gets a new reminder.

3. Create a contact property called Next meeting start. Make it a date and time field, because a date-only field drops the hour. Add an Edit record action that copies the associated meeting's start time into it.

4. Add a delay until that property, set to your lead time, such as 30 minutes before.

5. Add an if/then branch that continues only when the meeting is not canceled and the contact has a mobile number.

6. Send the text with the contact's first name and the time.

Step 3 is the one to get right. A plain delay counts from the booking, not from the meeting. Book three weeks ahead and your customer gets a reminder three weeks early. (Not ideal.) A phone vendor published this pattern in October 2026. Its weak spot is rescheduling: the start time on the contact doesn't update by itself, so a moved meeting can still send a text at the old time. Test a reschedule before you turn it on. (Source: "How to Send SMS Meeting Reminders with HubSpot and Allo")

Quiet hours need a second look. HubSpot defers any text due between 8 PM and 8 AM in the contact's local time until quiet hours end. So a 7 AM reminder for an 8:30 AM appointment goes out at 8 AM. Apps may follow different quiet hour rules, so ask each vendor. (Source: "Understand SMS quiet hours")

Treat these as transactional texts, and fire them from a workflow that watches a deal, ticket, or order property. A status change beats a clock as a trigger, because it fires when something actually happens.

Three rules keep alerts out of trouble. First, register your transactional use case honestly. HubSpot warns that sample messages that don't match the sender and use case can fail registration. So don't slip a promo into an alert. Second, expect to enroll the person as a marketing contact.

HubSpot's workflow page says contacts must be opted in and set as marketing contacts to get automated texts. Check what that does to your marketing contact count before you enroll every customer. Third, check your tokens. Deal-based tokens work in SMS only if your account is in HubSpot's beta for multi-object personalization.

Here's the part that's easy to miss. Order data often lives outside HubSpot, in a store, an ERP, or a booking tool. A status change there has to reach a HubSpot property before a workflow can react. That sync is a HubSpot integration job, and it decides whether the alert fires on time or never.

Connect your SMS number as a channel in the conversations inbox. Replies land there, and anyone with inbox access can read them, see the contact's CRM data, and answer (as long as the contact is still opted in). HubSpot says its long code add-on suits customer service and two-way communication best. (Source: "Manage and reply to marketing SMS messages in the conversations inbox")

You can also connect an SMS channel to Help Desk, so customers can text a number you print on your website or onboarding materials. Now the catch for sales teams: HubSpot says you can't start a text from Help Desk or from a CRM record. The channel is built for replies. If your reps need to open a conversation themselves, that's the usual reason to add a marketplace app. (Source: "Set up SMS messaging for support communications")

Before you lean on a shared inbox, decide who owns it. Name one team, set an assignment rule, and agree on a response time. In the first weeks, count the replies in a normal day so you can size the team that answers them.

Short version: register your business, collect explicit opt-in, and honor STOP. HubSpot enforces some of this for you. It can't write your consent language, and it can't check that your form matches what you told the carriers.

Registration asks you to describe every way people opt in. If the way is a website form, HubSpot's setup page lists what the form must have:

• A separate SMS consent checkbox that is optional, not pre-checked, and not required to submit the form. HubSpot recommends placing it near the phone number field.

• Your legal business name, the type of messages, message rates, message frequency, and how to opt out.

• Live links to a privacy policy and SMS terms of service that cover texting.

Other opt-in paths exist. A contact can text a keyword to your number. Or you can opt a contact in by hand when you hold their explicit and verifiable consent. A workflow action can also set a contact's SMS subscription and record the legal basis and how consent was given. Contacts opt out by replying STOP, and HubSpot updates their status. HubSpot says its consent page isn't legal advice, so have counsel review your wording. (Source: "Collect and manage consent to send SMS messages")

The disclosure text often has to show up on many pages and forms. A reusable custom website module can hold it, so every page that collects a mobile number shows the same wording. When legal edits the text, you change it once.

Pick the one that passes your own tests. The best HubSpot SMS integration for a clinic that sends reminders isn't the best one for a store that sends delivery alerts. Most "best of" lists come from SMS vendors, and each list tends to favor its author. So I won't rank them here.

Ask every vendor on your shortlist these questions:

Then run five real texts before you commit: a reminder, an alert, a reply, a STOP, and a send to a contact with no mobile number. Open each record afterward and check what arrived. A demo shows what the vendor built. These texts show what your account will do.

Rule out these causes first. They cover registration, consent, number format, and timing:

Start every investigation with one test contact. Text the contact, watch the workflow's enrollment history, and open the record. If the text shows up in the vendor's app but not on the record, the sync is the problem, not the message.

Can I Text Contacts Outside the US and Canada?

HubSpot sends only from US-based numbers, and its long code numbers reach recipients in the United States and Canada, not the U.S. Virgin Islands. For other countries, ask a marketplace app which numbers it uses and which local rules it follows. Vendors publish their own coverage, so confirm it for every country you need.

Do I Need Marketing Hub to Send Texts?

HubSpot's transactional SMS setup page lists all products and plans. Its workflow page lists the SMS add-ons beside Marketing Hub Professional and Enterprise, and the marketing add-on requires one of those. Confirm in your account which path your workflow needs. Marketplace apps have their own HubSpot plan requirements.

What Happens When Someone Replies STOP?

HubSpot updates the contact's SMS subscription automatically. After a contact opts out, you cannot send more messages unless they text you again, which re-establishes consent. Put a STOP in your tests, and check that any app you use passes opt-outs back to HubSpot.

Do Replies Count Toward My Text Limit?

Yes. HubSpot says incoming and outgoing messages in the conversations inbox count against your monthly SMS segment usage. A long message uses more than one segment, so keep texts short and watch your usage during the first month.

Can I Add Deal or Ticket Details to a Text?

If your account is in HubSpot's beta for multi-object personalization tokens, you can use tokens for any object type that matches the workflow, such as deal tokens in a deal-based workflow. Without the beta, check which tokens the SMS editor offers, and ask any app which properties it can merge.

Start small. A HubSpot SMS integration for appointment reminders is the easiest first project, because the trigger, the timing, and the consent are all clear. Build one reminder, run the five test texts, and expand only after the first one behaves.

One more thing. Treat any HubSpot text integration as a consent system first and a messaging tool second. Before you add more HubSpot SMS integrations, write down where each contact's opt-in came from.

And if you're moving to HubSpot from another system, bring each contact's opt-in status and its source into your HubSpot migration scope, because HubSpot expects verifiable consent.