HubSpot telephony and SMS integration.
Every call on the record. Aircall, RingCentral, Twilio, Dialpad, Kixie, Salesmsg, Sakari, Ringover, 3CX — whichever one you run, the job is the same. The call, its outcome, its recording and every SMS thread belong on the contact record, and the activity has to be reportable.
Four hundred dials, and the CRM saw nine.
Reps call from the phone system and log the ones they remember. Activity reporting is therefore a measure of how conscientious somebody is about admin, not of how much work they did, and every coaching conversation built on it starts from a false number.
Logged by hand, or not at all.
Telephony — the missing activityWhat a marketplace app does not cover.
Matching a number to a record
Numbers arrive in a dozen formats and a contact has three of them. Normalisation and a matching strategy, including what happens on no match, decide whether activity lands or disappears.
Outcomes, not just duration
A call log with a duration is not data. Structured outcomes and dispositions written back as properties are what make connect rate and conversation-to-meeting reportable.
Recordings, transcripts and retention
Where recordings live, who may listen, and how long they are kept are compliance questions. Two-party consent states and recorded-call disclosure get designed in rather than bolted on.
SMS consent is not email consent
Messaging consent is separate, regulated differently, and needs its own opt-out handling. A single unsubscribe property covering both is a compliance problem waiting to happen.
Power dialling against a list
For outbound teams, the queue has to come from a HubSpot list and write back in real time, or the dialler and the CRM immediately disagree about who has been called.
Voicemail, missed calls and routing
Inbound calls that nobody answered are the most commonly lost signal in a revenue system. They become tasks with an owner rather than a line in a phone system report.
Built to a contract, not to a connector.
Draw the boundary
Which system owns which field, in writing, before a line of code. Most broken integrations are two systems both believing they are the source of truth.
Model the join
The key that matches a record on one side to a record on the other, and the rule for what happens when it does not match — because it will not match.
Build and instrument
Sync built with retries, idempotency and a dead letter path, plus logging you can read without opening a console.
Reconcile
Counts compared on both sides on a schedule, with a report that names the drift rather than a green tick that hides it.
Hand over
A runbook covering the three failures that actually happen, so the next person does not have to reverse-engineer the design from the logs.
Activity goes up. Nothing else moves.
Wiring the phone system in makes dial counts visible and tempts everyone to manage to them. The useful metrics are connect rate, conversation to meeting, and meeting to opportunity. We build the reporting around those, because dials are an input and nobody ever closed one.
What people ask before they commit.
Which phone systems do you work with?
Aircall, RingCentral, Twilio, Dialpad, Kixie, Salesmsg, Sakari, Ringover, 3CX and most others with a usable API. Several have marketplace apps that cover the basics, and we build the part they do not.
Do call recordings sync to HubSpot?
They can, and whether they should is a retention and privacy decision rather than a technical one. Often the right answer is a link to the recording plus a transcript summary on the record.
Can we send SMS from HubSpot?
Yes, through the platform you already pay for, with messages on the timeline and workflow-triggered sending. Consent and opt-out are handled as a separate property set from email.
What about compliance?
Recorded-call disclosure, two-party consent states, quiet hours and messaging opt-out all get designed into the build. This is the part that gets skipped and it is the part with legal consequences.
How long does it take?
One to four weeks for most implementations. A custom Twilio build with power dialling and bespoke routing sits at the longer end.
Where people go from here.
Every dial, every thread, on the record.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.