Skip to content

Admin Monitoring (Tenant View)

This chapter describes what tenant admins can monitor to ensure Conversation Analytics is working as expected.

What to monitor regularly

  • Transcription health (voice calls)
  • transcripts present for recent calls
  • language is correct
  • AI Task enablement
  • required tasks are enabled for the tenant
  • filters are not excluding everything
  • Output freshness
  • recent conversations show populated fields
  • dashboards update with expected latency
  • Override tracking
  • know which tasks have custom prompt/filter overrides
  • document and review changes periodically

Where to monitor

AI Tasks status

Administration > Speech Analytics > AI Assistant > AI Tasks

  • Check Enabled tasks
  • Review filters and prompt overrides (if any)

Conversation spot-checking

  • Pick a handful of recent conversations and confirm:
  • transcript/thread exists
  • insights show under Conversation Details → Analytics
  • explanations look reasonable

Dashboards trend checks

  • Watch for sudden discontinuities that may indicate:
  • prompt changes
  • filter changes
  • ingestion/transcription changes

Overrides visibility

Tasks with tenant-level overrides display an "Overridden settings" tag on the task card. Review these periodically to track what has been customized.

Note: Job status, engine details, and usage metrics are managed at the platform level and are not typically visible to tenant admins. If you need this information, contact your provider.

EDITOR NOTE: tenant-visible monitoring tabs

We need to confirm whether tenant admins see any of these tabs:

  • Usage
  • Overrides
  • Jobs
  • Engines

Ask product (choose all that apply):

  • A) Tenant admins can view Usage
  • B) Tenant admins can view Overrides list
  • C) Tenant admins can view Job status
  • D) None of the above (provider-managed only)

Best-guess recommendation:

  • If a tenant-visible Overrides tab exists, include instructions to review it monthly.
  • If job status is not visible, document a "what to collect for support" checklist.

What to collect for support (when something is wrong)

When contacting your provider/MiaRec support, collect:

  • tenant name / ID
  • time range of affected conversations
  • example conversation IDs
  • which AI Task(s) are missing or wrong
  • whether the tasks are enabled and any overrides were made
  • screenshots of:
  • conversation analytics view
  • task configuration (prompt/filter)