Dialpad Integrations: Which CRMs Sync on Which Plan

For Salesforce you need Dialpad Connect Pro or Enterprise, or a Support or Sell plan; Standard does not list CRM integrations. HubSpot works on any Support or Sell plan and on Connect Pro or Enterprise. Pro is $25 per user a month with annual billing, so the CRM link costs $10 more per seat than Standard ($8 on monthly billing).

Two catches change the answer. Salesforce must be Enterprise or Unlimited edition, or another edition with API access. And on Connect, Zapier and the open APIs also start at Pro, so a Standard account has no automated route into a CRM at all, not even a workaround. Everything here comes from Dialpad's pricing page and help centre, read on 5 November 2026, and where a page was silent I say so rather than guess.

Follow me on Instagram@sagnikteaches

The plan ladder for CRM sync

Dialpad sells three seat-based products, and the CRM question is answered differently in each. Connect is the general business phone, Support is the contact-centre product, and Sell is the outbound sales product. For the full role-by-role test, see choosing between Connect, Support and Sell; here the only question is the CRM link.

Connect on LinkedInSagnik Bhattacharya

Where the cells come from: the Connect rows are the "Integrated apps and APIs" block of the plan table on Dialpad's pricing page, which ticks Salesforce, HubSpot, Zapier, Zendesk, ServiceNow, Slack, Microsoft Teams and the open APIs on Pro and Enterprise but not on Standard (Google Workspace is ticked on all three). The Support and Sell rows come from the help centre. The Salesforce install guide says the integration is free to install but needs a Connect, Support or Sell licence; the HubSpot articles say it is available to Support and Sell customers and to Connect users; the Zapier article names Connect Pro or Enterprise plus any Sell or Support licence; and the Zoho article says "eligible" Sell, Support and Connect users without defining eligible. That last word is the one to put to your rep in writing. A line in an email costs nothing and settles a dispute later.

Subscribe on YouTube@sagnikteaches

What the Salesforce link does

Dialpad's help centre describes the Salesforce integration as working with both Sales Cloud and Service Cloud. The requirements are specific: Enterprise or Unlimited edition (or another edition with API access), the latest Dialpad package from the AppExchange, API access switched on, and a Salesforce System Admin profile to install it. Calls log to the matching Salesforce record, reps can place Dialpad calls from inside Salesforce, and the help centre notes that automatic logging counts against your Salesforce API call limits, which an admin can see under Setup, Monitor, System Overview.

Two limits are easy to miss. In the Classic version of the integration, calls placed from a shared line, such as a department, main line or contact centre, are not logged; only calls from a person's direct line are. And list dialling inside Salesforce, the Powerdialer, is marked in the help centre as a legacy feature for Sell licences, being replaced by the newer Dialpad Dialer, with agents assigned to a contact centre. If your plan depends on either, test it in the trial. Fix your data first, too: standardise phone formats and merge duplicates in Salesforce, then connect, and check where a call from a number stored on two records ends up.

What the HubSpot link does

Dialpad's help centre says the HubSpot integration needs a HubSpot Sales Hub account at any level (Free, Starter, Professional or Enterprise) and someone with Super Admin or App Marketplace access to install it. Once connected, it logs inbound and outbound calls automatically, lets users add notes, tasks, deals and dispositions from the Dialpad sidebar, supports calling from inside HubSpot, and embeds the recording if HubSpot's "Make call recordings playable inside HubSpot" setting is on. Calls between colleagues in the same company are not logged.

Matching is where small teams trip. Dialpad looks for a HubSpot contact by phone number, email or name, and the phone number must be stored in a local or E.164 format (plus sign, country code and number, no spaces) to match. When several contacts match, Dialpad's main HubSpot article says it creates a new contact and logs the call there. For a number that matches nobody, the same article says it creates a contact, while the migration guide for the current version says automatic creation for unknown numbers was removed. Test both cases before go-live rather than trusting either page. Contact syncing from HubSpot into Dialpad is now an admin setting, and it runs one way only, from HubSpot to Dialpad.

Where the AI summary ends up

This is the point owners ask about most, and the help centre now answers it. In Salesforce, Dialpad writes the AI Recap into an "AI Summary" rich-text field, alongside AI Action Items, the AI Outcome and the Call Purpose (plus playbook adherence and an AI CSAT score if you pay for those modules). The catch: summaries and action items do not show on Salesforce Tasks until an admin adds the Dialpad AI component to the Task page in the Lightning page editor.

In HubSpot, the same fields are logged as custom fields on the call when the "Add AI-generated data to HubSpot activities" setting is on, but the AI Summary field has a 255-character limit, roughly two sentences. Treat it as a pointer to the full recap in Dialpad, not the whole record. For Zoho, a "Post AI-generated data to Zoho" setting adds an "AI Assets & Call Info" note to each call. In every case Dialpad AI has to be enabled on the call for a summary to exist.

Then test, because settings drift. Make a call between two team members on a test contact, hang up, wait for the recap, then open the contact in the CRM and note what appears: the log entry, the recording, the summary field, the action items, or nothing. Repeat from a second user. Write what you see on one page and keep it; it becomes your reference when someone says "the notes stopped appearing".

If you want to know how Dialpad's AI features sit across plans, the AI answering tutorial covers summaries and credits, and the five-seat cost tutorial prices the seats.

Pricing a pest-control firm's Salesforce link

Illustrative figures. A pest-control firm has eight office and sales staff and keeps its leads and recurring treatment plans in Salesforce. Four people take inbound enquiries, two chase quotes, and two handle renewals. All eight are on Connect Standard at $15, a monthly cost of $120.

The firm's complaint is that call notes live in people's heads. Quotes get chased twice or not at all. The owner wants every call attached to the lead. The step-by-step:

1. Confirm the Salesforce edition supports API access. The firm is on Enterprise edition, so the answer is yes.
2. Move the eight seats to Connect Pro: 8 x ($25 - $15) = $80 more a month, $960 more a year. Seats who do not touch Salesforce, such as a future technician seat, could stay on Standard if Dialpad lets one account hold both plans; ask before you assume it.
3. Have a Salesforce System Admin install the latest Dialpad package from the AppExchange, assign the administrator and standard-user permission sets, and connect it to the Dialpad account.
4. Add the Dialpad AI component to the Task page, then run twenty test calls across both lead and contact records, including numbers that match two records.
5. Switch on for all eight on a Monday and ask each person to check their first five calls on Tuesday.

The decision sum: if each of the two quote-chasers loses four chasing slots a week through bad notes, that is eight missed follow-ups a week. At a conservative one conversion in twenty and $400 average job value, eight chases are worth 8 x 0.05 x $400 = $160 a week, about $8,320 a year, against $960 for the upgrade. The sum rests on illustrative rates; swap in yours, and if the answer is a few hundred dollars either way, a cheaper route (below) may be better.

Example: a roofing company with HubSpot

A roofing company has three estimators who live in HubSpot, a two-person office and the owner. HubSpot Sales Hub is already in use, and Dialpad's help centre says any Sales Hub level qualifies, Free included. The estimators make about fifteen calls a day from the Dialpad app on their mobiles and want them logged. The help centre lists HubSpot for Sell customers, and Sell Essentials is $39 a seat, against $25 for Connect Pro. The sum: Sell for three estimators costs 3 x $39 = $117, Connect Pro 3 x $25 = $75, a $42 monthly gap.

The estimators do not run calling lists, so Connect Pro covers the need, saving $504 a year. If the owner later wants voicemail drop or live coaching, Sell Advanced (9), which includes both, becomes worth pricing. Read our power dialler pricing tutorial before that step.

Before and after: a record that stops being empty

Before: a contact called "[first name]" in the CRM has a created date, a phone number and a single note typed three weeks ago: "interested, ring back". After: the same contact shows an inbound call at 09:14, a 4-minute duration, the recording, and a two-sentence AI summary; the next three outbound attempts are logged automatically, including one voicemail. Nothing about the person changed. What changed is that the history stopped depending on someone remembering to type.

That is the whole value of the native link. Where it breaks is the first day: if the CRM's phone field holds numbers typed with words, extensions or odd spacing, such as "0155 555 0100 (mobile)", matching can fail. Dialpad's HubSpot article asks for numbers in local or E.164 format. Check the format on ten records before going live.

The Zapier route for CRMs without a native link

Zapier is not a way round the Connect Standard restriction. Dialpad's help centre says its Zapier integration is available on Connect Pro or Enterprise and to anyone with a Sell or Support licence, which is the same set of plans that gets the native links. Where Zapier earns its place is a CRM or job-management tool that Dialpad does not connect to natively; the help centre's own example is Pipedrive, linked through Zapier. Dialpad gives Zapier two triggers, Call State Changed and SMS Created, and the admin picks the scope: the whole company, a contact centre or a department.

The costs sit on Zapier's side. Zapier's pricing page lists a free plan with 100 tasks a month and two-step Zaps only, and paid plans from $19.99 a month. Triggers do not use tasks; each successful action does. A Zap that adds a note after every call, for a team making 40 calls a day, uses up 100 tasks in two and a half days, so plan on a paid tier from the start.

The limits matter as much as the price. Zapier runs after an event, so it cannot pop a contact card inside the CRM as the phone rings or let a rep click to call from the record. A safe pattern is to use it for one narrow job, such as "when a call ends, add a note to the matching record", and leave everything else manual. If you find yourself building five Zaps to imitate a native link, moving to a CRM that Dialpad links natively may cost less than the plumbing.

The mistake of paying for sync before checking the CRM edition

A cleaning company upgraded six seats to Connect Pro for the CRM integration, then found their CRM plan did not allow third-party API access. Six seats at $10 extra for four months was $240 for a feature that could not work. The warning sign was in the CRM's own plan comparison, which they had not read. Before you buy anything on the Dialpad side, open your CRM's admin settings and find "API access" or the equivalent, and write down what it says.

Prompt: write the field-mapping brief for your CRM admin

The technical part of connecting is small. The part that goes wrong is agreeing what should be logged. Before the admin starts, ask an AI assistant to turn your wishes into a one-page brief:

I run a small [type of business]. We are connecting Dialpad calls to [CRM].
Our team: [number] people who need call logging, [number] who do not.
List the information we want on each CRM record after a call:
(who called, direction, duration, recording, summary, outcome).
For each item, say whether it should be automatic or typed by the person,
what could go wrong, and one test I can run to check it works.
Keep it to one page and write for someone who has not seen our setup.

Illustrative output, shortened: "Direction and duration: automatic; risk: duplicates if the number matches two contacts; test: call from a number stored on two records and see where it lands. Outcome: typed by the person, three options only (booked, quote sent, no answer), because free text will be skipped. Summary: automatic if the integration provides it; test by making a three-minute call." What you fix in it: the assistant will assume features. Strike any item the vendor page has not confirmed, and mark it "to test".

Example: a cleaning company using Zapier on Connect Pro

A cleaning company with five office staff is on Connect Pro and keeps its customers and jobs in a cleaning-business scheduling tool that Dialpad does not link to natively. It receives roughly twenty enquiry calls a day across the team. The owner builds one Zap: when a Dialpad call ends, create a task in the scheduling tool called "Follow up: [first name]", due the next morning.

Sum: twenty calls a day over about twenty working days is roughly 400 calls a month, so 400 tasks, four times the free plan's 100. Adding a filter so that only calls over two minutes create a task might cut that to about 160, and Zapier does not count filter steps as tasks, but a filter adds a step and the free plan lists two-step Zaps only. Either way a paid Zapier plan is needed, listed from $19.99 a month; check which task tier covers your volume. Set that against the alternative of moving the customer list into a CRM that Dialpad links natively, and the decision turns on how much the scheduling tool matters to the business, not on the Zapier bill.

The test after building: make three test calls, one under two minutes, one over, one from an unknown number. Note which ones created tasks, and whether the unknown number produced a task with an empty name; if it did, add fallback text. Write down the three results.

Questions to ask after the integration is live

A fortnight after launch, ask five things. Are calls from known numbers landing on the right record? How many calls sit unassociated? Do the people who were meant to use the link actually look at the history? Has anyone started typing notes twice because they do not trust it? And has the number of follow-ups missed fallen? Count rather than guess: pull ten calls at random from the Dialpad history and find each in the CRM. Eight or nine of ten matching is a good start; six of ten means the number formats or contact duplicates need cleaning before the tool takes the blame.

A short pre-purchase list

• Name the CRM and the edition, and find out whether it allows API access.
• Write down which people need call logging; do not upgrade the rest.
• Ask Dialpad in writing which plan gives you the integration, and whether summaries appear.
• Use the 14-day Connect trial and make ten test calls, looking at the CRM record each time.
• If your CRM has no native Dialpad link, price Zapier at your real call volume.
• Record the decision and the date, so you can revisit it at renewal.

The Connect plan table also ticks Zendesk and ServiceNow on Pro and Enterprise, and Google Workspace on every Connect plan. If your customer records live in a ticketing tool rather than a CRM, ask the same questions of that link: plan, fields, and the test call.

If you are unsure whether you should be logging calls in a CRM at all, a quiet first step is to log them by hand for a fortnight and see how often anyone looks at the notes. If nobody does, the upgrade is not the problem.

Admin permissions and the things that quietly stop syncing

Integrations that work on day one often fail on day sixty, and the cause is nearly always an account, not a plan. The usual culprits: the admin who authorised the link left the company and the connection was tied to their login; a Salesforce user lost a licence; someone changed a required field in the CRM so that new records fail validation; or a new hire was added to Dialpad but not to the integration.

Remember who is allowed to connect each side: Salesforce needs a System Admin profile to install the package, and HubSpot a Super Admin or a user with App Marketplace access. Each Dialpad office connects to one CRM instance, so everyone in an office shares it. Give the authorisation to a shared admin account with a role-based mailbox, not to an individual. Add "connect CRM" to your joiner checklist, and "remove from CRM link" to your leaver checklist. Once a quarter, make one test call from a randomly chosen seat and check the record. Ten minutes four times a year beats a week of lost notes.

Example: reading a mismatch between two pages

Suppose your CRM is Zoho and you are on Connect. Dialpad's Zoho article says the integration is available to Zoho Standard, Professional, Enterprise and Ultimate customers and to "eligible" Dialpad Connect users, while the Connect plan table on the pricing page does not list Zoho at all. The message to send: "Your help-centre article says the Zoho CRM integration is available to eligible Connect users. Please confirm in writing whether Connect Pro, at [number] seats, is eligible, and whether AI summaries post to Zoho on that plan." That is a specific question with one answer, and the reply is your protection. Vague questions get vague answers.

Finally, remember where the cost really sits. The $10 gap between Standard and Pro is small per seat but compounds across a team, and the time to configure and test is the larger cost. If you want to go through your own set-up with someone, my AI implementation consultation covers exactly this kind of plan and tooling decision.

Dialpad CRM questions, answered

Does Dialpad Connect Standard integrate with a CRM?

Not natively. The plan table on Dialpad's pricing page ticks Salesforce, HubSpot, Zendesk, Zapier and the open APIs on Connect Pro and Enterprise, not on Standard; Standard keeps Google Workspace. Because Dialpad's Zapier link also needs Pro or above, the only CRM option on Standard is typing notes by hand.

Do I need an Enterprise Salesforce edition?

Dialpad's help centre says the integration needs Salesforce Enterprise or Unlimited edition, or another edition with API access, and API access switched on. Check your Salesforce edition before you pay for a Dialpad upgrade, because an edition without API access will block the connection.

Will AI call summaries appear inside my CRM?

Yes, once set up. In Salesforce the AI Recap lands in an AI Summary field, visible on Tasks after an admin adds the Dialpad AI component in the Lightning page editor. In HubSpot it is a custom field capped at 255 characters, sent when the AI-data setting is on. Test with a trial call before relying on it.

Is Zapier a proper substitute for the native link?

For logging a note or creating a task after a call in a CRM that Dialpad does not link natively, yes, but Dialpad's Zapier link needs Connect Pro, Enterprise, or a Sell or Support licence. For screen pops, click-to-call from inside the CRM and live contact matching, no: Zapier suits after-the-fact record updates.

Who can set the integration up?

Usually a Dialpad admin and a CRM admin together. Salesforce needs a System Admin profile to install the package; HubSpot needs a Super Admin or a user with App Marketplace access. Plan an hour for connecting and a day of test calls before you tell the team it is live.

Further reads

• Is Dialpad's AI Safe for a Law Firm? Consent, Summaries and Cost — Consent and privacy points for AI summaries in a regulated firm.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Dialpad's pricing page (Connect plan comparison table); Dialpad help-centre articles on Salesforce, Dialpad AI in Salesforce, HubSpot, HubSpot contact sync, Zoho CRM and Zapier; Zapier's pricing page (all read 5 November 2026).