Aircall Review: A Cloud Phone System Judged From the Outbound Seat

This Aircall review finds a capable CRM-connected business phone system with a real sequential Power Dialer and shared outbound campaign controls. It fits teams that want calling and CRM activity with manager reporting in one platform. It falls short when the requirement starts with predictive or parallel dialing, campaign execution inside Salesforce CTI, automatic future-list suppression, or native Salesforce campaign imports.

Aircall review scorecard

Aircall sits between a general business phone and a dedicated sales dialer. Its public documentation supports more outbound control than ordinary click-to-call, especially through Power Dialer and Outbound Campaigns. The same documentation shows gaps a sales team needs to test before moving production lists.

This assessment covers documented behavior and procurement fit. It does not claim a tested call-quality advantage, higher connection rate, or measured productivity gain.

Aircall Power Dialer is sequential

Aircall's Power Dialer page says the tool adds numbers to an agent's queue and calls them in sequence. It advances after the previous call ends. The same page distinguishes that behavior from predictive dialers, which call several numbers at once.

The Power Dialer help article documents lists of up to 1,000 numbers and an automatic sequence. It also covers wrap-up and requeue behavior, along with notes and tags. It states that CSV import reads only column A and has a 1 MB limit. Power Dialer is unavailable on Aircall mobile applications, and a rep running a session becomes unavailable for inbound calls.

This workflow can suit a rep who owns a prepared calling block and needs one number at a time. The simple import boundary can become restrictive when the rep needs several list fields beside each number. CRM context may solve that problem only if matching is reliable.

Test the full rep loop by selecting the record and placing the call. Label the outcome and write the note. Then schedule the next action and receive a callback. Confirm how inbound availability changes during the session so an active outbound block does not silently delay important replies.

Outbound Campaigns adds shared control

Aircall's Outbound Campaigns overview says several agents can dial from one shared contact list while the system locks a contact to avoid simultaneous duplicate calls. Campaigns add assigned agents and calling rules. They also add outcome labels and automated queues, with contact-level tracking across attempts.

A separate campaign setup guide documents one-time and continuous campaigns with up to ten custom outcomes. It also covers caller-ID pools and as many as five attempts per contact. The listed contact sources are CSV and API. HubSpot static lists are also supported. The published limits include 10,000 records per CSV import and 5,000 contacts from a HubSpot static list. The API limit is 100 contacts per request.

This is a meaningful improvement over one rep's personal queue. It still does not mean one agent calls several numbers in parallel. Agents receive the next available contact, and the workflow remains based on human-agent availability.

The same documentation says campaign dialing does not operate in mobile applications or CTI integrations. It also says Salesforce import is not currently supported. A team that expects reps to stay inside Salesforce while running a shared campaign should treat that requirement as failed until Aircall demonstrates a different current entitlement in the actual account.

There is a current release-status conflict. Aircall announced in August 2026 that Outbound Campaigns was generally available, while current campaign help pages still label human-agent campaigns beta. Confirm plan access and production status in writing. The confirmation should also cover support and any changing limitations.

CRM integration quality depends on matching rules

Aircall's HubSpot integration documentation covers contacts and call logs, along with tickets and insights. Contact sync requires a valid E.164 number in HubSpot's Phone field. The matching process checks contact email first and contact phone next. It then checks company phone. When duplicates share a number, the most recently updated record can receive the activity.

That behavior creates a predictable failure mode: a call can be logged, yet land on the wrong duplicate. HubSpot Company records also do not receive contact sync in the same way as Contact records. Define the intended object and clean the relevant phone fields before judging the integration by log volume.

Aircall's HubSpot troubleshooting guidance says expired authentication and disconnected numbers can stop logging. Configuration can also stop it. Calls made while the integration is inactive do not log retroactively. Recording links may also take time to appear. A manager therefore needs an exception check rather than assuming every completed call reached the CRM.

The Salesforce integration guide documents automatic logging for outbound and inbound calls, including missed and voicemail calls. Activity can be logged against Contacts and Leads or against Accounts and Person Accounts. Transfers and comments can synchronize. Tags and recordings can synchronize as well. Aircall CTI also embeds the phone inside Salesforce.

Standard Salesforce calling and shared Outbound Campaigns have different boundaries. The Salesforce connection does not change Aircall's statement that campaign dialing is unavailable in CTI. Some AI outputs also require an assigned AI Assist license.

Test duplicates and several phone fields, then test ownership changes and no-match calls. Also test expired authentication and delayed recording links. The acceptance condition is a correct and reviewable CRM record, not a successful integration login.

Analytics measures activity, not pipeline

Aircall's outbound analytics documentation covers outbound calls and calls connected beyond a configurable duration. It also covers connection percentage, average in-call time, and total connected time. Filters include users and teams, plus numbers and tags. Campaign filters are available when Outbound Campaigns is enabled.

A connected outbound call can include the recipient's voicemail system. That makes connection percentage unsuitable as a count of human conversations. Keep live answers and qualified conversations in separate fields. Resulting sales stages also need their own field.

Dashboard access is limited to administrators and supervisors, with permissions that can narrow the data. Tables display up to 5,000 rows. Aircall says most dashboards carry a 15-minute delay and points real-time monitoring needs to its Live Monitoring product.

Analytics+ adds time-of-day heatmaps and tagged outcome analysis. It also provides rep and line comparisons, attempts before pickup, and campaign performance. These fields require the add-on and should not be attributed to the included reporting layer.

Use analytics to manage queue activity and attempts. It can also show outcomes and exception patterns. Use CRM opportunity evidence for pipeline. A long connected duration does not establish buyer fit, and a high call count does not establish useful work.

Where Aircall falls short of a dedicated sales dialer

Aircall's limits become clear when the buying brief requires high-throughput campaign execution rather than a connected business phone.

First, its documented Power Dialer is sequential. Shared campaigns let several agents work one list, but they do not establish predictive or parallel human dialing. A team buying for several simultaneous lines per rep needs a different proven mode.

Second, campaign work does not run inside CTI integrations or mobile applications. This can split the rep's Salesforce workflow even though ordinary Aircall calls embed in Salesforce.

Third, native campaign sources currently include CSV and API, with HubSpot static lists also supported. They do not include Salesforce campaign import. A Salesforce-led team may need an additional data movement step with a named owner.

Fourth, future-list suppression after a DNC outcome remains manual. The source system must own that block before another campaign import.

Fifth, the public beta-versus-GA conflict adds procurement uncertainty. Confirm support and entitlement rather than treating a release-note label as operational proof.

These are not universal reasons to reject Aircall. They define the conditions under which a dedicated sales dialer offers a better match.

Run a production acceptance test

Build a 50-record controlled list. Include clean CRM contacts and duplicates. Add alternate phone fields and invalid formats, then include reassigned owners and suppressed records. Finish with records without a CRM match. Treat 50 as our test design, not an Aircall recommendation.

The implementation passes only when:

1. Invalid and duplicate records receive a visible disposition before calling.
2. A suppressed record never enters the available queue.
3. Each permitted call reaches the intended CRM object and owner.
4. The note and outcome remain attached to that record, along with the tag, recording, and next action.
5. An expired integration produces a visible exception.
6. Campaign outcomes and ordinary Aircall tags remain distinguishable.
7. Dashboard totals reconcile after voicemail connections are separated.
8. A callback reaches the correct inbound owner.
9. The account proves the campaign entitlement stated in the order.

Approve the account only after all nine checks pass with the team's records. A failure on multi-line dialing, Salesforce-native campaign execution, or automatic suppression is a failed requirement, not a training problem for the reps to absorb.

Our outbound services connect calling and prospect research with email infrastructure and CRM handoff. They also establish reply ownership in a managed system the client owns.

Ready to test the calling workflow?

We can test Aircall's shared campaign entitlement, DNC handoff, callback ownership, voicemail-adjusted reporting, and CRM object matching before production lists move. Book your free discovery call →