Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Call Insights Dashboard


Voice Insights Dashboard 2022.

The Insights Dashboard(link takes you to an external page) is a powerful aggregation tool that allows users to filter on specific dimensions like call type, timeframe, number prefix, country code, and automatically updates the data visualizations to take into account the filter criteria. Key sections of the Dashboard include the total number of calls placed on Twilio, the average length of those calls, who hung up, call completion rate (ASR), calls with high PDD, and calls whose quality performance may have been impacted by network conditions. Call data can be visualized in a number of ways for each metric, and calls can be exported to .csv.

The user experience of voice communication is measured by two key components - call connectivity and audio quality. Connectivity issues can originate from the user's handset, the last mile link between their phones and the cell tower, their carrier network, or from within Twilio's network. Congestion, spotty coverage, handoff failures and numerous other issues could prevent you from reaching your users, or cause connected calls to drop. Voice Insights Connectivity dashboards enable you to rapidly identify connectivity problems by giving you real-time visibility into four key metrics:

  1. Connection Rate: The percent of total calls that reached the destination. Canceled and failed calls are excluded from this calculation.
  2. High Post Dial Delay (PDD): Calls where the number of seconds elapsed between dialing the last digit of the phone number and the start of ringing exceeds local thresholds. High PDD can sometimes be reported as "dead air", "one way audio", or even "dropped calls".
  3. Network Affected: Percentage of calls adversely affected by poor network quality. Issues that indicate poor network quality include: packet loss, jitter, and latency.
  4. Who Hung Up: Breakdown of calls in which the SIP BYE message was received from the caller or callee. The BYE message signals the termination of an answered call. Calls that have not been answered will not have a BYE, so they will be excluded from the results.

Start by selecting the filters as shown below.


Filters

filters page anchor
Voice Insights Dashboard Filter 2022.

1. Account View Selection: Parent Account Only. Allows for toggling between Account and Subaccount Dashboards.

2. Time Range Picker: Choose from the various call types that can occur on the Twilio platform.

3. Filter Builder: You can narrow down the metrics you are viewing by choosing to view the data for a specific phone number, number prefix, country, device type, and users' carrier network. The applicable values are listed below.

FilterDescription
To Phone NumberThe phone number of the called party
From Phone NumberThe phone number of the calling party
To Client NameRegistered Client name of the called party; e.g. client:alice. Voice SDK calls only.
From Client NameRegistered Client name of the calling party; e.g. client:alice. Voice SDK calls only.
Verified CallerTrue/false. True indicates the caller ID has been received SHAKEN/STIR attestation(link takes you to an external page) value of A. Any other value, or absent attestion will be false.
Branded CallTrue/false. True indicates that the branded call details were successfully presented to the called party. False indicates that the branded call details were provided, but not successfully presented.
Branded Call CallerBrand name caller ID provided during Branded Call creation.
To SIP URISIP URI of the called party; e.g. sip:bob@pbx. SIP Interface and Elastic SIP Trunking calls only.
From SIP URISIP URI of the calling party; e.g. sip:bob@pbx. SIP Interface and Elastic SIP Trunking calls only.
To CarrierThe carrier of called party
From CarrierThe carrier of the calling party
To Country CodeISO Alpha-2 country code(link takes you to an external page) of the called party
From Country CodeISO Alpha-2 country code(link takes you to an external page) of the calling party
To Device TypeLandline, Mobile, or VoIP connection of the called party
From Device TypeLandline, Mobile, or VoIP connection of the calling party
To Number PrefixCountry code and area code or exchange for the called party
From Number PrefixCountry code and area code or exchange for the calling party
SIP ResponseThe last SIP response code received in the dialog.
Call StateThe final call status(link takes you to an external page).
Network AffectedCarrier, SIP, or Trunking calls tagged with jitter, packet loss, or latency.
Network Affected (SDK)Voice SDK calls tagged with jitter, packet loss, or latency. Twilio Voice SDK calls only.
To BrowserBrowser used to answer WebRTC calls. Twilio Client JavaScript SDK only.
From BrowserBrowser used to place WebRTC calls. Twilio Client JavaScript SDK only.
To SDK TypeJavaScript, iOS, or Android. Twilio Voice SDK calls only.
From SDK TypeJavaScript, iOS, or Android. Twilio Voice SDK calls only.
To SDK VersionTwilio SDK version number. Twilio Voice SDK calls only.
From SDK VersionTwilio SDK version number. Twilio Voice SDK calls only.
To Client Registration RegionThe Twilio region where the Client was registered. Twilio Voice SDK calls only.
From Client Registration RegionThe Twilio region where the Client was registered. Twilio Voice SDK calls only.
Edge Location (Region)The media region where the Twilio gateway handled media.
Client IP AddressThe IP address of the Client user. Twilio Voice SDK calls only.
App NameThe application name provided when creating the Twilio device in JavaScript, iOS, and Android SDKs.
App VersionThe application version provided when creating the Twilio device in JavaScript, iOS and Android SDKs.
Call DirectionThe type of call and associated direction: inbound, outbound API, outbound <Dial>, trunking originating, trunking terminating.
Silence DetectedTrue/false. True indicates Twilio detected silence on one of the media streams for the call. Depending on your use case, silence may be expected; e.g. one-time password delivery.
Answered by (AMD)The Answered By value for the summarized call based on Answering Machine Detection (AMD). One of unknown, machine_start, machine_end_beep, machine_end_silence, machine_end_other, human or fax. Refer to AMD for more detail.
Annotations: Answered ByA filter for subjective feedback identifying who answered the call. One of machine or human.
Annotations: SpamTrue/False. A filter for subjective feedback identifying if the call was spam or not.
Annotations: Call ScoreA filter for subjective feedback regarding call score. A range of 1-5 indicates the call experience score, with the following mapping as a reference for the rated call [5: Excellent, 4: Good, 3 : Fair, 2 : Poor, 1: Bad].
Annotations: Connectivity IssuesA filter for subjective feedback regarding call connectivity issues. One of no_connectivity_issue, invalid_number, caller_id, dropped_call, or number_reachability.
Annotations: Quality IssuesA filter for subjective feedback regarding call quality issues. One of no_quality_issue, low_volume, choppy_robotic, echo, dtmf, latency, owa, static_noise.

Connection Rate allows you to filter by call state.

Connection Rate.

The Voice Insights account-level dashboards provide trends on the following metrics:

MetricDescription
Who Hung UpWho disconnected the call, based on the direction of the SIP BYE event. Percentage is calculated based on the total number of errors with respect to the total calls.
Connection RateTotal calls completed with respect to the total number of calls. Documentation for the applicable call status values is here.
High PDDPost-dial-delay (PDD) is the number of seconds elapsed between dialing the last digit of the phone number and the start of ringing. The tab represents percentage of total calls with high Post-Dial-Delay (PDD), compared against 99th percentile of all Twilio calls to the destination country.
Network AffectedThis tab shows percentage of calls adversely affected by poor network quality. Issues that indicate poor network quality include packets arriving out of order (jitter), never arriving (packet loss), and taking a long time to arrive (latency). For Carrier and SIP/Trunking call types, high packet loss is defined as 5% cumulative packet loss, high jitter is defined as average jitter of more than 5 milliseconds, and high latency is defined as Twilio-internal RTP traversal time of greater than 150 milliseconds. For SDK calls high jitter is defined as 30 milliseconds or higher for 3 out 5 consecutive samples, and high packet loss at 1% or higher for 3 out of 5 consecutive samples.

Who Hung Up ValuesDescription
CallerThe BYE message was received from the "From" number
CalleeThe BYE message was received from the "To" number
ErrorA SIP error code was received on the call. The count is based on the total number of server(link takes you to an external page) or global(link takes you to an external page) errors seen.

The call logs view helps you drill down into a subset of calls with specific issues. To get to the call logs, click on the phone icon towards the right of the screen as shown below. Up to 2000 results can also be exported to a comma-separated value file.

Call Logs View.

Rate this page: