Evidence note: Use this review to build a shortlist. We publish a numerical score or final recommendation only after the product completes the same hands-on scenarios and exception tests used for its peers.

The short verdict

Aircall is a credible communications layer for service businesses that need shared phone numbers, IVR, call routing, recordings, analytics, mobile access, and CRM connections. Its strongest fit is a team with at least three phone users and a named owner for routing, follow-up, and reporting. The buying decision must still model local number coverage, call bundles, SMS availability, recording retention, AI usage, and add-ons for the operating country.

Strongest desk signalConnected calls
Cost triggerSeats + usage
Test firstMissed-call ownership

Who it fits

Growing service teams with a real office or call-handling function, at least three users, and a need to connect phone activity with CRM or support records.

Watch closely: The published entry price assumes annual billing and a three-license minimum. Country coverage, usage, extra numbers, AI agents, Analytics+, and messaging can materially change total cost.

Pricing and plan gates

The current US annual-billing selector displays Essentials at USD 30 per license monthly and Professional at USD 50, both with a three-license minimum: USD 90 or USD 150 per month before usage, taxes, extra numbers, and add-ons. Custom starts at 25 licenses. Re-capture the selected country, billing cycle, included call bundle, and written quote before purchase.

Evaluation access: Aircall presents a free-access evaluation path. Confirm the evaluation period, included number, enabled integrations, AI allowance, and any country restrictions before testing.

  • Price the three-license minimum even if only one or two people answer calls today, and capture the selected country and billing cycle.
  • Separate extra numbers, inbound and outbound usage, international calls, SMS or MMS, recording, AI, WhatsApp, Analytics+, and taxes in the written quote.
  • Confirm the exact CRM or help-desk integration, the system of record, write-back fields, retry behaviour, permissions, and duplicate-prevention rule.
  • Verify the operating country's number eligibility, supported SMS number type, carrier registration, domestic-message boundary, portability, emergency calling, consent, recording notice, and retention requirement.
  • Create a component-level exit inventory for numbers, recordings, messages, tags, contacts, call history, analytics, integration mappings, users, permissions, and billing records.

Strengths and constraints

Why it stays on the shortlist

The strongest documented signals

  • Essentials combines shared numbers, IVR, business hours, recording, SMS, desktop and mobile apps, 250-plus integrations, and API access
  • Professional adds smart routing, queue callback, Power Dialer, live monitoring, advanced analytics, and Salesforce CTI
  • The integrations directory exposes a broad CRM and help-desk surface for a controlled system-of-record test
  • Country-aware pricing and support documentation make several cost, retention, and messaging gates inspectable before a pilot
Where the decision can break

The constraints to price and test

  • Essentials and Professional have a three-license minimum; the current US annual selector therefore starts at USD 90 or USD 150 per month before extras, while Custom starts at 25 licenses
  • Native SMS is currently available only in the United States, Canada, United Kingdom, France, Australia, and Germany; supported number types and domestic-message rules vary, and MMS is narrower
  • An additional number is listed at USD 6 monthly, while international calls, AI products, WhatsApp, Analytics+, and other add-ons can change total cost
  • Recording and analytics history have plan and dashboard-retention boundaries; Analytics API is available only with Analytics+ and an external scheduler is needed for recurring exports
  • A phone platform does not replace job scheduling, estimates, dispatch records, invoicing, payments, or technician records

What we still need to test

  1. Run a synthetic after-hours missed call through voicemail, callback ownership, tags, and CRM logging, then repeat once to detect duplicate writes.
  2. Route two synthetic call types through IVR and queues, make one user unavailable, and inspect transfer, callback, overflow, and peak-hour behaviour.
  3. Send consented synthetic SMS only from an eligible country and number type; record registration, delivery, opt-out, retention, and failure evidence.
  4. Verify recording notice, role-based access, retention visibility, deletion, and export with non-customer test audio.
  5. Disconnect the CRM integration during a synthetic write, reconnect it, and inspect retry visibility, idempotency, and the final system-of-record timeline.
  6. Export a bounded call-history period and verify that recordings, tags, user activity, and analytics can be reconciled; treat scheduled Analytics API export as an Analytics+ and external-scheduler test.
  7. Reconcile the three-seat base, numbers, peak minutes, messages, international usage, AI, analytics, and every enabled add-on against the written quote and exit inventory.

Evidence sources

Editorial record

Who reviewed this page and what happens next.

Commercial relationships cannot change the evidence state, fit statement, caveats, or conclusion.

Research and review
Andre Ribeiro
Published
Last material review
Next scheduled review
Evidence scope
Global product surface; country-specific number, messaging, and call-cost evidence required
Evidence state
Desk / Pending

Testing methodologyEditorial standardsCorrections and update log