What actually gets logged in HubSpot when a message arrives
Contact matching, thread continuity, CRM activity, associations, and files. A step by step account of what happens between an inbound message and your CRM.
“It syncs to HubSpot” covers a lot of ground. At one end that means a message body pasted into a note. At the other it means a conversation your team can still work from six months later. The difference comes down to what happens in the couple of seconds between a customer hitting send and something showing up in your CRM.
Here’s that sequence.
1. The message arrives
An inbound Telegram message or SMS reaches the integration through the channel’s webhook. It brings a channel-native identity with it, either a Telegram username and user ID or a phone number, plus the message body, any attachments, and a timestamp.
Nothing has touched HubSpot yet.
2. The sender is matched to a contact
This step decides whether everything after it is useful.
For SMS the identity is the sender’s phone number in E.164 format. For Telegram it’s the username or user ID. Either way, it gets looked up against your existing contacts first.
If a contact matches, the conversation attaches to that record. No duplicate, no second copy of a customer you already know.
If nothing matches, a contact is created from the channel identity. That matters more than it sounds. A big share of Telegram users will never give you an email address, and a CRM that can only create contacts from email addresses just can’t hold them. Matching on channel identity means the conversation doesn’t depend on information the customer hasn’t given you.
3. The conversation is published to an inbox
The message gets published to whichever HubSpot conversations inbox you picked for that channel during setup. It shows up as a thread alongside email and chat, in the place your team already works.
Which inbox is a per-channel choice. A support bot and a rep’s personal account can feed completely different inboxes, with different routing and notification rules on each.
4. Both directions stay on one thread
When someone replies from HubSpot, the reply goes out through the original channel, the same Telegram account or the same Twilio number, and stays on the same thread.
Direction, timestamps, and participants stay accurate. Six months later it’s still clear who said what, in what order, and which side started it. Sounds obvious, and it’s exactly what falls apart in setups that treat inbound and outbound as separate events.
5. Activity lands on the timeline
The conversation is recorded as HubSpot communication activity on the contact’s timeline, sitting with the emails, calls, and meetings rather than in a parallel system somebody has to remember to check.
It’s also associated with companies and deals already linked to that contact. Teams underestimate this one. A support conversation that surfaces on the deal record changes what your account manager knows walking into a renewal call, and nobody had to link anything by hand.
6. Files move with the message
Photos and documents transfer both directions. Support conversations are mostly screenshots, an error message, a receipt, a photo of something broken, so a text-only bridge throws away most of the actual content. Supported MMS media works the same way on SMS.
7. Duplicates get prevented
Every message keeps its original channel ID, direction, timestamp, and HubSpot thread. If a delivery gets retried after a brief interruption, that record is what stops the same message becoming two pieces of CRM activity.
Invisible when it works, very obvious when it doesn’t. Duplicate activity is corrosive. It makes timelines untrustworthy, and once a team stops trusting the timeline they stop reading it.
What doesn’t get logged
Worth being straight about the edges.
SMS delivery receipts stay in Twilio. Status callbacks come through for operational tracking, but HubSpot shows the conversation, direction, participants, activity, and files rather than a customer-facing delivery view. Whether a specific message reached the handset is a question for Twilio.
Data doesn’t pile up forever. Message and webhook data is deleted after 30 days. Only what’s needed to route the conversation is kept, and nothing sits in our systems longer than that.
What you end up with is a CRM record that answers “what happened with this customer” without anyone reconstructing it from three different tools. To see it against a specific channel, the Telegram and Twilio SMS pages break it down per integration, and the FAQ covers what teams usually ask before connecting.