Xsquare Technology

Log Twilio Calls and Texts in HubSpot, Salesforce or Zoho

Here’s a problem we hear from small sales and service teams all the time: the calls and texts happen in Twilio, but the customer record lives in the CRM. Someone has to copy notes across by hand, or nobody does, and the next person who talks to the customer has no idea what was said last week.

This post explains what a good Twilio-to-CRM connection looks like, the three ways to build one, and what HubSpot, Salesforce and Zoho each offer. Vendor details were checked against HubSpot, Salesforce, Zoho and Twilio documentation on 15 November 2026. Products and plans change, so confirm on the linked pages before you choose.

What “good” looks like

Before picking tools, agree on the result you want. For most teams it comes down to five things:

  1. Match on phone number. Every call or text is matched to a contact using the phone number, stored in one consistent format (E.164, for example +14155550123). Decide what happens when there’s no match: create a new contact, or log the activity somewhere for review.
  2. Write an activity, not just a note. A call should appear as a call (direction, duration, outcome, who handled it) and a text as a message, on the contact’s timeline.
  3. Recordings and message bodies only where allowed. Store call recordings or SMS text only if your account settings, your customers’ consent and the laws you work under allow it. Many teams store a link to the recording instead of the file.
  4. Trigger texts from CRM events. A deal stage change, a booked appointment or a new lead can send an SMS through Twilio.
  5. One owner for opt-outs. If someone texts STOP, the CRM should know, so nobody sends a campaign to them by mistake.
How a Twilio to CRM integration logs a call or SMS: webhook, match contact by phone number, write activity, follow-up

Three ways to connect Twilio to a CRM

1. A native or marketplace connector

Some CRMs have a Twilio connection built in, and most have third-party apps in their marketplace. This is the fastest route when it covers what you need. The trade-off is that you get the connector’s idea of how calls and texts should be logged, and you may pay a per-user fee for the app on top of your CRM and Twilio costs.

2. Zapier or a similar automation tool

For simple, one-way rules, such as “when a text arrives in Twilio, add a note to the matching contact” or “when a deal moves to Won, send a thank-you SMS”, an automation tool works without code. We’ve written about this in automating customer engagement with Zapier and Twilio. It gets harder when you need phone-number matching with fallbacks, two-way sync, or call logging with recordings.

3. A custom integration in your own Twilio account

A developer writes a small service that receives Twilio webhooks for calls and messages, looks up the contact through the CRM’s API, and writes the activity. It also listens for CRM events and sends messages. This gives you exactly the logging rules you want, keeps everything in your own Twilio account, and avoids a third-party app sitting between your two systems. The cost is development time and someone to maintain it.

A typical custom integration has four parts: a webhook endpoint for Twilio call and message events, a lookup that matches the phone number to a CRM contact, a writer that creates the call or message activity, and a small queue that retries if the CRM API is briefly unavailable. Twilio signs its webhook requests, so the endpoint should validate that signature before trusting the data.

Three ways to connect Twilio to a CRM compared: marketplace app, Zapier-style automation, custom integration

HubSpot

HubSpot gives you several routes:

  • Twilio Connect for calling. HubSpot’s knowledge base describes connecting a Twilio account so users with a Sales Hub or Service Hub Professional or Enterprise seat can make calls in HubSpot using Twilio minutes, with recordings available in HubSpot. HubSpot says it doesn’t charge extra for minutes bought through Twilio Connect, and it isn’t available on a HubSpot trial.
  • Calling apps from the App Marketplace. HubSpot supports third-party calling providers listed in its marketplace.
  • The Calling Extensions SDK. For a custom calling app, HubSpot’s Calling Extensions SDK lets your app appear inside HubSpot on a CRM record. HubSpot creates a call engagement on the record’s timeline and your app fills in the details. An app built for your own team doesn’t have to be listed publicly.
  • Logging texts. HubSpot’s Communications API can log SMS, WhatsApp and LinkedIn messages and associate them with a contact, so a custom integration can write Twilio texts to the timeline.

Salesforce

  • Twilio Flex with Salesforce. Twilio documents a Flex integration for Salesforce that embeds the Flex agent interface with click-to-dial, screen pop and activity logging. It’s built on Salesforce Open CTI, and Twilio’s page warns that Open CTI is scheduled for retirement on 28 February 2028, after which those integrations stop working.
  • Partner telephony. Salesforce is steering voice integrations towards its newer partner telephony products, and Twilio documents a setup for Salesforce’s Partner Contact Center with Twilio as the telephony provider. If you’re starting fresh, ask about this route rather than building on Open CTI.
  • Custom logging. For a small team that just wants calls and texts recorded against contacts, a custom service using the Salesforce API to write activity records is often simpler than a full contact-center product.

Zoho CRM

  • Marketplace extensions. The Zoho Marketplace lists several paid, third-party Twilio SMS extensions for Zoho CRM, some with two-way messaging linked to records. Check who publishes each one, when it was last updated, and how it handles replies.
  • Build your own extension. Zoho publishes a tutorial on building a Twilio extension for Zoho CRM, for example to send an SMS when a lead is created.
  • Webhooks and workflow rules. Zoho CRM workflow rules can call a webhook, so a small service can receive the event and send a message through Twilio.

When a custom CRM is the better home for this data

If your team spends more time working around the CRM than in it, or you pay for seats mainly so people can see call history, it may be worth asking whether a lighter custom CRM would serve you better, with calls and texts built in from the start. We compare the options in custom CRM vs HubSpot or Salesforce, and you can see what we build on our custom web app and CRM development page.

FAQ

Does HubSpot work with Twilio?

Yes. HubSpot supports connecting a Twilio account (Twilio Connect) for calling on eligible paid seats, third-party calling apps, and custom calling apps built with its Calling Extensions SDK.

Can Twilio text messages be logged in HubSpot?

Yes, with an integration. HubSpot’s Communications API lets an app log SMS messages and associate them with contacts.

Is the Twilio Flex integration for Salesforce still supported?

Twilio’s documentation says it relies on Salesforce Open CTI, which is scheduled for retirement on 28 February 2028. Plan new builds with that date in mind.

Is there a Twilio integration for Zoho CRM?

There are third-party Twilio SMS extensions in the Zoho Marketplace, and Zoho documents how to build your own Twilio extension.

Should I use Zapier or a custom integration?

Zapier suits simple one-way rules. A custom integration suits phone-number matching, two-way sync, call logging with recordings, or rules that depend on your own data.

Want your calls and texts in your CRM?

Xsquare builds Twilio integrations in your own Twilio account. See our Twilio development services, or contact us and tell us which CRM you use and what you want logged.

Scroll to Top