How to Connect Aircall to Salesforce and Sync Calls and Notes

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Connect Aircall to Salesforce and Sync Calls and Notes.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Connect Aircall to Salesforce and Sync Calls and Notes.

To set up Aircall with Salesforce, you need Aircall Professional and Salesforce Enterprise or Unlimited (or Professional with bought API access). Install Salesforce v3 from Integrations > Apps, connect your numbers and install the CTI package. Notes land in the lead’s call Task Comments; tags and missed-call reasons land in Call Result. An outcome on a lead field needs a Salesforce Flow.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Check one date first. Salesforce’s developer documentation says Open CTI, the framework Aircall’s embedded phone uses, is unavailable to newly created Agentforce Service orgs and scheduled to retire in February 2028; Trailhead gives 28 February 2028. Aircall’s Lightning guide says existing orgs can keep using it until then and points new Service orgs to Salesforce Service Cloud Voice instead.

What do you need before setting up Aircall with Salesforce?

Aircall with Salesforce needs Salesforce Enterprise or Unlimited (or Professional with API access, if you will not use Omni-Channel), Aircall Professional or a custom Enterprise agreement, and a Salesforce administrator. Aircall’s Salesforce configuration guide lists the minimum requirements:

  • Salesforce Enterprise or Unlimited, or Salesforce Professional with API access bought through your Salesforce account executive, provided you will not use Omni-Channel.
  • Omni-Channel routing needs Enterprise or Unlimited.
  • Aircall Professional or a custom Enterprise agreement. The pricing page marks the Salesforce Sales Cloud and Service Cloud integrations as not included on Essentials.
  • A Salesforce administrator with top-level permissions, or full object-level and field-level security permissions, and a Salesforce licence. An Integration User licence cannot install it.
  • The same email address for each person in Aircall and Salesforce. If they differ, calls are assigned to the account admin instead of the right user.

For a three-person sales team, the Aircall side is at least three Professional licences: $150 a month on annual billing at the pricing page’s $50 per licence, before numbers beyond the one included, call charges and add-ons. A newly created Service org that cannot use Open CTI needs the Service Cloud Voice route; the pricing page lists Aircall for Salesforce Voice as a $30-per-seat add-on, and Aircall’s add-on article says it is bought through its sales team, not in the Dashboard. Get both vendors to confirm your editions and route in writing before configuring anything.

Allow an illustrative half-day for an administrator and a sales coordinator to check compatibility, prepare test leads and run tests. Duplicate data, missing permissions or an unsupported route can stretch that, so settle them before designing custom lead updates.

Should Salesforce staff work from Tasks, Aircall Logs or both?

Choose Both Task and Aircall Log object, the default, or Only Aircall Log object, because logging to Tasks alone is no longer available. The current Salesforce v3 package logs every interaction to the Aircall Log object, a custom object built to get round Task field limits. It holds the standard call fields plus richer ones, including AI summaries and key topics when Aircall’s AI is enabled, and IVR or routing details. Both options sit under Call logging should be done on, in the integration’s Settings tab.

With Both, each call creates a lightweight Task and a detailed Aircall Log, and the Task carries a lookup field called Aircall Log so users can click through. That is one call in two places, never two calls. Salesforce cannot hold a lookup from a custom object back to a Task, so the link lives on the Task only.

A bookkeeping practice keeps Both while its weekly activity report still counts Tasks. It adds the Aircall Logs related list to its Lead page layout, so the coordinator sees the activity on the lead and opens the Aircall Log for detail. Aircall says a change of logging mode applies only to new interactions, so if the practice later moves to log-only, it rebuilds the Task-based report and any Flows first and notes the switch date, so older Tasks are not mistaken for missing data.

The HubSpot integration tutorial describes a different record model; do not copy its ticket and outcome assumptions here. The first question in Salesforce is whether the Task and Aircall Log exist and point to the right lead.

If you want help deciding how your team should log calls in Salesforce, I offer one-to-one AI consultations for small businesses.

How do you install the Aircall Salesforce package?

Install the Aircall Salesforce package from the Aircall Dashboard, connect a test number, then install and configure the CTI, which Aircall requires even if you never use its embedded phone.

  1. In the Aircall Dashboard, open Integrations > Apps and choose Salesforce v3, then Install app and approve the authorisation request.
  2. Select the number you will test with and click Add Number. No call logs until at least one number is connected.
  3. Choose Sandbox or Production, click Connect to Salesforce and sign in if asked.
  4. Click Install CTI. Aircall says this is required even if you never use its embedded phone, because it installs the package the integration runs on.
  5. Click Configure CTI, then Next Step. Install Omni-Channel package is optional and can wait.
  6. Click Open Salesforce Settings, tick Visible for all profiles, save, return and click Finish. Then create a test call log.

Calls on numbers not connected to the integration never log in Salesforce. Keep a short register: quotation line connected, support line connected, supplier line deliberately excluded, with the reason for each.

Make a disposable test lead with a phone number you control. A print shop that skips this step connects its quotation number but makes its first test from a second outbound line, and nothing appears on the lead. The fix is to call from the connected number, not to reinstall the package.

How does Aircall match a call to a Salesforce user and a lead?

Aircall matches the person and the lead as two separate checks: user matching decides who owns the activity, and record matching decides which customer record gets it. According to Aircall’s field guide, an answered inbound call or any outbound call is owned by the Salesforce user with the same email as the Aircall user, provided that Salesforce user has existed for at least a day. Failing that, the owner of the related contact, account or lead; then whoever you named in When a call is not matched to a Salesforce User, assign it to; and last, the admin who installed the integration.

Missed inbound calls work differently: they go to the owner of the related contact, account or lead, then the fallback setting, then the installing admin. So a missed call from a lead lands with the lead owner, not with whoever was rung, which is usually what a sales team wants. Records Aircall creates for unknown numbers are owned by the integration admin, so plan a reassignment rule.

Clean duplicate numbers across objects. When several records share a number, Aircall picks Contact first, then Lead, Account and Person Account, and among records of the same type the first one Salesforce returns, typically the most recently updated. A lead can therefore lose its calls to an old contact with the same number.

An IT support firm finds exactly that: a test lead and an old contact both hold the caller’s number, and the inbound call logs to the contact. They decide which record represents the relationship, remove the number from the other and repeat the call.

Click-to-dial is the exception to the priority order: a call started from a lead is associated with that lead. So test an inbound call and a lead-launched outbound call separately; one good outbound click proves nothing about incoming matching.

Where do Aircall notes and call results land in Salesforce?

With Task logging on, Aircall puts agent notes in the Task’s Description (Comments), and puts tags, direction, status and missed-call reasons in Call Result (CallDisposition). Use the table below as your mapping sheet; all of it comes from Aircall’s Salesforce call logging fields article.

InformationTask field (label)What it does not do
Agent notesDescription (Comments), up to 32,000 charactersChange the lead’s own description or status
Recording or voicemail linkComments, the Call Recording field or both, as you chooseStore the audio in Salesforce
Tags, direction, status, missed reasonCallDisposition (Call Result)Qualify the lead
Lead or contactWhoId (Name)Resolve duplicates for you
OwnerOwnerId (Assigned To)Prove the callback happened
Open or doneStatus: Completed (Past Activities) or In progress (Next Steps)Track the customer’s request

Notes appear as “[agent name] added a new comment:” followed by the text, and later notes, including those after a transfer, are appended. Call Result is a structured string: the word aircall, the call’s tags, its direction, answered_call or unanswered_call, the Aircall number without the plus sign and, for a missed call, a reason such as out_of_opening_hours, no_available_agent, abandoned_in_ivr, short_abandoned or agents_did_not_answer. An illustrative missed call reads:

['Quote_requested', 'aircall', 'inbound', 'unanswered_call', '[Aircall number]', 'agents_did_not_answer']

That string is the hook for automation: a Flow can look for a tag or a missed reason in it. Aircall also says that editing tags or comments in Aircall updates the Salesforce Task, so corrections reach the record without a second log.

Notes only save if the agent finishes the post-call step. Aircall’s Lightning guide says to wait for the Call ended screen in the CTI, enter notes and tags, then click Keep conversation open or Close conversation; refreshing the page or closing the CTI first can lose them. Put that step in the team’s routine and test it.

A wedding planner’s test note reads: “Preferred date not confirmed; caller checking guest count; coordinator to reply once numbers arrive.” The agent finishes the post-call step, a second user reads it on the lead’s activity, then the agent edits the note in Aircall and the second user confirms the same Task changed rather than a new one appearing.

How do you update a lead outcome after an Aircall call?

Update a lead outcome with the native Call workflow settings first, and add a Salesforce Flow only if the lead record itself needs a field. In the integration’s Call workflow settings, each call type (outbound answered, outbound unanswered, inbound answered, missed call and voicemail) can log as Completed, In progress or Do nothing. Set missed call and voicemail to In progress and they appear under Next Steps on the lead as open items, owned by the lead owner, until someone closes them.

If the team needs an outcome on the lead record itself, such as a field called Latest phone outcome, that is a Salesforce Flow. Aircall’s Aircall Log guide suggests Flows for this kind of automation, such as creating follow-up tasks from call outcomes. On Trailhead, Salesforce explains that a record-triggered flow optimised for Actions and Related Records can update records other than the one that triggered it, which is what updating the lead from a call record needs.

  1. Pick one source object, Task or Aircall Log, to match your logging mode, and never trigger the same update from both.
  2. Run only on records Aircall created for a lead, not on calls someone logged by hand.
  3. Trigger on an explicit tag in Call Result, such as Callback_requested, never on free text in the notes.
  4. Update one approved field on that lead, and do not overwrite a newer result with an older call.
  5. Make re-runs safe: an edited note must not create a second follow-up task.
  6. Test a missing lead, conflicting tags, a correction and a removed tag before switching it on for everyone.

For example, a salesperson tags a call Callback_requested. The Flow sets the lead’s Latest phone outcome to “Callback requested” with the date, and checks that one open follow-up task exists. When the salesperson later fixes a typo in the note, Aircall updates the Task, the Flow runs again and must change nothing. Decide in advance what happens if the tag is removed.

Teams with Salesforce Sales Engagement licences have a native route instead: Aircall’s Sales Engagement guide says the CTI writes a Call Resolution value to the Aircall Log, which you map to Cadence Call Results so cadence steps complete automatically. Keep AI summaries out of qualification rules either way; “interested in options” and “agreed to proceed” are different commitments, and a person should apply the outcome.

How do you test Aircall and Salesforce with twelve calls?

Twelve test calls prove the connection without double-counting: with both logging options on and every call type set to log, 12 calls create 12 Tasks and 12 Aircall Logs. Here is the main worked example. A three-person IT support firm tests four cases per salesperson: an answered outbound call to an existing lead, an answered inbound call, a missed inbound call and a voicemail. That is 12 interactions, so expect 24 records describing 12 calls. Aircall creates a Task when a call is answered or, if it is not, when it ends.

For each case, check the lead, owner, call type, note and Call Result; for missed calls and voicemails, also check the open item under Next Steps. The test passes only when the salesperson who must respond can see the information and act on it.

Suppose ten pass and two belong to the admin instead of the salesperson. Check the two users’ emails, and how long their Salesforce users have existed, before touching record matching. After the fix, rerun both failures and one passing case with another user.

Add an unknown-number case. For unknown numbers the integration can create a Contact, a Lead or an Account, or do nothing. If you create leads and Person Accounts are switched off, Aircall fills the required Company field with “Unknown Company”, so add a weekly filter on that value to qualify or delete them. Logging to an existing Case or Opportunity only works for records tied to a contact, and is unavailable when unknown numbers create leads.

Finally, ring after hours. A setting decides whether calls log only during business hours or even when the number is closed, so a caller’s message can exist in Aircall and be absent from Salesforce by design. Write down which way you chose so the callback team knows where to look.

If tracking your twelve-call test in a spreadsheet is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

Why does a salesperson not see the Aircall phone in Salesforce?

A salesperson sees no Aircall phone in Salesforce when a CTI setup step is missing, even though the package is installed. Aircall’s Lightning CTI guide covers these steps, which are the usual culprits:

  • In Setup, open the call-centre settings, select Aircall CTI for Salesforce and add each user with Manage Call Center Users. A user can belong to only one call centre at a time.
  • Create a softphone layout (Setup, Softphone Layouts, New, Default Layout).
  • The Aircall Lightning app already has the phone; for any other app, add the Open CTI Softphone utility item in App Manager.
  • Add https://*.aircall.io as a Trusted URL with the connect-src, font-src, frame-src, img-src, media-src and style-src directives, or users see “Content is blocked”.
  • Assign the AirCall_PermissionSet to every CTI user and to the integration user, or call logging can break.
  • Make the Task Type field visible to all CTI profiles. Aircall says that if it is not visible, calls will not be logged.

Then ask an ordinary salesperson, not the admin, to open the sales app, sign in to the Aircall phone, ring the test lead with click-to-dial and receive an inbound call. Note any difference between their experience and the admin’s; a mismatched email between the two systems can also stop the CTI loading.

How do you keep follow-ups owned after the connection changes?

Treat a completed call as logged, not as finished: an answered call logged as Completed sits under Past Activities even if a quote is still owed. For a print enquiry where the agent promised to check paper stock, the note names the open question and the person checking it, and that follow-up stays open in your sales process until answered.

Test late information too. Two controlled calls to the same lead, the second with a different result, show whether your Flow protects the newer outcome from an older call’s late edit. That is a stronger check than watching one fresh call fill an empty field.

Investigate failures in layers: eligible route, authentication, connected number, the Type field and other permissions, record matching, then your custom Flow. Keep the failing call’s reference and the record you expected, so the administrator traces the real fault.

Compare activity counts with the Aircall dashboard review using the same period and lines, and review the Aircall plan comparison before changing plans, since dropping to Essentials removes the integration. Put the February 2028 Open CTI retirement on the system owner’s list, with Salesforce’s Open CTI support policy as the reference, and repeat the lead, note and ownership tests after package updates, user changes or a switch of logging mode.

Further reads

Show 2 more related tutorials

Sources: Aircall Help Centre articles How to configure your Salesforce integration; How to configure your Aircall CTI in Salesforce Lightning; Salesforce call logging fields; Logging your calls in Salesforce; Aircall Log Object (ALO); Configure Aircall for Salesforce Sales Engagement; Purchasing add-ons in Aircall. Aircall pricing and Salesforce integration pages. Salesforce Developers, Open CTI support policy; Trailhead, Build Record-Triggered Flows.

Want a second pair of eyes on your setup?

Bring the process you're trying to fix. On a 1:1 call we'll work out which AI tools should handle it, which parts stay manual, and how to roll it out without disrupting the team.

Book a 1:1 call with me