Close CRM Review 2026: Verdict, Pricing, Limits, and Best-Fit Teams

Close is a calling-first CRM, and its list price is the least interesting number on the invoice. Solo starts at $9 per user/month on annual billing, but the tier that makes the product worth buying for a team is Growth at $99 per user/month, and calling, SMS, and AI credits are billed separately from both.

This Close CRM review answers one decision: whether a 1 to 50 seat outbound team should run its pipeline, its dialer, and its follow-up sequences in the same system.

The fit is narrow. Close suits an outbound-led inside-sales team that works the phone daily, and it suits a solo founder under 10,000 leads.

It fits poorly for customer-success-heavy teams. It is disqualified for any organization whose identity policy requires Okta or Auth0 single sign-on.

Buyers comparing a wider field should also look at the best CRM for sales teams before committing to a calling-first system.

Quick Verdict

Sources: Close official pricing and Close plans and billing documentation, checked August 3, 2026.

What Is Close CRM?

Close is a sales CRM that packages lead and opportunity management together with built-in calling, SMS, email, workflows, reporting, and the vendor’s Chloe AI features, according to Close’s product site. The legal entity behind it is Elastic Inc, named in Close’s partner program agreement.

The category matters for budgeting. Close is closer to a sales-engagement platform with a CRM attached than to a general-purpose record system, so the buying comparison is rarely feature-for-feature against a broad suite.

Readers new to the category can start with what CRM software does before comparing plan gates.

The practical consequence is a different cost shape. A CRM that only stores records has one bill; a CRM that also places the calls has a seat bill and a usage bill, and the second one moves with activity.

How Close CRM Was Researched and Evaluated

This review is based on Close’s official US pricing page, its help center, its developer documentation, its security and GDPR pages, and labeled third-party review and community evidence. Pricing, plan limits, and support terms were checked on August 3, 2026.

Close was assessed against the same buyer criteria applied to every CRM covered here: workflow fit, plan gates, usage-based cost, operational limits, migration and data portability, security and admin controls, support terms, and total cost by team size.

Greater weight was given to the factors that change a purchase decision rather than a feature count: the tier at which core outbound work becomes possible, the charges that sit outside the seat price, and the constraints that force an upgrade. Independent review platforms and community threads were used to test whether documented behavior matches reported buyer experience.

Claims that could not be verified from official documentation were excluded. Workflow descriptions follow Close’s documented steps and stated limits, and quantities such as call rates that vary by destination are described by mechanism rather than by a single published number.

The same standard is set out in the site review methodology.

Close CRM Pricing and True Cost

Close publishes four plans. The annual figures below are the effective per-user monthly rate when billed annually, and Close bills by billing schedule, plan, and user count, with telephony charged separately, according to Close’s plans and billing documentation.

Source: Close’s official pricing page, checked August 3, 2026. Prices can change after that date, so re-verify before signing.

A freshness warning belongs beside that table. Several reviews still ranking for this query describe Close using retired Base, Startup, Professional, or Enterprise plan names, so a budget built from them will not match a current quote.

The verified 2026 structure is Solo, Essentials, Growth, and Scale.

What Close costs at 1, 5, 10, and 25 seats

Seat math first, usage second. Every figure below is annual list cost on annual billing, calculated from the published per-user rates.

Calculation basis: seats multiplied by the annual effective rate multiplied by 12 months, using $35, $99, and $139 per user/month from Close official pricing, checked August 3, 2026. A single Solo seat is $108 per year at $9 per user/month, and Solo is not available above one user.

Those totals exclude calling, SMS, phone numbers, AI add-ons, and support add-ons.

At 10 seats the picture changes in the buyer’s favor. Close offers qualified discounts to customers with 10 or more seats that commit for 12 months or longer, and the discount amount is not published.

A 10-seat or 25-seat buyer should therefore ask for a written quote rather than budget from the list figures above.

The charges that sit outside the seat price

Calling, SMS, phone numbers, and certain AI tools are usage-based and drawn from a usage-credit balance, according to Close’s variable usage cost documentation. Calling and SMS are enabled by default on every plan unless an admin restricts them.

That default is the part most budgets miss.

Sources: Close variable usage cost documentation, Close support plan documentation, and Close secondary organization documentation, checked August 3, 2026.

Per-minute call rates are deliberately absent from that table. Close bills calls per minute and rounds up to the nearest minute and cent, and forwarded or transferred calls can produce several separately charged legs, so a rate card copied from any review will misstate a real bill.

Estimate the mechanism instead of the rate. Ten reps making 60 connects a day at two minutes each will be billed on rounded-up minutes, not on true talk time, and every warm transfer adds a leg.

SMS carries the same trap in a different form. Close bills SMS by unit rather than by message: an English-only unit is 140 characters, while a unit containing emojis or non-English characters can be as short as 33 characters.

One emoji in a template can therefore multiply the billable units for an entire campaign. I would test the exact production copy before forecasting SMS spend, not a clean English draft of it.

Call Assistant deserves its own line in a budget because it has two parts. A five-seat Growth team that adds Call Assistant pays $5,940 in seats plus $600 in base fees, or $6,540 a year before a single transcribed minute at $0.02, and only calls longer than 30 seconds are transcribed.

Premium Support is the largest single add-on. At $750 per month it reaches $9,000 a year, which is more than the annual seat cost of five or ten Essentials seats.

Treat it as a risk-management purchase for a team whose pipeline stops when the CRM stops, not as a default line item.

Which Close Plan Is Practical?

Growth is the practical plan for any team that runs repeatable outbound, and the reason is a plan gate rather than a preference.

The documented capability that separates the tiers is workflow automation, and its operating consequence is direct: a team on a tier without it works every follow-up by hand.

So the recommendation for an affected buyer is conditional. Choose Growth when the official documentation shows the sequences and dialing your reps need, and stay on a lower tier when the trade-off of manual follow-up is acceptable. Essentials supports unlimited leads and contacts, team collaboration, built-in forms, email, calling, SMS, inbox, and tasks, but it does not include Workflows.

Growth adds automated Workflows, Chloe in Workflows, Power Dialer, Custom Activities, and bulk email, according to Close’s official pricing page. Buying Essentials to save money removes the automation and dialing that make Close different from a cheaper pipeline tool.

The gap is $64 per user/month on annual billing. For a five-person team that is $3,840 a year, which is the honest price of automated outbound rather than a modest upgrade.

Scale is a governance and parallel-dialing purchase, not a volume purchase. It adds role-based permissions, lead visibility, Predictive Dialer, unlimited call-recording retention, live call coaching, user groups, and advanced controls for another $40 per user/month annually.

Sources: Close official pricing, Close AI credit documentation, and Close support plan documentation, checked August 3, 2026.

Plan changes are asymmetric, which matters for anyone planning to trial a higher tier. Upgrades apply immediately with a prorated charge, while downgrades are scheduled for the end of the current billing period and require usage to already sit below the lower plan’s limits.

A team that upgrades to Scale for a quarter and then adds custom roles cannot step back down mid-cycle. I would treat a Scale upgrade as a decision for the full billing period.

Core Workflows and Feature Gates

Sources: Close official pricing, Close roles and permissions documentation, Close lead page documentation, and Close AI credit documentation, checked August 3, 2026.

Two rows in that table carry the heaviest operating consequence, more than the price column does. Recording retention of 30 days on Essentials means a manager reviewing a disputed call from six weeks ago has nothing to review, and custom roles arriving only at Scale means least-privilege access is a $139 per user/month requirement.

Workflows and the timing reality

A Growth or Scale user builds a sequence by selecting eligible leads from a Smart View, configuring email and timing steps, and activating the workflow. That is the documented path, and the useful detail sits in what happens next.

Workflow email timing depends on the communication window and the connected account’s sending limits, and a draft-for-review step holds the sequence until a person sends the email, according to Close’s workflow step documentation. Workflow email steps are also subject to overall email-sending limits, and other email activity can delay them further, per Close’s workflow documentation.

A scheduled send is therefore a queue position, not a guarantee. A team promising a prospect a follow-up at a named time should build buffer into the sequence, segment large Smart Views into smaller batches, and watch sending capacity when several campaigns run at once.

Power Dialer, Predictive Dialer, and where the money goes

Power Dialer is the Growth-tier answer to call volume, and it runs against a filtered Smart View or contact search. Predictive Dialer and live call coaching stay on Scale.

Community evidence points the same way as the documentation. TrustRadius community insights identify the Power Dialer as a recurring strength, with users reporting time savings and more efficient calling, and individual TrustRadius reviews also flag reporting depth and the Predictive Dialer sitting behind a more expensive plan.

The buyer consequence is a two-step budget. A ten-rep team that starts on Growth at $11,880 a year and later needs parallel dialing and live coaching moves to $16,680, plus the telephony that both dialers generate.

Chloe, AI credits, and what stops at zero

Close includes monthly AI credits on every plan, and the allowance stops scaling before headcount does. Essentials grants 1,000 credits per user but caps the organization pool at 10,000, Growth grants 1,500 per user capped at 15,000, and Scale grants 2,000 per user capped at 20,000, while Solo receives a flat 500.

An eleventh Essentials seat therefore adds a license fee and no additional included credits. Credits reset monthly and do not roll over, so an underused month is not banked against a heavy one.

When the balance reaches zero, credit-based functions such as Chloe Voice Agents, Enrichment, and Auto Updates pause, listed free AI features stay available, and calls already in progress complete. Usage warnings appear once consumption reaches at least 75 percent.

Top-ups are a subscription rather than a metered overage. AI Credit Subscription Plans start at $20 per month for 1,200 credits and run through $1,500 per month for 150,000 credits on the verified portion of the published table.

Upgrading a credit plan charges the full new price without proration, while downgrades take effect the next cycle.

That no-proration rule is the trap. A team that jumps a tier mid-month to clear a backlog pays the whole new tier for that month.

I would set an internal alert well below the 75 percent warning and buy the smallest tier that covers a normal month rather than a peak one.

Teams weighing credit-based assistants across vendors can compare the wider field of AI CRM software before committing to one credit model.

AI Lead Summaries sit on Growth and Scale and summarize the last 90 days of activity or the most recent 100 activities, whichever is greater. For a long-running enterprise account with years of history, that is a recent-activity briefing rather than an account history.

Setup, Onboarding, and Ease of Use

Setup difficulty is moderate, and it splits cleanly into two paths. A spreadsheet import is self-serve, while a CRM-to-CRM migration is an admin-only project with a sample migration, field mapping, error review, and a full cutover.

The spreadsheet path carries the sharper risk. Close’s importer can match existing leads on one or more comparison fields, then add missing data, replace existing lead data, or skip matches. The replace option cannot be undone, according to Close’s lead import documentation.

Import results separate created, updated, skipped, and failed rows, with detail views and undo controls for supported imports. That summary is the checkpoint a first import should be planned around.

A workable first-week sequence is narrow on purpose. Export a backup of the source data, run a small sample file, and choose add-missing or skip rather than replace.

Read the failed and skipped groups before scaling the file, and only then load the full list.

Mobile is available but version-sensitive. Close provides official iOS and Android apps and supports operating-system versions no more than one major version behind, per Close’s mobile app documentation.

A fleet of older devices is therefore a deployment question to settle before rollout rather than after.

The 30 and 90-day adoption test. By day 30, every rep should be dialing from a Smart View rather than a spreadsheet, and the lead record should show call, email, and SMS activity in one timeline. By day 90, at least one workflow should be running unattended, the monthly AI credit burn should be predictable, and the first full telephony invoice should match the forecast within a range the finance owner accepts.

If those three are not true at day 90, the problem is rarely the software. It is usually that the team bought Essentials and is doing Growth-tier work by hand.

Integrations, API, Security, and Support

Close ships built-in Meetings and email sync plus Zoom and Slack integrations, and other applications connect through OAuth or API keys and through automation platforms such as Zapier or Make, according to Close’s integrations documentation. Those are three different reliability profiles wearing one label.

A native integration is Close’s to fix, an OAuth or API connection is the buyer’s to build and maintain, and a Zapier or Make connection adds a third vendor, a second bill, and a second failure point. I would inventory which of the three each critical connection falls into before signing, because that answer decides who gets paged when a sync breaks.

API access and the event-log API are included on all four plans, which is unusually open for this price band. Included access is not unlimited throughput, though.

Rate limits are enforced per endpoint group with separate per-key and organization limits, and an integration must pause according to the rate-reset value after a 429 response, per Close’s API rate-limit documentation. A data team planning a nightly full sync should design for backoff from the first sprint rather than discovering the limit in production.

Security and admin controls

Close states that it is SOC 2 Type 2 compliant and that it protects confidential data through authentication, encryption, restricted access, redundancy, monitoring, and incident processes, on Close’s security page. It also states that it meets GDPR controller and processor obligations, uses encryption in transit and at rest, and maintains annually reviewed incident-response processes, on Close’s GDPR statement.

Both are vendor statements, and a security review should request the underlying report rather than treat the page as the artifact.

Certification is not the constraint that fails deals here. The identity stack is.

Close supports Google single sign-on, and its official help page states that Auth0 and Okta are not supported, per Close’s Google SSO documentation. For a company standardized on Okta, that ends the evaluation regardless of every other strength in this review.

Two-factor authentication is authenticator-app based rather than SMS, and admins can see which users have enabled it, per Close’s two-factor authentication documentation. Creating and editing custom roles is limited to admins on the Scale plan, so least-privilege access carries a per-seat price for the whole team, not for the admins who need it.

Support terms

Standard support is email only, Monday through Friday from 9 a.m. to 7 p.m. Eastern Time, excluding listed major US holidays. A team selling into Pacific-time evenings or working weekends is outside that window.

Premium Support starts at $750 per month and includes a customizable SLA, a first-response target of two hours or less during business hours, a dedicated queue, and screen-share appointments. The target covers first response, not resolution, which is the distinction to press on before signing an SLA.

Migration Risks and Data Portability

Migration into Close is a source-specific validation project rather than a one-click transfer. CRM-to-CRM migration is admin-only and powered by Import2, and it supports a published list of source CRMs. It moves through source connection, field mapping, sample migration, error review, and a full import confirmation, according to Close’s CRM migration documentation.

Coverage varies by source, and Close documents at least one hard boundary. For SalesforceIQ, only Accounts and Contacts are imported, while Notes and other Activities are non-transferable because of source API limitations.

Automation is the quieter gap. Close’s migration documentation does not establish that source automations are recreated, so sequences, assignment rules, and triggers should be inventoried and rebuilt by hand in the plan rather than assumed.

Attachments need their own test. The support-tool email-message export does not include attachments, while note attachments and lead files use separate export and download paths, per Close’s support tools documentation.

Exit terms matter as much as entry terms. Users can export Leads, Contacts, or Opportunities in CSV or JSON from a Leads search, but not directly from a Contacts Smart View. CSV is also not the preferred format when activity data is needed, per Close’s data export documentation.

Audit history has a ceiling too. The event-log export covers a 30-day window and a maximum of 100,000 events, which is a scheduling requirement for any admin who needs longer retention than that.

A migration plan that survives contact with a real CRM covers six checks. Inventory every object and automation in the source system, preserve a full source export, and run the sample migration to compare record counts field by field.

Then avoid replace-entire-record duplicate handling on the first pass, test representative attachments and activity history, and rebuild unsupported automation before cutover. The general sequence is set out in this CRM migration checklist.

Close CRM Limitations

Six constraints do real damage to real teams, and none of them appear on the pricing page as a warning.

Communication cost is variable by design. Calling, SMS, phone numbers, and several AI functions are metered, calls round up to the nearest minute and cent, and transfers create additional charged legs. A finance owner who wants one predictable monthly number will not get it from a calling-first CRM.

Automation starts two tiers up. Workflows, Power Dialer, bulk email, and SMS in workflows are absent from Solo and Essentials, so the cheap tiers are a shared record system rather than an outbound engine.

Included AI credits stop scaling before the team does. Organization caps of 10,000, 15,000, and 20,000 credits mean seats added beyond the cap bring no extra included credits, and unused credits expire each month.

Recording retention is a compliance gate. Thirty days on Solo and Essentials and 90 days on Growth mean anything longer is either a manual export routine or a move to Scale.

Identity support is narrow. Google SSO is documented and Auth0 and Okta are not supported, and custom roles require Scale, which puts both federated identity and least-privilege access outside reach for many mid-market security policies.

Migration completeness is source-dependent. SalesforceIQ notes and activities are documented as non-transferable, automation recreation is not documented, and email exports exclude attachments, so switching cost is a project line rather than a footnote.

Close CRM Pros and Cons

Sources: Close official pricing and TrustRadius Close CRM reviews, checked August 3, 2026.

Who Should and Should Not Buy Close

Fit here is decided by daily motion and identity policy, not by company size. The five cohorts below are separated by how much of the week is spent dialing and by which control a security review will insist on.

Who should use Close CRM

Solo founders working a finite prospect list. Solo at $9 per user/month annually covers integrated email, calling, and SMS under a 10,000-lead ceiling, which is enough until a second person joins.

Three to five-person SDR teams running repeatable sequences. Growth at $5,940 a year for five seats buys Workflows, Power Dialer, bulk email, and SMS automation, and this cohort gets the clearest return on the automation gate.

Ten to fifty-rep inside-sales teams that live on the phone. Scale earns its premium when parallel dialing, live coaching, or segmented lead visibility becomes a requirement, and any buyer at this size should request a discounted quote before accepting list pricing. Teams still deciding on category fit can compare against the best CRM for small business shortlist first.

Agencies and multi-brand sellers with many mailboxes. Ten connected email accounts per user on Growth and Scale supports more mailbox complexity than the three allowed on lower tiers. Growth and Scale include one secondary organization, and every organization beyond that costs $50 per month and isolates its data.

Who should avoid Close CRM

Customer-success-heavy teams. A long-term Reddit discussion describes Close as effective for outbound but weaker as a broad CRM or for customer-success work, and the plan gates point the same way, since the paid capabilities are dialers and sequences rather than lifecycle management.

Organizations that require Okta or Auth0 SSO. The documented SSO path is Google, which makes this a procurement stop rather than a workaround.

Teams that need a fixed, all-inclusive communications budget. Usage-based calling and SMS, A2P registration fees, and credit-based AI make the monthly total move with activity.

Regulated teams on a low-tier budget that need long recording retention. Thirty days on Solo and Essentials forces either manual exports or a plan the budget did not anticipate.

Buyers who need every note, activity, attachment, and automation to transfer in full. Coverage is source-specific, with documented non-transferable objects for SalesforceIQ and undocumented automation recreation.

Close CRM Alternatives

Three alternatives address the three most common reasons a buyer walks away from Close: usage-based communication cost, weak fit outside outbound, and the Google-only SSO boundary. Verify current pricing and identity support directly with each vendor, since none of those figures are established by Close’s documentation.

Pipedrive

Worth shortlisting when the team’s daily work is moving deals through stages rather than dialing lists, since the case for Close rests on consolidating the dialer into the CRM. Read the Pipedrive CRM review for current plan gates before comparing quotes.

HubSpot Sales Hub

Worth shortlisting when sales and marketing share one funnel and the handoff is where deals leak. The HubSpot CRM review covers the seat and contact mechanics that drive its cost at scale.

Zoho CRM

Worth shortlisting when per-seat cost is the binding constraint and the team can rebuild its outbound motion in a different automation model. The Zoho CRM review sets out the edition gates that decide which tier is usable.

Final Verdict: Is Close CRM Worth It?

Close is worth it for an outbound-led sales team that makes calls its primary motion and wants the dialer, the sequences, and the pipeline in one record. For that team, Growth at $99 per user/month annually is the plan that matters, and $5,940 a year for five seats is a defensible price for automation plus a Power Dialer.

Close is not worth it for a customer-success-heavy team, for an organization standardized on Okta or Auth0, or for a finance owner who needs a fixed communications bill.

Choose Close if outbound calling volume is the constraint on revenue, Google identity satisfies your security policy, and the budget can absorb metered telephony, SMS units, and AI credits on top of seats. Choose a pipeline-first CRM if calls are occasional and the dialer would sit idle.

One question belongs on the calendar before the first renewal. By then the team should be able to show workflows running unattended, a telephony line predictable within an accepted range, and recordings retained long enough for coaching and disputes.

Without those three, the renewal is paying for a dialer the team is not using.

Frequently Asked Questions

These answers use the plan prices, gates, and limits verified on the official pages linked above, checked August 3, 2026.

How much does Close CRM cost?

Close publishes four plans: Solo at $19 per user/month monthly or $9 annually, Essentials at $49 or $35, Growth at $109 or $99, and Scale at $149 or $139, checked August 3, 2026. Five Growth seats on annual billing total $5,940 a year before calling, SMS, phone numbers, and AI credits, which are billed separately.

Does Close CRM have a free plan?

No, unless a trial counts for your purposes: the four published plans are all paid, and Close offers a trial with no credit card plus a 30-day money-back guarantee after purchase. That combination lowers the cost of testing a real pipeline, but there is no permanently free tier to fall back to once the trial ends.

Which Close plan includes Workflows?

Growth is the first plan with automated Workflows, and Scale includes them too, while Solo and Essentials do not include Workflows, Power Dialer, bulk email, or SMS in workflows. Moving from Essentials to Growth adds $64 per user/month on annual billing, which is $3,840 a year for a five-person team.

Is Close CRM worth it for a five-person sales team?

Yes, if the five people are dialing daily and running repeatable sequences, because Growth at $5,940 a year gives that team Workflows, Power Dialer, bulk email, and AI Lead Summaries. If the same five people mostly manage inbound deals through stages, that automation gate is paying for capability the team will not use.

Does Close CRM include calling and SMS in the plan price?

No: calling, SMS, phone numbers, and certain AI tools are usage-based and drawn from a usage-credit balance, and both calling and SMS are enabled by default unless an admin restricts them. Calls are billed per minute rounded up to the nearest minute and cent, and transfers can create several separately charged legs.

What happens when Close AI credits run out?

Credit-based features such as Chloe Voice Agents, Enrichment, and Auto Updates pause, listed free AI features stay available, calls already in progress finish, and warnings appear once usage reaches at least 75 percent. Credits reset monthly with no rollover, and extra credits are bought as a subscription starting at $20 per month for 1,200 credits.

Is Close CRM SOC 2 compliant?

Close states on its security page that it is SOC 2 Type 2 compliant and describes authentication, encryption, restricted access, redundancy, monitoring, and incident processes. That is a vendor statement rather than an independent audit reproduced here, so a security review should request the report itself along with the GDPR terms Close publishes separately.

Can Close CRM work with Okta or Auth0 SSO?

No, based on Close’s own documentation, which supports Google single sign-on and states that Auth0 and Okta are not supported, so for a company that mandates federated identity through those providers this is a disqualifier rather than a configuration exercise. Two-factor authentication uses an authenticator app, and SMS-based 2FA is not supported.

How hard is it to migrate into Close CRM?

Harder than a spreadsheet import suggests: CRM-to-CRM migration is admin-only through Import2 and runs through source connection, field mapping, a sample migration, error review, and full import. Coverage varies by source, since SalesforceIQ notes and activities are documented as non-transferable and automation recreation is not documented, so plan to rebuild sequences by hand.

Close CRM vs HubSpot: which fits a small outbound team?

Pick by bottleneck rather than by feature list: if revenue is limited by call and SMS volume, Close consolidates the dialer into the CRM, and Growth is the tier that makes that real. If revenue is limited by the marketing-to-sales handoff, evaluate HubSpot’s seat and contact pricing at your list size before comparing anything else.

About the author

Macedona

Macedona is the founder and lead reviewer at SaaS CRM Review, where he has published 175+ in-depth reviews, pricing guides, and comparisons of CRM and SaaS tools. Each review is based on hands-on testing or verified documentation, and every article states clearly which method was used. Pricing and features are checked against official vendor sources, with the verification date noted in the article. Macedona follows a published review methodology and editorial policy. SaaS CRM Review earns affiliate commissions from some links, which never influence ratings or rankings. Read the full affiliate disclosure.

Follow the author: