This glossary defines the key terms used throughout Aircall’s Analytics dashboards. These definitions will help you interpret metrics and understand how calls, users, and performance data are tracked.

Tip: Within the Analytics and Live Monitoring dashboards, most metrics include built-in tooltips.
Hover over the “i” icon next to a metric to view its definition and calculation directly within the dashboard.
Screenshot 2025-11-10 at 11.13.42.png

Calls

TermDefinitionNotes / Examples
CallAny inbound or outbound call made or received, whether answered or not.Internal calls (made between users within the same company) are excluded.
Inbound callA call initiated by an external caller and received by a company-owned Aircall number.
  • Internal calls are excluded.
  • When a call is transferred between agents, it is counted as a single call attributed to the last participant. 
  • When a call passes through an IVR and is transferred to another Aircall number, it is considered one call attributed to the final line. 
  • An outbound call that is successfully transferred to another agent is tracked as an inbound call. 
  • If the transfer is unsuccessful, it remains tracked as an outbound call.
Calls waitingAn inbound call that is waiting to be picked up by a user (when users are unavailable or ringing).
  • Calls still in the IVR or welcome message are excluded. 
  • This metric is used in Live Monitoring only.
Call statusThe current stage of a call, such as ringing, in call, or in IVR.Used in Live Monitoring. See the full list of call statuses in our article Call Statuses in Live Monitoring
Answered inbound callAn inbound call where a user or agent connected with the caller. 
Unanswered inbound callAn inbound call where a user or agent did not connect with the caller. 
Unanswered call handled by AI Voice AgentAn unanswered inbound call handled by the AI Voice Agent, either as a fallback or as the primary interaction. 
Time to AnswerFor answered inbound calls, the time between when the caller starts ringing an agent or enters a queue and when the call is picked up.Time spent in the welcome message, IVR menus, or with the AI Voice Agent is excluded.
Inbound calls within SLAAnswered inbound calls where the waiting time before connection did not exceed the SLA.
  • The SLA is determined by the SLA (in seconds) filter in Analytics, or by the SLA setting in Live Monitoring.
  • In certain dashboards this is sometimes referred to as Inbound in SLA and Answered within SLA
  • Calls outside of business hours are by default excluded in Live Monitoring dashboards. In Analytics dashboards that need to be specified using the available Hours filters.
  • This metric uses the same Time to Answer definition in both Live Monitoring and Analytics.
Inbound calls breaching SLAAnswered inbound calls where the waiting time before connection exceeded the SLA.
  • The SLA is determined by the SLA (in seconds) filter in Analytics, or by the SLA setting in Live Monitoring.
  • Uses the same Time to Answer definition in both Live Monitoring and Analytics.
Outbound callA call made by an Aircall user to an external recipient, whether connected or not.
  • Internal calls are excluded.
  • When an inbound call is transferred to an external number, it is counted as an outbound call to that number.
Connected outbound callAn outbound call that was successfully connected with the recipient or their automated responder.In the User KPIs section of the Monitoring page and the Analytics+ dashboard, coaching sessions are included. When a user coaches another agent, it counts as a connected outbound call.
Subsequent callA subsequent call is a call that was made to or from an external caller who previously made an unanswered call.
  • Only connected outbound calls are included. 
  • Unanswered inbound calls with a subsequent call are unanswered calls where the same caller has been connected with an agent within 24 hours. This connection may happen through an inbound call from the same caller, a callback, or any outbound call made to that caller. When this occurs, each unanswered call made by that caller within the 24 hour period is considered to have had a subsequent call.
  • If there is more than one consecutive unanswered inbound call from the same caller, all unanswered calls made by that caller will be considered to have had a subsequent call if that caller is successfully connected to an agent later.

    Examples:

  • A caller phones twice with no answer, then calls again 23 hours later and reaches an agent. Both unanswered calls are considered calls with a subsequent call.

  • A caller phones and receives no answer. An agent calls back successfully 23 hours later. The unanswered call is considered a call with a subsequent call.

  • A caller phones and receives no answer, then calls again after 25 hours and reaches an agent. The unanswered call is not considered a call with a subsequent call, since the connection happened after 24 hours.

Callback requestOccurs when a caller requests a callback after not reaching an agent.The request may be completed (called back) or not. There is no time limit for a callback to be considered.
Unique callersAll inbound calls from the same phone number during a specific period are counted as one unique caller.

If a single contact has multiple phone numbers, each number is counted as a separate unique caller. 

Example: On September 12, two calls from +33 623 99 99 XX and three from +33 625 35 67 XX equal five calls but only two unique callers.

Call Routing and IVR

TermDefinitionNotes / Examples
IVR widgetIn Smartflows, a menu that allows callers to select how their call is redirected.In Analytics, the name of the last IVR widget (menu) the caller passed through is stored.
IVR branchIn Smartflows, one of the options a caller selects within an IVR widget.Analytics records the name of the last branch chosen by the caller.

For more information, see our article Smartflows widgets: The IVR widget and voicemail notifications

Ringing attempts

TermDefinitionNotes / Examples
Ringing attemptOccurs whenever Aircall notifies a user’s app or device of an incoming call.
  • Internal calls are excluded.
  • If a call rings sequentially to multiple users, each instance counts as a separate attempt.
  • If a call rings simultaneously to multiple users, each instance also counts as a separate attempt.
  • Calls not picked up on the mobile app or redirected elsewhere are excluded.
Picked upA ringing attempt that results in the user or agent connecting with the caller.
  • If a call rings simultaneously to Users A and B, and User B answers, there are two attempts: one picked up (User B) and one not picked up (User A).
  • If a call rings sequentially to Users A and B and User B answers, there are two attempts: one picked up and one not picked up. 
  • If a call is transferred and both users answer, there is one call (attributed to the last participant) but two picked-up attempts.
Not picked upA ringing attempt that does not result in the caller connecting with a user or agent.
  • If a manually transferred call is unanswered by the target user, it is not counted as not picked up. 
  • Sequential or simultaneous attempts are tracked individually.
DeclinedAn inbound call that was explicitly rejected by the user.Edge cases that are excluded from this count are listed under Not picked up.

 

Individuals involved in a call

TermDefinitionNotes / Examples
CallerFor inbound calls, the external number or person calling an Aircall number. 
RecipientFor outbound calls, the external number or person being called by an Aircall user. 
CustomerEither the caller or recipient of a call, depending on the call direction. 
User (or agent)An Aircall user with the Agent role, who can receive inbound calls and make outbound calls.Missed or unanswered calls are not associated with any user.
Call participantAny user, agent, or line involved in a call.Calls can include multiple participants, for example when routed through an IVR or transferred between users. The last participant is considered the main participant.

Messaging

TermDefinitionNotes / Examples
SMS segmentA 160-character unit used by carriers to count SMS messages. Longer messages (up to 1600 characters) are divided into multiple segments but displayed as one message.
  • Applies only to SMS, not MMS. - Data for this metric is available from January 15, 2024, and complete from January 16, 2024. 
  • For more details, see our article French messaging limitations.
MMS Multimedia Messaging Service, an extension of SMS that supports messages containing multimedia files such as images or PDFs. 

Network Diagnostics

TermDefinitionNotes / Examples
Media regionThe geographic region where the media server handling the call is located.The location affects latency and call quality.
External media IPThe public IP address used to route media traffic during the call.This may differ when using proxies or TURN servers.
APP Jitter AvgThe average variability (in milliseconds) in packet arrival times.This measures network stability.
APP MOS AvgThe average Mean Opinion Score (MOS) ranging from 1 to 5, which represents perceived call quality.Higher scores indicate better audio quality.
APP Packet Loss %The percentage of packets lost during transmission.This reflects the reliability of the network connection.
APP RTT AvgThe average Round Trip Time (in milliseconds), which measures the latency between sending and receiving data. 
APP Flags SummaryA list of significant network events that occurred during the call, such as high jitter, latency, packet loss, ICE failure, or low MOS.This summary highlights potential network issues affecting call performance.
CallsThe total number of calls processed, including inbound calls that were picked up and outbound calls that were connected.Unconnected calls and internal calls are excluded. Transfers between users count as two separate calls.
ICE failureAn error that occurs during the process of establishing connectivity using the Interactive Connectivity Establishment (ICE) framework. 
Calls with poor networkCalls where jitter, latency, packet loss, or MOS exceed quality thresholds. 
Calls with good networkCalls where jitter, latency, packet loss, or MOS are close to, but do not exceed, quality thresholds. 
Calls with excellent networkCalls with optimal quality metrics (low jitter, low latency, minimal packet loss, and high MOS). 

Other

TermDefinitionNotes / Examples
User statusIndicates whether a user is available to handle calls, busy, or unavailable.For more details, see our article Analytics: User status list
After Call Work (wrap-up)The period after a call when users complete follow-up tasks such as tagging or adding notes.
  • When a specific wrap-up time is set, it begins when the call ends and finishes when the time elapses or the user manually changes their status. 
  • When mandatory tagging is active, it ends once the call is tagged. 
  • When both conditions apply, it ends only when the call is tagged and the wrap-up time has elapsed or the user manually sets their status to Available.

For more information, see our articles: Setting up your Wrap-up Time and Mandatory Call Tagging.