Zendesk integration updates

Aircall has introduced several enhancements to the Zendesk integration, improving both functionality and user experience. These updates include more flexible assignment rules, customizable insight cards, enhanced ticket views, and expanded messaging support.

Improved assignment rules

When creating Assignment Rules, users can now search for Lines, Teams, and Users more efficiently. Additionally, multiple Lines can be selected at once during configuration to streamline setup.

Customizable insight cards for contacts

Insight Cards for contacts can now be customized directly from the Integration Settings page in the Aircall Dashboard. Users can choose whether to display custom insight cards and select up to five contact details to show.

Tip: Customizing insight cards helps highlight the most relevant contact information for your team.

New ticket view option

Leveraging Zendesk’s Public API (TPE V2), Aircall can now display information about standard call fields within each ticket. In the Integration Settings page, users can decide which fields to show to provide additional call context.

Available fields

Agent, Call Started At, Call Ended At, Completion Status, Direction, Duration, From Line, Outside Business Hours, Overflowed To, Recording URL, To Line, Voicemail, Wait Time, DNIS, Call Type, IVR Time Spent, Call Disposition, Transcript, and External ID.

The selected fields will appear directly in the corresponding Zendesk ticket.

Important: To use this feature, ensure that the Agent Workspace is enabled in Zendesk and that you have access to a Talk Partner Edition (as a standalone license or through the Zendesk Suite).

Improved Zendesk settings

With the updated integration, users can now choose what appears for each Inbound and Outbound call:

• The ticket
• The contact history
• Or nothing

Note: You must use the Aircall CTI within Zendesk for this feature to function properly.
For setup guidance, visit: How to Configure Your Aircall CTI Within Zendesk

Users can also decide whether the ticket title should update after each call.
For example, if a ticket was created for an inbound unanswered call, and later updated from an outbound answered call, the ticket title will reflect the new call status.

Note: The “Ticket should be created” setting applies only to calls, not to messages sent or received outside business hours as well as Calls handled purely by AI Voice Agent.

WhatsApp message logging

The Aircall-Zendesk integration now supports logging WhatsApp messages (text only) into Zendesk tickets.
Users can configure, via the dedicated integration settings for the WhatsApp channel, whether inbound and outbound messages should:

• Be logged in a new ticket, or
• Be added to an existing ticket

Users can also define the ticket status when these messages are logged.

These options can be configured through the Ticket Workflow and New Ticket Status settings.

Tip: Enabling WhatsApp message logging ensures all customer interactions are captured in Zendesk for a complete communication history.

AI Voice Agent Calls Logging 

When using the Voice Agent, calls can follow two possible paths:

• Voice Agent only: The call is handled entirely by the Voice Agent without transfer.
• Voice Agent → Aircall user: The Voice Agent transfers the call to a human Aircall user.

In both cases, calls are logged in Zendesk  as inbound received calls to ensure accurate reporting and visibility.

AI Voice Agent Calls, will be logged as internal note or voice comment based on whether Ticket View setting is enabled or disabled in integration settings. 

Voice Agent only

For calls handled entirely by the Voice Agent:

• Calls are logged as inbound received calls.
• It is immediately clear from the log that the call was handled by the Voice Agent.
• Voice Agent notes are included and are easily distinguishable from other notes.

Voice Agent → Aircall user

When a call is transferred from the Voice Agent to a human Aircall user, logging depends on whether the transfer is answered or missed.

Answered transfer

If the agent answers the transferred call, it is logged as an inbound answered call. For reporting clarity:

• The title includes both the Voice Agent and the agent’s name.
• Notes from both the user and the Voice Agent are logged
• Tags indicate it was a Voice Agent call, alongside any user tags.

Missed transfer

If the agent does not answer the transferred call, it is logged as a missed call, but still marked as a Voice Agent transfer. The log will include:

• A title showing that the call was transferred by the Voice Agent.
• Notes from the Voice Agent.
• The recording of the call.
• Tags showing it was a Voice Agent call.

Missed transfer to voicemail

When a transferred call is not answered by the agent and the caller leaves a voicemail, Aircall records it as a Voicemail while maintaining its Voice Agent transfer status in the call log.

What appears in the call log

The call log for a missed transfer that results in voicemail includes:

• Title indicating the call ended in voicemail after being escalated by the Voice Agent
• Notes added by the Voice Agent
• Voicemail recording from the caller
• Tags showing that it was a Voice Agent call