What Click to Call Actually Logs in Your CRM, and Where It Stops Scaling

TL;DR:

Click to call turns a phone number shown inside your CRM into a one-click call, and it reaches the CRM one of three ways: the CRM's own calling, a browser extension, or a CTI embedded in the record by your phone system. The three write very different things back, and only one of them writes back enough to keep your reporting whole at volume.

• What a good click writes back: direction, duration, the line, a recording link, the disposition, notes, tags and an AI call summary. HubSpot stores it as a call engagement; Salesforce as a Task.
• The gap teams find late: in Salesforce a call log is captured only once a disposition, note or tag is added or updated after the call. A rep who hangs up and clicks the next number leaves a hole in the record.
• Click to dial is human initiated by definition. A person picks each number and clicks it. That is the point of it, and it is also the ceiling.
• The ceiling is a ratio, not a magic number. Across Aloware accounts in the year to 31 August 2026, counting every rep-placed dial, the median rep placed 19 to 27 outbound dials on a business day and the 75th-percentile rep 70 to 83.
• It breaks in three places at volume: throughput, wrap-up discipline, and number reputation. Hiya's 2026 State of the Call puts 86% of unknown calls unanswered, and clicking faster does not change that.

Your reps click a phone number inside HubSpot, the call connects, the recording lands on the contact, and nobody retypes anything. That is the whole promise of click to dial, and for the first few months it is completely true. Then the team doubles its dial count and the cracks show up in the report rather than on the phone. Dispositions go missing. Calls attach to the wrong object. The connect rate slides.

What is click to call, and what does it do inside a CRM?

Click to dial is a feature that turns any phone number displayed in your CRM into a link a rep can click to place a call from their computer, with the call and its outcome written back to that record automatically. It removes three steps from every dial: copying the number, switching to a phone app, and logging the outcome afterwards.

Those steps are not a small tax. Aloware's September 2026 analysis of 510 recorded sales conversations found double entry, meaning the dialer does not log to the CRM so reps retype everything, was the most-cited reason buyers were shopping for a new phone system, and HubSpot came up in 83 of the 510 calls. That analysis reads AI-written call summaries rather than transcripts, so take it as direction, not quotation.

Two terms get used interchangeably and should not be. Click to dial is the rep's action; a CRM dialer is the whole calling layer behind it, including lists, routing, recording and reporting. The CRM dialer guide covers the vocabulary in one place.

Whoever owns compliance will ask whether this counts as an auto dialer. Under 47 U.S.C. § 227(a)(1), an automatic telephone dialing system is equipment with the capacity to store or produce numbers using a random or sequential number generator and to dial them, and a rep clicking one chosen record is a different activity. Consent, do-not-call and calling-hours obligations still apply to every outbound call however it is placed.

What are the three ways click-to-call attaches to your CRM?

Every click-to-call setup is one of three attachments. Treat the attachment like the wiring behind a light switch: the rep flips the same switch every time, and what the wiring reaches decides what actually turns on.

The third is the only attachment where the CRM itself is a participant. HubSpot documents it for developers: the Calling Extensions SDK lets an app provide a calling option directly from a CRM record, and when a user makes a call, HubSpot creates an engagement on the activity timeline of that record and then exchanges data with the app to fill in the details. Aloware's HubSpot CTI app, currently in beta, is built on that framework, which is what lets it handle inbound calls inside HubSpot. Salesforce does the same job through an Open CTI softphone: with the Aloware Talk2 Dialer in place, a phone button appears wherever a number is displayed, in a record or a list view. What syncs sits on the HubSpot integration page and the Salesforce integration page. If your CRM already ships its own calling, the question is not whether it dials. It is which of the checks in that table you would still be buying separately.

A CTI also carries the two things reps ask about on day one. Inbound calls reach the right person: Aloware can route a caller to their HubSpot deal or contact owner, and in Salesforce an inbound call pops a notification naming the caller and the receiving line. And reps can text from the record they are calling from, through the Talk2 Conversation messenger in both CRMs.

Pick one owner per surface, in either CRM: inside HubSpot or Salesforce the CTI owns the click, and the extension is for pages outside the CRM. Aloware's own guidance for Salesforce says exactly that.

• Wrong: an extension and a CTI on the same Salesforce tab.
• Right: the CTI owns the click inside the CRM, the extension owns everything outside it.

What does a click actually write to the record?

Through a CTI like Aloware's, a click writes a complete activity record: who called whom, on which line, for how long, the outcome, a link to the recording, and a summary of what was said. That is the difference between a real integration and a logging checkbox, and it is the question buyers most often forget to ask on a demo.

In HubSpot, the call lands as a call engagement on the contact, carrying the recording URL, duration, disposition, HubSpot call type, and the AI call summary when AloAi Voice Analytics is running. Calls and texts also flow to associated Deals, Companies and Tickets, so activity shows up where the deal is worked. Structured call events, including call started, ended and disposed, can enroll a contact in a HubSpot workflow on uPro + AI and above, which is how a missed call becomes a task instead of a memory.

In Salesforce, the same call becomes a Task under the Contact or Lead, and under the Opportunity when that has been set up to match on phone number, carrying the timestamp, outcome, duration, direction, line, numbers, recording and voicemail links, tags, notes and the AI summary.

Two Salesforce behaviors belong on your evaluation checklist, because both are structural rather than fixable later:

• A call log is captured only when a disposition, note or tag is added or updated after the call. A bare call with no wrap-up leaves nothing behind. At twenty dials a rep remembers. At eighty, they do not.
• Call and message records bind to one object, Contacts or Leads, not both at once. If a Lead later appears with the same phone number as a Contact, future logs follow the Lead. Mortgage and solar teams hit this first, because in those funnels the duplicate is the norm.

• Wrong: wrap-up happens whenever, from memory.
• Right: wrap-up is one keystroke before the next dial, and the disposition fires the workflow.

Wrap-up does not have to run on memory, and you do not need a power dialer to fix it. Mandatory tags and dispositions come with the Core AI plans, and Aloware can require a HubSpot call type before a rep finishes a call, which turns the Salesforce logging rule from a discipline problem into a settings decision. Ask about it on the demo.

One consequence is worth settling before rollout: with call recording on, a CTI records every call it places, so recording-consent rules in the states your reps dial into become a standing setting rather than a per-call decision. Name who owns that check.

Where does click-to-call break at volume?

Click to dial does not fail loudly. It stops paying for itself, in three places at once.

1. Throughput. The click is cheap. The gaps around it are not: find the record, read it, click, wait for ring-out, mark the outcome, return to the list, scroll, find the next record. Across Aloware accounts in the year to 31 August 2026, counting every rep-placed dial whether it came from a click or a dialer session, the median rep placed roughly 19 to 27 outbound dials on a business day, while the 75th-percentile rep placed 70 to 83, and half of connected outbound calls ended inside 66 seconds. Do the arithmetic on a rep placing 80 dials: at the 16.7% to 20.4% outbound connect rate those accounts run at, that is 13 to 16 conversations out of 80 attempts, and half of those conversations are over inside 66 seconds. The other 64 to 67 attempts still cost their full navigation, ring-out and wrap-up time. (Aloware first-party data, rep-days with an assigned user, twelve months to 31 August 2026. Test, demo and internal accounts excluded, auto-dialer traffic with no assigned user excluded, medians interpolated in ten-dial bins, connected calls carrying a definitional floor of 30 seconds of talk time. The 16.7% to 20.4% band is a tenure cross-section across a sample of 1,229 accounts, not one cohort followed over time, and long-tenured accounts dominate its top bucket.)

2. Wrap-up discipline. Every logging behavior above depends on a human finishing the call properly. That assumption holds at twenty dials and quietly collapses at eighty, and the damage stays invisible until a manager reports on outcomes and finds calls with no disposition.

3. Number reputation. More dials from the same number means more unanswered calls and more declines, the exact pattern carrier analytics score against a line. Hiya's 2026 State of the Call reports that 86% of unknown calls go unanswered. Clicking faster raises the number of unknown calls you place; it does nothing to make them known. That repair is a separate layer of work, covered in how to double your call pickup rates.

• Wrong: dial harder from the same number.
• Right: repair the number's standing, then raise the dial count.

So here is the threshold, without hedging:

• Under about 30 dials per rep per day, on one CRM, which is just above the 19 to 27 a median rep places. Click to dial with a proper CTI is the entire answer. Do not buy a power dialer. Spend the money on making the wrap-up write.
• Roughly 30 to 70 dials per rep per day. Throughput is not your problem yet. Patchy dispositions and numbers starting to get labeled are. Fix logging first, because a disposition nobody captured cannot be recovered, then caller reputation, because that takes weeks to repair once it slips.
• Above roughly 70 to 83 attempts per rep per day. That is where Aloware puts the handoff, and the reason is the arithmetic above rather than the percentile: at that volume the fixed cost of finding, clicking and dispositioning each record takes more of the shift than the conversations do.

Key takeaway: the ceiling on click to dial is not the software, it is the human action attached to every single dial. When navigation and wrap-up take more of the day than the conversations do, the click is the bottleneck.

When does a power dialer take over from click to dial?

A power dialer removes the two steps click to dial leaves behind: choosing the next record and navigating to it. Aloware's Power Dialer works a list one contact at a time and advances automatically, and the CRM record travels with the session: HubSpot users get the HubSpot record inside the dialer, Salesforce users get a popup that refreshes to the next contact.

Four things change for the team, and they are the reason to move rather than the marketing:

• No-answers get a second attempt without a decision. A require-agent-redial setting enforces a redial of contacts who did not answer the first time and removes the warm-up wait between attempts.
• Wrap-up stops being optional. Dispositioning happens inside the session, in the same window as the record, closing the logging hole above.
• The list comes from the CRM, not a spreadsheet. A HubSpot list or a filtered Salesforce list view imports straight into the dialer, so the session works the same segment the CRM defines.
• Manual and dialer activity separate in the reporting. The Power Dialer report compares power-dialer calls against manually placed calls by user and by team, which is how you see whether reps actually adopted it.

On plans: the Power Dialer sits on the uPro + AI plan at $60 per user per month on the quarterly plan, or $70 month to month, and power-dialer sessions bill as agent calls, so rep-dialed calls to the US and Canada are unlimited on the Core AI plans. The answer-rate layer, the Pickup Stack of NumberGuard, Branded Calling and Local Presence, is a paid add-on priced separately from the seat and never part of a plan price.

Two honest limits, because they decide fit faster than any feature list. Aloware does not build a parallel or predictive dialer, deliberately: multi-line dial-ahead pacing produces abandoned calls and dead air, the signature carrier analytics score against a number, so the answer-rate problem gets worse while the dial count improves. Buyers whose hard requirement is maximum simultaneous dials go with a vendor built for that; teams measured on connect rate get more out of a single-line dialer plus the Pickup Stack. Second, a power dialer will not rescue bad data. It will burn through it faster.

How do you test click to dial on a demo?

Twenty minutes on a screen share will tell you more than any feature grid. Ask the vendor to do these seven things, in this order, on their own system:

1. Dial from a list view, not a record page. An integration that puts the call button only on the record page breaks the workflow of any rep working a filtered list.
2. Hang up without dispositioning, then open the record. Ask what got written and what did not. This one test separates real logging from a checkbox.
3. Ask which object the call attaches to when a Lead and a Contact share a phone number. A vendor who has thought about it will tell you the rule.
4. Find the recording link and the call summary on the CRM record, not in the vendor's app. If a rep has to leave the CRM to hear a call, nobody hears the call.
5. Ask what fires a CRM workflow: the call ending, or the call being dispositioned. Then ask where talk time comes from. Without that, your follow-up automation runs on guesses.
6. Ask which plan the CTI, the dialer and the analytics each sit on. Get it in writing. The click is usually the cheap part.
7. Ask who watches the outbound numbers, and what happens the day one gets labeled as spam. With 86% of unknown calls going unanswered, silence here is the most expensive answer on the list.

The bottom line

Click to dial is not a dialer. It is a shortcut, and a good one: it collapses three steps into one and puts the call on the record while the rep is still on it. For a team calling a couple of dozen leads a day out of one CRM, that is the whole answer, and buying anything heavier is buying a problem you do not have.

What it cannot do is carry a team past its own throughput. Pick the attachment that writes the most back to the record, watch dials per rep against dispositions per rep, and move when those two lines stop tracking each other.

If you are running outbound inside HubSpot or Salesforce, book a demo. We will run the seven tests above on your own CRM, with the Power Dialer and AloAi Voice Analytics in the record.