Choose the HubSpot inbox
Connect each Twilio number to the HubSpot conversations inbox your team already uses. Multiple numbers can stay separate and clearly named.
HubSpot integration
HubSpot Twilio SMS Integration
Connect a Twilio number to the HubSpot inbox your team uses for customer conversations, and text contacts straight from their HubSpot record. TryWired matches contacts by phone, keeps inbound and outbound messages on the same thread, logs the activity, associates related CRM records, and carries supported MMS files.
Start nowRead the setup guideHow the connection works
Connect a Twilio phone number and choose the HubSpot conversations inbox where its SMS and MMS threads should appear.
Start a conversation first: an embedded TryWired card on the HubSpot contact record lets your team text a contact without waiting for an inbound message.
Match the sender by phone number and create a HubSpot contact only when no existing record matches.
Record inbound and outbound direction accurately and send HubSpot replies through the original Twilio number.
Transfer supported MMS media with the conversation and keep communication activity associated with related contacts, companies, and deals.
Pricing
$35/mo, first channel
then $28/mo per additional channel · cancel anytime
What HubSpot receives
The message arrives with the context your team needs.
The integration keeps the channel conversation connected to the inbox, contact, CRM timeline, related records, and files instead of leaving your team with a loose copy of the message.
Match or create the right contact
TryWired looks up the sender before creating anything new. The sender's E.164 phone number is the contact identity, so an existing HubSpot record is reused whenever the number matches.
Keep both directions on one thread
Incoming messages and HubSpot replies stay tied to the original conversation. Direction, timestamps, participants, and thread history remain clear in HubSpot.
Start the conversation from the CRM
An embedded TryWired card on the HubSpot contact record lets your team send the first message without waiting for an inbound one. The outbound-first thread is logged and continued just like any other.
Log the conversation on the CRM timeline
Each conversation is logged as HubSpot communication activity and associated with the contact, plus any companies and deals already connected to that contact.
Carry files and context with the message
Photos, documents, and other supported files move between the channel and HubSpot. Conversation history and internal thread comments stay available to the team.
Stay aligned through interruptions
TryWired keeps a durable record of inbound and outbound messages, preserves their original channel IDs, and prevents duplicate deliveries from becoming duplicate CRM activity.
What to know before connecting it
HubSpot plan and inbox access
HubSpot currently supports custom inbox channels on Sales Hub Professional or Enterprise and Service Hub Professional or Enterprise. An admin with Account Access chooses the conversations inbox during setup.
Proactive messaging from the contact record
TryWired embeds an SMS card as an iframe on the HubSpot contact page. An admin adds it once through record customization, and after that any user with access to the record can open the card and send the first message using the contact's phone number and your connected Twilio number. The thread continues in the HubSpot inbox you selected, so an outbound-first conversation is logged the same way an inbound one is.
Delivery status stays in Twilio
Twilio sends delivery and failure callbacks to TryWired for operational tracking. The current HubSpot view shows the conversation, direction, and attachments; it does not yet provide a customer-facing delivery-status view. Delivery receipts remain available in Twilio.
Consent and opt-outs remain your responsibility
TryWired does not replace your consent process or Twilio's sender and opt-out configuration. Keep consent records in the system your team uses and configure Twilio for STOP handling, sender registration, and the rules that apply to your countries and message types.
Channel-based pricing, no per-message charge
TryWired starts at $35/month for the first Twilio number and $28/month for each additional number. There is no per-seat charge and no per-message charge from TryWired. Twilio bills its own messaging and carrier fees in your Twilio account.
Common questions
A few practical details
Can we text a contact before they message us?
Yes. Add the TryWired SMS card to your HubSpot contact record and your team can send the first message from the contact page. The card runs as an iframe inside HubSpot, uses the contact's phone number and your connected Twilio number, and puts the outbound message on the same thread that later replies arrive on. Consent and sender rules still apply to messages you initiate.
Can the integration send and receive MMS?
Yes, for supported media and Twilio numbers with MMS capability. TryWired captures inbound media with the message and can send supported HubSpot attachments back through Twilio.
How are contacts matched?
The sender's E.164 phone number is used as the contact identity. TryWired reuses a matching HubSpot contact or creates one when no match exists.
Does HubSpot show whether an SMS was delivered?
Not yet. Twilio delivery receipts and errors remain visible in Twilio. TryWired receives status callbacks for operations, while HubSpot shows the message thread, direction, participants, activity, and files.
More channels
Other HubSpot integrations
TryWired also supports these connections.
Talk through your HubSpot setup
Tell us which channel account and HubSpot inbox you use. We will confirm the fit atsupport@trywired.io.