HubSpot SMS Integration:
Built CRM-Native, Not Bolted On

Plans start at $49 per month for 1,000 messages, with higher tiers at $99, $399, $999, and $1,999 depending on volume, and enterprise plans from $6,875 per month for 250,000 messages up to $15,000 per month for 1 million. Every plan is month-to-month with no contracts and no cancellation penalties. See the pricing page for full tier details.

Message IQ runs as a native action inside HubSpot. Sending a text is a step in the HubSpot workflow builder, next to Send Email and Create Task. There are no webhooks, no Zapier, and no middleware sitting between the two systems. Teams can also work from a standalone web app or the mobile app when they are away from the portal.

No. Message IQ is available in the HubSpot portal, in a standalone web app, and on mobile. Teams that do not use Chrome, or that prefer not to install browser extensions, send and reply the same way everyone else does.

Yes. The SMS step is part of the workflow builder and can run from a contact, company, deal, or ticket workflow. Messages pull property values from the record that triggered them, so the text can include a location, a date, a service type, or any other field you store in HubSpot.

Not today. The Message IQ SMS action is available in contact, company, deal, and ticket workflows. It does not appear as an action inside a custom object workflow, so a message cannot be triggered from a custom object record. If your process is built around a custom object, the usual path is to drive messaging from the associated contact records and keep the fields you need for personalization on the contact. That mapping is worth working through early rather than after you buy.

Sends and replies log to the contact timeline automatically. SMS also appears in HubSpot’s shared inbox and help desk alongside email and chat. Every reply lands as a real one to one conversation, not a marketing event.

It depends on where the team works. Inside HubSpot, Message IQ follows your HubSpot user and team permissions, so an owner sees only the conversations tied to the records they already have access to. The standalone Smart Ramp app does not apply those limits, so teams that need strict separation by location should work from the HubSpot portal. The shared inbox also supports conversation assignment and filters for unread, read, unreplied, sent, starred, and closed.

That is common in multi-location businesses, and the contact record stays shared. Working inside HubSpot, visibility can be filtered by the phone number that sent or received the message, so each location sees the thread tied to its own number. The standalone Smart Ramp app does not apply that filter, and a user there sees every message on the account. If shared contacts are normal for you, give each location its own number and keep day to day work in the HubSpot portal.

Yes. Active and static HubSpot lists work as SMS audiences without an export. Active lists update on their own, so the audience stays accurate as leads convert, customers cancel, or records change.

Anything you already track in HubSpot. Lifecycle stage, location, service or class type, day of week, owner assignment, and any other property or list criteria can define an audience. The segmentation lives in HubSpot, so there is no second set of lists to maintain.

The reply lands in the shared inbox as a one to one conversation and logs to the contact record, so a person can continue the conversation. Opt-out keywords are handled for you: STOP, UNSUBSCRIBE, QUIT, and CANCEL confirms the opt-out property on the contact, and that property can suppress any further messages. For an ordinary reply, such as someone asking to move a time, received messages generate a native HubSpot event. You use that event to unenroll the contact from the active workflow. It is a one time build in HubSpot rather than something you manage message by message.

The SMS step lives in a HubSpot workflow, so HubSpot’s own enrollment rules control it. When a contact meets your customer criteria, standard un-enrollment and suppression settings remove them from the nurture workflow and your customer workflow takes over. There is no separate audience to keep in sync in a second system.

Delivered, failed, and received messages generate native HubSpot events. That means SMS reporting happens inside HubSpot’s own reporting tools, next to the rest of your data, instead of in a separate dashboard. Because the events are native, you can report by owner, team, or location the same way you report on anything else in the portal. Message counts and average response time are built there rather than shipped as a fixed report inside Message IQ, which can be set up up front and gives you reports that match how your business is organized. Link clicks are written back to the contact record through IQ Link Tracking.

No. IQ Autoscaling supports one business number at any volume. Separate numbers by rep, team, or location are available, and they are what makes visibility filtering by number work when the same contact belongs to more than one location.

Outbound messages are scanned for reply-STOP language, and the required text is added when it is missing. STOP, UNSUBSCRIBE, QUIT, and CANCEL set the opt-out property on the contact record. Delivery, bounce, unsubscribe, and line type data sync back to the contact. 10DLC brand and campaign registration is handled for you at setup.

Accounts are usually live within one business day, and brand registration often clears the same day. Campaign approval will take about two weeks. The Campaign timeline is set by the carriers, not by us.

Plans are month to month with no contract. Every plan includes every feature and unlimited users, so you are not paying by owner or by staff member. Pricing is based on message volume. Current rates are on the pricing page.

Message IQ sends to numbers in the United States and Canada. There is no international messaging support today. Where your staff is located is a separate question, and there is no restriction there. A team member working outside the United States can send and reply like anyone else.