This article answers common questions about using Salesforce Voice (SfV) with Aircall, including permissions, call logging behavior, UI customization, and known limitations.

Required permissions for Salesforce Voice

To use SFV with Aircall, users must have specific Salesforce roles and permission sets.

Which permissions are required for SFV to work?

You must assign any one of the following roles, based on your business needs:

  • Contact Center Admin (Partner Telephony)
  • Contact Center Agent (Partner Telephony)
  • Contact Center Supervisor (Partner Telephony)

Additionally, the user must have the Aircall SfV User permission set assigned.

Important: Without the appropriate Contact Center role and the Aircall SfV User permission set, users may not be able to use Service Cloud Voice features with Aircall correctly.

VoiceCall object behavior

When is the VoiceCall object created?

The VoiceCall record is created as soon as the call is connected. This object is used by Salesforce to track the core details of the voice interaction.

SfV Phone user interface

Can the SfV Phone user interface be modified?

No. The SfV Phone UI is a standard, out-of-the-box component provided by Salesforce and cannot be customized.

Note: You can configure related Salesforce settings and workflows, but the visual layout and behavior of the SFV Phone interface itself are not configurable.

Call recording in Salesforce Voice

How can I enable call recording in SfV?

To enable call recording when using Aircall with SfV:

  1. Assign the Aircall SFV Permissions set to your users.
  2. This permission set includes the required settings for call recording to function properly.

Once assigned, calls handled through SFV can be recorded according to your configured policies.

Aircall Voice object and VoiceCall object

Why is there an Aircall Voice object if the VoiceCall object already tracks call data?

The Aircall Voice object acts as an extension of the standard VoiceCall object.

  • The VoiceCall object is a standard Salesforce object with limits on the number of fields it can contain.
  • Due to these limitations, the Aircall Voice object is used to store additional call-related data, such as enriched information or extended attributes that cannot be held in the standard object.

The Aircall Voice record is automatically created and linked whenever a VoiceCall record is created.

Known issues and limitations

Minimized Omni-Channel widget for inbound calls

If the Omni-Channel interface is minimized when an inbound call arrives, it does not automatically expand or provide a prominent notification.

For users who have manual call acceptance enabled, this means they must actively monitor and interact with the widget.

Steps required for users with manual call acceptance

When an inbound call arrives and the Omni-Channel widget is minimized, the user must:

  1. Notice the subtle notification that a new call is incoming.
  2. Manually expand the Omni-Channel widget.
  3. Click to accept the call.
Tip: Encourage agents who use manual call acceptance to keep the Omni-Channel widget visible whenever possible to avoid missing inbound calls.