Analytics β Twilio Call and Voicemail Metrics Aggregation
SmartBot's analytics panel aggregates missed call and voicemail data from your centers' phone lines, giving you a clear picture of how many guest calls go unanswered and how many voicemails are left β broken down by center and date. This article explains how to read that data and what actions to take when call volumes indicate a service gap.
Audience: Organization administrators and center managers who review SmartBot analytics to monitor call handling performance.
Before you begin
- SmartBot must be enabled for your organization with at least one center configured to use the voice channel.
- The missed call feature must be enabled for the centers you want to analyze. Contact your Zenoti administrator if you are unsure whether it is active for your centers.
- You need access to the analytics panel in SmartBot. If you do not see the analytics navigation item, ask your organization administrator to grant you the appropriate SmartBot access level.
Steps
Open the SmartBot analytics panel
- Sign in to the SmartBot admin console.
- In the left navigation, select analytics.
- The analytics dashboard opens, showing aggregated metrics across your centers.
Set the date range for call metrics
- Locate the date range selector at the top of the analytics panel.
- Select a start date and an end date for the period you want to review.
- The panel refreshes to display missed call and voicemail counts for the selected range.
Note: Dates are displayed in each center's local time zone. A call that arrives at 11:45 PM local time counts toward that day's totals for that center, even if the UTC timestamp falls on the following calendar day. This ensures that the numbers you see reflect your center's actual operating day.
Read missed call and voicemail metrics
The analytics panel shows the following call metrics per center:
| Metric | What it shows | Why it matters |
|---|---|---|
| Missed calls | Number of inbound calls not answered during the selected period | High missed-call counts signal that guests cannot reach the center, which may lead to lost appointments |
| Voicemails | Number of voicemail messages left by guests during the selected period | Elevated voicemail counts alongside high missed calls suggest staffing or coverage gaps during peak call hours |
Tip: Compare missed call counts week over week. A sudden spike often corresponds to a staffing gap, a holiday, or a high-demand promotional period. Identifying the pattern helps you decide whether to adjust staffing schedules or expand SmartBot's voice channel coverage.
Compare metrics across centers
- If your organization has multiple centers, the analytics panel lists each center as a separate row.
- Sort or filter by center to identify which locations have the highest missed call or voicemail volumes.
- Use this comparison to prioritize where operational changes β such as extended hours, additional staff, or expanded SmartBot voice handling β would have the greatest impact.
Worked example: Your organization has three centers. After filtering the analytics panel to the past 30 days, you see that Center A recorded 42 missed calls and 18 voicemails, Center B recorded 8 missed calls and 3 voicemails, and Center C recorded 61 missed calls and 27 voicemails. Center C's numbers suggest a consistent gap between call volume and available staff. You might review Center C's staffing schedule during peak hours or work with your administrator to expand SmartBot's voice channel handling at that center.
Understand how metrics are matched to centers
SmartBot matches each inbound call to a center by comparing the called phone number against the phone numbers provisioned for each center. You do not need to configure this matching manually β it happens automatically as part of the analytics aggregation process.
For organizations with a large number of centers sharing a Twilio account, the system fetches call data efficiently to keep the analytics panel responsive. Regardless of the method used, the metrics you see in the panel are accurate and attributed to the correct center.
Similarly, voicemail lookups run across all relevant calls in parallel, so the analytics panel reflects complete voicemail data without requiring additional action from you.
Note: Voicemail data includes a short buffer beyond your selected date range end to ensure that voicemails left near the boundary of the period are not missed. If you see a voicemail count that appears slightly higher than expected for the last day of your range, this buffer is the reason.
Tips
- Filter to a single center first. When investigating a specific center's call performance, narrow the date range to a single week and focus on one center at a time. Aggregated totals across many centers can obscure where the real issue lies.
- Track missed calls relative to total call volume. A center that misses 20 out of 25 calls needs different attention than one that misses 20 out of 200. Use the analytics panel alongside your phone system's total call data to calculate a missed-call rate.
- Correlate spikes with your appointment calendar. High missed-call days often align with busy appointment periods. Cross-reference the dates of your highest missed-call counts with your Appointment Book to confirm whether the spike corresponds to a fully booked day.
- Use voicemail counts as a leading indicator. Rising voicemail counts before missed calls spike can indicate that guests are beginning to give up before staff can answer. Addressing the voicemail trend early prevents the pattern from worsening.
- Review trends monthly. A single high-missed-call day may be an anomaly, but a consistently elevated count over four weeks indicates a structural issue worth addressing at the scheduling or staffing level.
Troubleshooting
The analytics panel shows no call data for a center, but the center does receive calls.
Verify that the voice channel is enabled for that center in SmartBot settings. If the voice channel is not active, SmartBot does not aggregate call data for that center. Ask your organization administrator to check the center's channel configuration.
Missed call counts appear lower than expected based on your phone records.
Call metrics are attributed to centers by matching the called phone number. If a center's phone number has changed recently and the new number has not been updated in SmartBot's configuration, some calls may not be attributed correctly. Contact your Zenoti administrator to confirm that all current center phone numbers are configured correctly.
Voicemail counts do not match the number of voicemails you see in the call logs panel.
The analytics panel and the call logs panel use the same underlying data but display it differently. The analytics panel shows counts aggregated by date and center for the selected range, while the call logs panel shows individual records. If you suspect a discrepancy, compare the date range in both panels to confirm they are set identically, then contact Zenoti Support if the difference persists.
The date range selector does not update the metrics.
Refresh the page and reapply the date range. If the panel still does not update, confirm that your SmartBot access level includes the analytics panel. Access levels are managed by your organization administrator.