Skip to main content
Analyzers let you run post-call analysis on interactions so you can extract structured information from transcripts and call data. You can use them to identify outcomes, classify conversations, and make call review more consistent.

​
What Analyzers Do

You can use analyzers to:
  • extract structured data from completed calls
  • classify calls by outcome, sentiment, or intent
  • power reporting and downstream workflows
  • review call quality more consistently

​
How to Add Analyzers

You can create analyzers in the dashboard and then enable them for the relevant agents, or make them always enabled for all agents. When you create an analyzer, you define:
  • a title
  • a prompt
  • an output type
  • which agents the analyzer should run on
This is useful when you want to standardize the way insights are extracted across many calls.

​
Output Types

Analyzers can return different kinds of outputs depending on what you want to capture. Available output types include:
  • free text
  • number
  • boolean
  • enum
  • structured data
Choose the simplest output type that still gives you the result you need. For example, if you only need a yes or no answer, a boolean output is usually better than free text.

​
How to Define Structured Data

If you want an analyzer to return multiple fields in a consistent format, you can use structured data output. In the dashboard, the Structured Data Fields section lets you switch between UI and Raw. You can define structured output in two ways:
  • use the UI to add fields and set the type for each field
  • use raw text fields to define the structure manually
In the UI view, you can add fields one by one and define:
  • the field name
  • the field type
  • a description
  • whether the field is required
Available field types in structured output include:
  • string
  • number
  • boolean
  • object
  • array
If you switch to Raw mode, you can define the same structure directly as JSON. The raw editor expects a JSON array of field definitions. For example: 
[
  {
    "name": "customerName",
    "type": "string",
    "description": "The customer's full name",
    "required": true
  },
  {
    "name": "issueResolved",
    "type": "boolean",
    "description": "Whether the customer's issue was resolved",
    "required": true
  }
]
Structured output also supports nested objects and arrays, which is useful when you need to capture more complex results in a predictable JSON structure. This is useful when you want to collect data in a format that is easier to review, filter, export, or use in downstream workflows.

​
How Analyzers Work

After a call is completed, Simple AI can run any analyzers associated with that interaction. If an analyzer is always enabled, it can run on calls across all agents. Otherwise, it runs only for the agents where it has been enabled. Analyzer results are stored with the call, which makes them available later for review, filtering, exports, and reporting.

​
Rerun Analyzers on Previous Calls

If you create a new analyzer or update the prompt or output you want, you can rerun that analyzer on previous calls. This is useful when:
  • you added a new analyzer and want to backfill older calls
  • you improved the analyzer prompt and want updated results
  • you want to reprocess a date range for reporting or QA
When you rerun an analyzer, Simple AI can reprocess either eligible calls from a date range you select or an individual call when you want to refresh results for a specific interaction.

​
How Reruns Work

Reruns are supported for previous calls and can be applied across a date range or on an individual call. Depending on how you trigger the rerun, it may apply to:
  • a single call
  • all calls in the selected date range
  • calls associated with the agents where that analyzer is enabled
If you are using date range reruns, it is a good idea to choose a clear range so you only reprocess the calls you actually want to update.

​
Best Practices

Analyzers work best when the prompt is very specific about what should be extracted and what format the answer should use. For example, instead of writing Analyze whether this call went well, it is usually better to write Return true if the customer's issue was fully resolved during the call, otherwise return false. If you are using structured outputs, define the fields as clearly as possible so the result is easier to use later.

​
Video Demo

​
Creating and Rerunning Analyzers

​
Rerunning Analyzers on Individual Calls