Overview
Metrics and Variables is the administrator screen where you tune the values that Ender Turing's analytics run on. It is not a day-to-day screen: the settings here apply to the whole workspace and change how conversations are measured, how quality figures are displayed, and how generative AI features connect to model providers.
The screen is organised into three collapsible panels:
Panel | What it covers |
Variables Configuration | Speaker labels, silence and threshold values, quality-metric formatting, the reasonable-call filter, manual conversation creation, and client search aliases |
EnderGPT | AI provider keys, the model used for each AI task, AutoQA re-scoring, LLM usage reporting, and prompt templates |
Repetitive Call Configuration | The rules that decide when a conversation counts as a repeat contact |
Each panel is saved on its own.
How It Works
Finding the screen
Open Settings from the main navigation.
Select Settings in the Settings menu (the entry with the tune icon).
At the top of the page, switch to the Metrics and Variables tab.
If you do not see the Metrics and Variables tab, your role does not meet the access conditions below — the page opens on the Settings tab instead.
Who can use it
Reaching this tab requires three conditions at once. All of them must be true:
Condition | What it means |
You can manage system settings | The core requirement for every field on this screen |
You can manage Enders (automations) | Needed because the reasonable-call filter reuses the automation filter builder |
You can view conversations | Any level is enough — all conversations, your team's, or your own |
If any condition is missing, the tab is hidden and the page falls back to the general Settings tab. There is no read-only mode: anyone who can open the tab can edit and save every field that is visible to them.
The EnderGPT panel appears only if you can manage system settings and either your workspace allows AI model selection or your account has extended platform access. In workspaces where Ender Turing manages model selection centrally, the whole panel stays hidden and models are maintained by Ender Turing.
Saving changes
Every panel has its own Save button at the bottom. Saving one panel does not save the others, so save each panel you edited before leaving the page.
Fields are validated as you type. If a required value is missing or out of range, the error appears under the field and Save does nothing until you correct it. A confirmation message appears once the save succeeds.
There is no recalculate or reprocess action on this screen.
Variables Configuration
The first panel holds the general analytics variables.
Setting | Type | Notes |
Unknown speaker label | Text (required) | The label used for a speaker the system could not identify |
Agent display name | Text | How the agent side is named in AI prompts such as AutoQA and summaries. Leave empty for the default Agent. Examples: Operator, Lead |
Client display name | Text | The same for the customer side. Leave empty for the default Client. Examples: Customer, Guest |
Silence min. significant | Number, in seconds | The shortest pause treated as a meaningful silence |
SER sensitivity | Number between 0 and 1 | Sensitivity used for speech emotion recognition |
Use phrase expansion (e.g. morphological cases) for tags | Checkbox | Lets Ender Turing generate grammatical variants of your tag phrases so tags also match inflected forms |
Short conversations preferred (uncheck for sales) | Checkbox | Tells the dashboard how to group handling-time results. Leave it on for support-style operations; turn it off for sales, where longer conversations are not a bad sign |
Script Adherence Threshold | Number between 0 and 1 | How close a phrase must be to your script before it counts as adherence |
FCR Resolved - Value / FCR Not Resolved - Value | Text | The values in your incoming data that mean "resolved" and "not resolved", used for First Contact Resolution reporting |
Quality Metrics Decimal Precision | Whole number, 0 to 4 | How many digits appear after the decimal point in percentage metrics. Values of exactly 0% or 100% are always shown without decimals |
Reasonable call filter | Filter builder | Defines which conversations are complete enough to be worth measuring |
Allow empty conversation creation | Checkbox | Lets users create a conversation manually, without a recording, so it can still be scored |
Client search aliases | JSON editor | Maps a customer name to the identifiers it should also match in search |
Two fields behave differently from plain inputs:
Reasonable call filter opens the same filter builder used by Enders. The default filter keeps conversations longer than 20 seconds where both sides actually spoke. One condition is not accepted here: filters built on the interval to the next conversation are rejected when you save, with the message "Next conversation interval is not supported in reasonable call filters".
Allow empty conversation creation reveals a JSON editor underneath when you switch it on. There you define the extra fields — code, title, and type — that appear on the manual creation form, for example a CRM link or a claim number.
Client search aliases is also a JSON editor. It expects a mapping such as {"name1": ["phone1", "phone2"]}. Very large alias lists switch to a plain text box instead of the highlighted editor so that typing stays responsive.
EnderGPT
This panel connects Ender Turing to your AI providers and decides how the generative AI features behave. It is hidden entirely in workspaces where Ender Turing manages these values for you.
Provider credentials
OpenAI API Key
Google Gemini API Credentials (json)
DeepSeek API Key
DeepSeek API Base URL (optional)
Keys are masked when the page loads: only the first and last few characters are shown, with asterisks in between. That masked value is safe to leave alone — save the panel without touching the field and the stored key is preserved. Use the eye icon to reveal what you are typing while entering a new key.
AutoQA re-scoring
Re-Score if lower then threshold — when on, a conversation that scores below your threshold is scored a second time with the re-scoring model, so borderline results get a closer look.
Re-scoring threshold — a value from 1 to 100, expressed as a percentage of the scorecard's maximum score. The field stays disabled until the checkbox above is on.
Usage reporting
LLM cost and provider-token reporting are always enabled. There are no reporting checkboxes in this panel. Users who can manage both System and Automation settings can view USD, input, cached input, output, and total tokens in Settings > System > Usage. See System for how the metrics are used and how missing historical token data is displayed.
Privacy and logging
Audit LLM/GPT content in Logs — records the full request and response content of AI operations in the logs.
Enable anonymization on LLM call — on by default. Personal data is masked in the transcript before it is sent to the model provider. Turning this off sends the raw text.
Categorisation limit
Max LLM Categorization Attempts — a whole number from 3 to 10, default 4. It caps the categorisation attempts made for a single conversation, typically one rule-based attempt plus the AI-based ones.
Models per task
Each AI task has its own model slot, so you can pair a fast model with a routine job and a stronger model with a job that needs it:
Slot | Used for |
AutoQA model | The first pass of automated quality scoring |
AutoQA re-scoring model | The second pass, when re-scoring is enabled |
Summary model | Conversation summaries |
Topics model | Topic classification |
EnderChat model | Chat with EnderGPT |
Internal model | Internal AI tasks, such as expanding tag phrases |
Each slot takes a provider and a model name. Depending on the model you pick, one extra control appears:
Reasoning effort — for OpenAI and Azure models. Choose from none, minimal, low, medium, high, or xhigh, or leave it at Not set — model default. Not every model accepts every level; the provider reports an error if the combination is not supported.
Thinking budget (tokens) — for Gemini models that support thinking. Enter
-1to let the model decide, or a whole number from 1 to 32768.
Changing the provider clears any reasoning or thinking value you had set, so re-check it after switching.
Prompt templates
AutoQA - Prompt template (jinja2)
Summary - Prompt template (jinja2)
Topics - Prompt template (jinja2)
These are the base templates behind the corresponding AI features. For everyday prompt work, use Gen AI Studio instead — it offers versioning, a usage panel, and a safer editing experience.
Repetitive Call Configuration
The last panel defines when a conversation should be treated as a repeat contact — a customer coming back about something that was not finished the first time. Ender Turing looks at the previous conversation with the same caller and links the two when it matches your rules.
Setting | Type | Notes |
Previous conversation was with DURATION >= | Number (required) | The previous conversation must last at least this long to count. |
Previous conversation DIRECTION IN | Multi-select (required) | Inbound, Outbound, or both. At least one must stay selected |
Previous conversation was handled by same Queue (Prev call "Queue") | Checkbox | Link the two conversations only when they went through the same queue |
Previous conversation was ended with | Multi-select | Restrict to how the previous conversation ended: Agent, Client, Call Transfer, System, Error, or Other. Leave empty to accept any |
Previous conversation match any CRM statuses | Multi-select | Restrict to specific CRM statuses. The list is filled from the CRM statuses present in your data. Leave empty to accept any |
The two required fields are enforced on save: a duration of 0 or more must be present, and at least one direction must remain selected.
Things to keep in mind
Changes here affect the whole workspace and every user in it, not just your own view.
Save each panel separately — moving to another panel does not save the one you were editing.
Masked API keys are safe to leave untouched; retyping a key is only necessary when it actually changes.
Some fields on this screen overlap with work that has a better home elsewhere: prompts belong in Gen AI Studio, and workspace-wide preferences such as language, retention, and email live on the neighbouring Settings tab.
