ZenotiHelp

Call Logs β€” Bot Name Shown on Voicemail Records

ZTZenoti Docs Team Updated November 3, 2026 3 min readGuide

When you review voicemail records in SmartBot, each entry includes the name of the AI agent configuration that handled the call. This lets you quickly identify which SmartBot setup received a missed call β€” useful when your organization runs multiple centers with different configurations.

Audience: Organization administrators and center managers who review call logs and voicemail records in SmartBot.

Before you begin

  • Your organization must have the missed-call feature enabled for at least one center. Contact your Zenoti account team if you are unsure whether this is active for your organization.
  • You must have access to the SmartBot admin console with call log panel access enabled for your account.
  • To query voicemail records across all centers, you need organization-level access. To view records for a single center, center-level access is sufficient.

Steps

View the bot name on a voicemail record

  1. Sign in to the SmartBot admin console.
  2. In the left navigation, select callLogs.
  3. The call logs list displays your voicemail records. Each record includes a bot name field that shows which AI agent configuration handled the call.
    • For a center-level view, the bot name reflects the configuration associated with that center.
    • For an organization-level view, the bot name reflects the configuration associated with the organization.
  4. Select any voicemail record to open its detail view and confirm the bot name displayed alongside the voicemail.

Note: The bot name shown in a voicemail record is determined at the time the call is received and reflects the AI agent configuration active for that center at that moment. If you have updated the configuration since the call was received, the record still shows the name that was active when the call came in.

Interpret the bot name field

The bot name field helps you answer two questions:

  • Which configuration handled this call? Use the bot name to cross-reference your center configurations, especially if you manage multiple centers with distinct SmartBot setups.
  • Is this an org-level or center-level record? Organization-level queries return voicemail records across all centers, each tagged with its own bot name so you can distinguish activity by configuration.

Tip: If voicemail records show an unexpected bot name, verify the AI agent configuration assigned to that center. For organization-level communication settings, see the Configurations category.

Tips

  • Filter by center before reviewing bot names β€” If your organization has many centers, narrowing the call log view to a specific center first makes it easier to confirm that the correct AI agent configuration is handling calls for that center.
  • Use the bot name to audit configuration changes β€” After updating a center's SmartBot configuration, check a few recent voicemail records to confirm the new bot name appears as expected on calls received after the change.
  • Pair call log reviews with analytics β€” Reviewing which bot configuration handled calls alongside voicemail volume helps you identify centers that may need configuration adjustments. See View SmartBot analytics for guidance on interpreting call and voicemail metrics.

Troubleshooting

The bot name field is blank on a voicemail record. A blank bot name can occur if the voicemail was received before a bot configuration was fully associated with the center. Verify that the center has a complete SmartBot configuration saved, then monitor new records to confirm the bot name populates going forward.

The bot name shown does not match the current configuration for that center. Voicemail records capture the bot name at the time of the call. If you updated the center's configuration after the call was received, the record will still display the previous bot name. This is expected behavior and does not indicate an error.

The callLogs panel is not visible in the SmartBot admin console. Call log panel access requires the missed-call feature to be enabled for your organization. If the panel does not appear in the navigation, contact your Zenoti account team to confirm the feature is active and that your account has the appropriate access level.

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