Aircall Log Object (ALO)

The Aircall Log object (ALO) is a Salesforce custom object used by the Aircall for Salesforce v3 integration to store enriched call and message data. It is designed to overcome Salesforce Task limitations and to give you a single place where you can see full interaction details, including AI insights.

NOTE:
If you previously used the **Aircall Voice object** in an older Salesforce package, the **Aircall Log object** is its modern equivalent in the current Salesforce v3 package. New configurations and migrations should use the Aircall Log object.

What the Aircall Log object does

The Aircall Log object:

• Stores one record for each Aircall interaction (call, SMS, or MMS) that is logged to Salesforce
• Includes standard call fields that also exist on the Task object (for example: duration, direction, recording link)
• Adds additional fields that are not available on Task, such as:
  • Message content and metadata for SMS and MMS
  • AI summaries and key topics
  • IVR or routing details where available
• Links each log to the most relevant Salesforce record, for example:
  • Contact, Lead, Account, Opportunity, Case, or other supported objects

This lets you keep your Tasks lightweight and still have a complete, detailed history of every interaction.

How ALO works with Tasks

By default, Aircall logs to both Task and the Aircall Log object. For each interaction:

• A new Aircall Log record is created with all available call or message details
• A Task is also created with key call fields (for example: subject, basic call details), and it includes a lookup to the related Aircall Log record
• Both records can be related to the same Contact, Lead, Account, or other supported record so agents and managers can quickly navigate between activity timelines and detailed logs

This model keeps backward compatibility for any existing Task based reports or workflows while unlocking richer data on the Aircall Log object.

Configure where calls and SMS are logged

You choose whether Aircall logs to both Task and ALO or to ALO only from the Aircall Dashboard.

Steps

1. Go to Aircall Dashboard > Integrations & API.
2. Go to Integrations and open your Salesforce V3 integration.
3. Open the Settings tab.
4. Find the Call logging should be done on setting.
5. Choose one of the available options:

• Both Task and Aircall Log object
  • Default setting.
  • Aircall creates a Task plus a detailed Aircall Log record for each interaction.
• Only Aircall Log object
  • Recommended if you are close to Salesforce Task field limits or want to centralize logging on ALO.
  • Aircall creates only an Aircall Log record; no Task is created automatically.

IMPORTANT:
Logging to **Only Task** is not available. The Salesforce Task object has strict field limits and does not support rich text. To ensure you can use current and future logging features, Aircall always logs to the Aircall Log object.

Any changes you make here apply only to new interactions. Existing Tasks and ALO records are not changed.

Where to find Aircall Log records in Salesforce

Once the updated Salesforce v3 package is installed and configured, you will see the Aircall Log object in Salesforce.

You can access ALO data in several ways:

From related records

• Add related lists for Aircall Logs on page layouts for objects such as Contact, Lead, Account, Opportunity, and Case.
• When a call or message is logged, the related Aircall Log records appear in those lists.

From the Aircall Log tab (if enabled)

• In Salesforce Setup, you can add the Aircall Log tab to your app navigation.
• Use list views and filters to see all logged interactions across your org.

From Tasks (when using “Both Task and Aircall Log object”)

• Each Task created by Aircall includes a lookup to the corresponding Aircall Log record.
• Agents can open the Task from the activity timeline, then click through to the Aircall Log for full details.

Use Aircall Log data in reports and automations

Because the Aircall Log object is a Salesforce custom object, you can:

• Build custom reports and dashboards based on Aircall Log records, such as:
  • Calls by queue, number, or agent
  • SMS volume and outcomes
  • AI based tags, topics, or sentiment fields (where available)
• Use ALO fields in Flows, Process Builder (if still used), or Apex to automate:
  • Follow up task creation based on AI outcomes or call topics
  • Case updates when specific IVR paths or queues are involved
  • Routing logic based on interaction type or direction

TIP:
Reference the Aircall Log object as the primary data source when you need rich call or message detail. If you continue to log to both Task and ALO, keep Task-based reports for high-level activity views and use ALO-based reports for detailed analytics.

Limitations and behavior to be aware of

Keep these Salesforce specific behaviors in mind when working with ALO:

No “ALO to Task” lookup

• Salesforce does not allow a lookup from a custom object to Task.
• The link between Task and Aircall Log is stored as a lookup on the Task that points to the ALO record.
• To surface related Tasks from the Aircall Log page, use related lists or custom report types that join Tasks and Aircall Logs.

Task field limits still apply when using “Both”

• When you log to both Task and ALO, Task still consumes Salesforce custom field slots.
• If you are already close to the Task field limit, consider switching to Only Aircall Log object logging and moving any Task only automations over time.

Package and integration requirements

• The Aircall Log object is available with the Salesforce V3 Aircall package that includes the unified logging model.
• The Aircall for Salesforce integration must be installed and active, and the package must be updated to the version that includes the Aircall Log object.

If you hit errors related to field limits or do not see the Aircall Log object in your org, contact your Salesforce admin to verify package version and field usage, then reach out to Aircall Support if needed.