Once the Aircall–Jobber integration is set up, it automatically logs activity to Jobber and displays relevant client information in Aircall Workspace. This article explains how the integration works in daily use.

For installation and configuration steps, see How to setup and configure the Jobber integration.

Caller insight card

When you receive an incoming call, Aircall Workspace displays a caller insight card for recognized Jobber clients.

By default, the card includes:

  • Client name
  • Email address
  • Company name
  • A link to view the full client profile in Jobber

If you enable the customized insight card in your integration settings, up to five additional fields of your choice can be displayed instead.

Image showing fields in call

Call and message logging

Once the integration is active and at least one number is connected, Aircall automatically logs call and message activity to the corresponding Jobber client record.

Call logging

For each call, the following details are logged:

  • Call direction (inbound, outbound, or missed)
  • Caller and called numbers
  • Name and email of the handling agent
  • Call recording and voicemail links
  • Notes and tags added during the call
  • Call assignment and transfer details, including agent names and external numbers for external transfer
image showing call logging

Message logging

For messages, the following details are logged:

  • Message direction (sent or received)
  • Sender and recipient numbers
  • Message content
  • Media files sent or received via MMS or WhatsApp
image showing message logging

Activity is logged as either an internal note or a new request on the Jobber client record, depending on your configuration.

If no matching client is found, the integration follows your contact creation settings to determine whether to create a new client.

Note: When searching for a match in Jobber, the integration checks both direct client records and contacts associated with a client. Activity is logged against the matching client.
Contact settings

AI transcription and insights logging

If you have AI Assist or AI Assist Pro and have enabled AI insights logging, the following data is added to Jobber after each call:

  • Call transcription
  • Call summary
  • Key topics (can also be logged as tags)
  • Action items (can also be logged as open tasks)
  • Call sentiment

You can control which insights are logged and how they appear from the AI Entities Logging Settings in your integration settings.

Important: If your account does not include AI Assist or AI Assist Pro, AI insight logging is unavailable and transcriptions will not be logged in Jobber.
AI transcript and insights logging

Contact creation

When a call or message is associated with a number that does not exist in Jobber, the integration can automatically create a new client record if this option is enabled.

New clients are created with:

  • Default name: “Aircall new client”
  • The caller’s phone number

You can update the client’s details directly in Jobber after creation.

Contact creation applies to both inbound and outbound calls and messages.

contact creation

Contact sync

When contact sync is enabled, Jobber client records are synced to your Aircall phone system. This allows contacts to appear during incoming and outgoing calls.

The integration syncs:

  • Contact name
  • Phone number

Any updates made in Jobber are automatically reflected in Aircall. For more information please see Synchronizing your integration’s contacts to Aircall.

contact sync

AI Voice Agent call logging

When the AI Voice Agent handles a call, it follows one of two paths: it either manages the call from start to finish without involving a human agent, or it transfers the call to a human Aircall user. What is logged in Jobber depends on the path taken.

Note: AI Voice Agent call logging must be enabled in your Jobber Settings before any of the scenarios below will log. Make sure the AI Voice Agent has been added to a Smartflow before enabling this setting.

Voice Agent only

The call is handled entirely by the AI Voice Agent, with no transfer to a human agent.

  • Logged as an inbound received call
  • Clearly identifies that the AI Voice Agent handled the call
  • Includes AI Voice Agent notes, visually distinct from standard agent notes
AIVA call logging

Voice Agent transferred to a human agent

When the AI Voice Agent transfers a call to a human Aircall user, the logged result depends on whether the call is answered.

Transfer answered

The agent answers the transferred call.

  • Logged as an inbound answered call
  • Includes:
    • A title identifying both the AI Voice Agent and the answering agent
    • Notes from both the AI Voice Agent and the agent
    • Tags indicating it was a Voice Agent call, along with any agent-added tags
transfer answered logging

Transfer missed

No agent answers the transferred call.

  • Logged as a missed call
  • Includes:
    • A title indicating the call was transferred by the AI Voice Agent
    • AI Voice Agent notes
    • The call recording
    • Tags indicating it was a Voice Agent call
Transfer missed

Transfer missed, caller leaves voicemail

No agent answers the transferred call and the caller leaves a voicemail.

  • Logged as a voicemail
  • Includes:
    • A title indicating the call ended in voicemail after an AI Voice Agent escalation
    • AI Voice Agent notes
    • The voicemail recording
    • Tags indicating it was a Voice Agent call

Uninstalling or disconnecting the integration

Jobber in Aircall

Delete from Aircall

Deleting the integration from the Aircall Dashboard disconnects it from your Jobber account. Jobber will then display an option to reconnect.

Disconnect from Jobber

If you disconnect the Aircall app from within Jobber, the integration is automatically set to inactive in Aircall. A message appears in the integration settings. To resume use, reinstall the integration.

Reinstall with the same Jobber account

Jobber allows only one active connection per account. Installing the integration again with the same Jobber credentials automatically deactivates the previous integration. A warning is displayed during installation, and the deactivated integration shows a message in its settings.