Call activities
Direction, duration, the user who handled it and the outcome, logged as a call engagement on the contact and associated deal.
CRM
Sales and service teams already work in HubSpot. This integration takes the calls, voicemails and text messages that happen on 3CTel and writes them to the matching contact and deal, so the timeline is complete without anyone typing it in.
The HubSpot integration sends 3CTel call, voicemail and SMS events to HubSpot and logs them as activities on the matching contact, company or deal. It is delivered through 3CTel's API and webhooks, either directly or through an automation platform, depending on your HubSpot subscription and existing tooling. The approach is confirmed with you during planning and availability is verified before activation.
Last updated:
Direct API and webhooks, or your existing automation platform.
Your HubSpot administrator approves the app and the objects it may write to.
3CTel users to HubSpot owners, phone properties, and the rule for unknown callers.
Test contacts and a temporary number confirm logging before live numbers move.
There is no single HubSpot integration that fits every account, so 3CTel scopes one of two delivery paths with you.
| Path | How it works | Usually chosen when |
|---|---|---|
| Direct API and webhooks | 3CTel sends call and message events to HubSpot's API and creates engagements on the record matched by phone number | You want the simplest setup and have no automation platform in place |
| Automation platform | 3CTel webhooks feed a workflow tool you already run, which transforms events and writes them to HubSpot with your own rules | You already route data through an automation platform, or you want custom deal logic and notifications |
Reliable calling with routing your team will actually use.
Learn more: Business PhoneText from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSSee what your phone traffic is actually doing — and staff for it.
Learn more: Call AnalyticsDirection, duration, the user who handled it and the outcome, logged as a call engagement on the contact and associated deal.
A voicemail creates a note on the contact with the transcript and a reference to the recording held on 3CTel.
Inbound and outbound business texts are logged to the contact timeline so a rep sees the whole exchange before calling back.
Optional. A call from an unrecognised number can create a contact with the number and the menu option the caller chose.
3CTel does not replace HubSpot's own calling feature or its subscription decisions. It records what happens on your business phone system in the CRM you already use.
Someone who can create or approve an app in your HubSpot account and decide which objects 3CTel may write to.
Most business subscriptions do. API limits vary by tier; the specialist checks yours before recommending a path.
Matching depends on consistently formatted phone numbers. A short clean-up of contact phone fields is often the first task.
Create a contact, log to a holding record, or ignore. The choice is yours.
The specialist confirms the delivery path, your administrator authorizes the connection, and mappings are agreed: which 3CTel user maps to which HubSpot owner, which properties hold the phone number, and what an unknown caller should do. The integration is tested on a temporary number with a few test contacts before live numbers move. Nothing is billed before activation.
Click-to-call from HubSpot records is scoped where the direct API path is chosen and your browser setup supports it. The call is placed from the rep's 3CTel app and shows the business number. Where it is not practical, reps dial from the app and the call is still logged to the record automatically.
The call is matched to a contact by phone number first. If that contact has open deals, the activity is associated with them by a rule agreed at setup, such as the most recently updated deal. On the automation-platform path you apply your own rules, for example only associating calls with deals in certain stages.
Yes, if you want them to. A missed or abandoned call can be logged as a call activity with a missed outcome, and on the automation-platform path it can also create a task for the owner or send a notification. Many teams use this to make sure every missed call from a known contact gets a callback.
Call and message data pass between 3CTel and HubSpot, and through your automation platform where that path is chosen. Recordings stay on 3CTel; HubSpot receives a reference, not the audio. Retention on 3CTel is configured with you. Revoking the HubSpot connection stops logging without affecting phone service.
Reliable calling with routing your team will actually use.
Learn more: Business PhoneText from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSSee what your phone traffic is actually doing — and staff for it.
Learn more: Call AnalyticsQueues, routing and supervision for teams that live on the phone.
Learn more: Contact CentreThe phone workflow behind a support desk that answers, follows up and improves.
Learn more: Customer serviceNo. It logs calls made and received on 3CTel, with your business numbers, queues and recording, into HubSpot records. Some teams keep both.
A tier with API access for a private or connected app. The specialist confirms your subscription and API limits before recommending a path.
Yes. When a contact is matched, the activity can also be associated with the company record and open deals under the rules set during planning.
It is scoped per account and the delivery path is confirmed during planning. Availability is verified with you before activation and nothing is billed until then.
Tell us which objects should carry call activity and what an unknown caller should trigger. A specialist confirms the delivery path and quotes it before activation.