ZenotiHelp

Analytics β€” Twilio Call and Voicemail Usage Metrics Aggregation

ZTZenoti Docs Team Updated September 20, 2026 4 min readGuide

SmartBot's analytics engine aggregates Twilio call and voicemail data into per-center, per-day metrics, giving you a clear picture of missed call volume and voicemail activity across your organization. This article explains how to interpret those metrics and what actions to take based on what you see.

Audience: Organization administrators and center managers who monitor SmartBot call analytics.

Before you begin

  • Your organization must have SmartBot enabled with the voice channel configured for at least one center.
  • You must have access to the analytics panel in the SmartBot admin console.
  • Call and voicemail metrics are calculated using each center's local timezone. Verify that each center's UTC offset is correctly configured before interpreting date-level data.

Steps

View call and voicemail metrics

  1. Sign in to the SmartBot admin console.
  2. Select analytics from the navigation panel.
  3. Review the metrics displayed for your organization. The analytics engine produces one row of data per organization, center, and local calendar date, so each center's figures are isolated from others.

Understand what each metric represents

The analytics dashboard surfaces two core call-related metrics:

Metric What it measures Why it matters
Missed calls Number of inbound calls that were not answered during the selected date range High missed call counts may indicate that your center's call capacity or IVR configuration needs attention
Voicemails Number of recordings left by guests on missed calls Voicemail volume relative to missed calls shows how many guests left a message versus hanging up

Filter by center or date

Use the filter controls in the analytics panel to narrow the data:

  • By center β€” Select one or more centers to compare missed call and voicemail volumes across locations.
  • By date β€” Select a date range to see trends over time. Dates reflect each center's local calendar day, not UTC.

Note: Because call timestamps are converted from UTC to each center's local timezone before being assigned to a date, a call that occurs late at night UTC may appear on the following day's metrics for a center in an earlier timezone. This is the expected behavior and ensures metrics align with each center's business day.

Interpret the data and take action

Use the metrics together to identify patterns and prioritize follow-up:

  • High missed calls, low voicemails β€” Most guests who could not reach the center did not leave a message. Consider whether your IVR flow offers a clear missed-call-to-SMS option so guests can self-serve via SmartBot rather than calling back.
  • High missed calls, high voicemails β€” Guests are attempting to reach the center and leaving messages. Review whether staffing or call routing adjustments are needed during peak hours.
  • Declining missed calls over time β€” Indicates that IVR improvements or increased SMS channel adoption are reducing unanswered call volume.
  • Spike on a specific date β€” Cross-reference with your appointment book to determine whether a promotion, staffing shortage, or system event drove the anomaly.

Worked example: A center manager notices that missed calls for their downtown center jumped from 8 to 34 on a Friday. Filtering the analytics view to that center and date, they confirm the spike is isolated to that location. They check the appointment book and find the front desk was understaffed that afternoon. They use this data to justify an additional front-desk resource during Friday afternoon shifts.

Compare centers to identify outliers

  1. In the analytics panel, set the date range to the past 30 days.
  2. View the missed calls metric across all centers in your organization.
  3. Identify centers with consistently higher missed call counts than the organizational average.
  4. For those centers, check the voicemail count to understand how many guests attempted to leave a message.
  5. Use the comparison to prioritize IVR configuration reviews or staffing changes at underperforming centers.

Tips

  • Compare missed call volume week-over-week to detect trends rather than reacting to single-day spikes. A steady upward trend is a stronger signal than an isolated outlier.
  • If a center has a high voicemail-to-missed-call ratio (most callers leave a message), ensure your team has a process for reviewing and returning those calls promptly β€” SmartBot aggregates the data, but follow-up is a manual workflow.
  • When comparing multiple centers, keep timezone differences in mind. A center operating on Eastern Time will show its late-evening calls on the same business-day date that a Pacific Time center has not yet reached.
  • Use the date filter to align your review cadence with your reporting cycle β€” for example, pulling the prior week's data every Monday morning.

Troubleshooting

Missed call count appears lower than expected for a center

The analytics engine assigns calls to dates based on each center's local timezone. If you are comparing the SmartBot analytics figures to a raw Twilio report that uses UTC dates, the totals will differ. Verify the center's configured UTC offset is correct, then re-check the date range in the analytics panel.

Voicemail count is zero even though guests have left messages

Voicemail recordings are associated with their corresponding missed calls. If a center's missed call count is also zero, the center's voice channel may not be active or the missed-call flow may not be enabled. Confirm the voice channel is configured for that center in SmartBot settings.

Metrics for a newly added center are not appearing

Analytics data is produced per organization, center, and local calendar date. A center that was added recently will only show data from the date its configuration became active. Allow at least one full business day after activation before expecting data to appear.

Data appears inconsistent across two centers in the same city

Even centers in the same city may have different UTC offsets configured. Check each center's timezone setting to confirm they match. If the offsets are misconfigured, the call dates will be assigned to the wrong calendar day.

Was this article helpful?
Your feedback helps us improve our documentation.