Skip to main content

General Settings

Configure organization-wide preferences: default language, audio retention, dispute limits, agent visibility on dashboards, scorecard behavior, and the SMTP server for outgoing email. This article is automatically maintained (general-settings).

Overview

The Settings page brings together organization-wide preferences for your Ender Turing workspace. From a single screen you can:

  • Set a default language for conversations whose language could not be detected automatically.

  • Decide how long recognized audio files are kept before automatic deletion.

  • Set dispute limits for agents.

  • Control what agents see on dashboards, in tags, and in automated scoring.

  • Adjust scorecard scoring defaults.

  • Configure the SMTP server used for invites, password resets, and email reports.

The page is split into two cards:

  • General Settings — the main block of platform-wide toggles and values.

  • SMTP Settings — the outgoing-email server used for system messages.

These settings affect every user in the workspace. They are intended for administrators rather than day-to-day users.

How It Works

Accessing the Settings page

  1. Open Settings from the main navigation.

  2. In the Settings menu, select Settings (the entry with the tune icon, directly below Scorecards and above Apps).

The page may also expose a Metrics and Variables tab next to Settings; that tab is documented separately and is not covered by this article.

Who can use it

The Settings entry appears in the navigation for users whose role grants either the analytics-settings or system-settings management permission. Without one of those permissions, the entry is hidden and the page cannot be opened.

Opening the page is not the same as being able to save changes:

  • Saving any field requires the system-settings management permission. Users who can open the page through the analytics-settings permission alone cannot save: Save changes is rejected by the backend. They also do not see the SMTP card values or other system-only fields — those fields are filtered out of the response and the SMTP card therefore shows blanks or defaults rather than the configured values.

  • The Default language field also requires the Ender Turing staff permission. System-settings managers without it can see the current value but cannot save a change to it.

  • The Max days to store recognized audio files field is shown and editable only for users with the system-settings management permission. Other users do not see the field at all.

In both cloud (multi-tenant) and on-premises (single-tenant) deployments, every field on the page except Default language is editable for any system-settings manager. No workspace superuser is required. To choose a Company logo, you also need permission to read EnderDrive, because the file picker loads its folders and files from EnderDrive.

When a field is read-only for your role, it still shows the current value so you can see how the workspace is configured.

Saving your changes

Each card has its own Save changes button at the bottom. Changes you make to the General Settings card are saved separately from changes to SMTP Settings. Use the corresponding Save changes button for the card you edited.

General Settings

The General Settings card collects the following preferences. They are grouped here by topic for clarity, but on the page they appear as a single scrolling list.

Branding

  • Company logo — pick an image stored in EnderDrive (PNG, JPEG, or JPG) to use as the workspace logo. Click Set as company logo to open the file picker. A preview of the selected file appears below the selector.

Regional and recognition preferences

  • Default language — the language Ender Turing falls back to when an audio file does not specify a language and automatic language detection cannot decide one.

  • First day of week — choose Monday or Sunday. This shapes how date pickers across the platform present weeks (the calendar grid that opens for a date or date-range filter). It does not currently change how weekly report data is grouped.

  • Default phone prefix — a dial prefix used to broaden phone-number matching and customer lookup. When a search or lookup runs against a local number that has no country code, Ender Turing also tries the prefixed variants so the same contact can be found. The setting does not rewrite numbers as they are stored from incoming calls — the original number is kept; the prefix only widens which stored numbers match a query.

  • Convert spoken numbers in transcripts — controls whether spoken numbers are converted to digits for transcripts produced through the multichannel diarization path. This covers calls that arrive with separate agent and client channels and are split per channel; it does not currently rewrite transcripts produced through the single-channel fallback path, which stores the speech-to-text result unchanged.

    • Off — leave the recognized words unchanged.

    • On — replace the spoken form with digits, for example "two thousand five hundred sixty eight" → "2568".

    • On (Extended) — keep both forms, for example "2568 (two thousand five hundred sixty eight)".

  • Agent prefix — a string used as a prefix for agent identifiers in your workspace.

Audio retention

  • Max days to store recognized audio files — how long audio files are kept after recognition before they are automatically deleted. Enter a whole number of days greater than zero; non-integer values are rejected. Conversation transcripts, review scores, feedback, and playlist audio are kept independently of this setting and are not affected by it.

In cloud (multi-tenant) deployments, if you raise the value above 365 days a warning appears under the field reminding you that longer retention can lead to additional usage-based costs.

This field is visible only to users with the system-settings management permission. Users without that permission do not see the field or the warning.

Cost tracking

  • Agent hourly rate — Average Org-wide (Default) — a default hourly cost used in cost-aware analytics when a per-agent rate is not configured. Includes a currency selector (USD, EUR, UAH, PLN, GBP, CAD, CHF, CNY, JPY, KRW, MXN, NZD, SEK, SGD, TRY, ZAR).

Authentication and disputes

  • Authentication: auto-create Ender Turing users on first OIDC login — shown only when OIDC is configured and the user has system-settings management permission. When enabled, federated identity provider users (for example, Entra ID) receive an Ender Turing account on their first successful sign-in. Existing accounts are linked by verified email, and new users receive the Agent role. Save this value with the page's Save Changes action.

  • Dispute limit per agent — shown only when Scoring — Appeals is turned on in the Features tab. The maximum number of disputes a single agent can open in the selected period. Set to -1 for unlimited disputes.

    • The period selector (Month, Week, or Day) sets the calendar period the limit is measured against. The quota resets on calendar boundaries — the start of each month, the start of each Monday-based week, or the start of each day — rather than on a rolling 30/7/1-day window.

Agent visibility

  • Agents can see only own team tags in conversations — restrict the tags an agent sees in transcripts to those of their team.

  • Allow agents to see automated scoring and feedback — when enabled, agents can see automated scoring results and the feedback attached to them.

Dashboards

  • Allow selecting multiple teams on dashboards — let users pick multiple teams at once on dashboards.

Scorecards

  • Allow reviewers to choose a scorecard during conversation review — let reviewers choose which scorecard to apply while reviewing a conversation.

  • Assign default scorecards based on conversation filters — assign the default scorecard automatically from conversation filters.

  • Maximum allowed score per scorecard point — the maximum value that a single scorecard point can take. Used when validating scoring forms.

Settings that moved

Some controls that used to be on this card now live elsewhere:

  • Disputes, preview (beta) features, and audio waveform generation are turned on or off in the Features tab, next to Settings. Only users with permission to manage system settings see that tab.

  • The percentile filter for agent scoring is turned on from the Agent Scoring header on the Dashboard (Configure Table → Show percentile filter).

Agent filter

  • Show deactivated agents for last N days in Agent Filter — how long deactivated agents continue to appear in the agent filter after deactivation. Defaults to 60 days.

SMTP Settings

The SMTP Settings card controls the outgoing email server used for system messages such as user invitations, password resets, and email reports.

  • Use default SMTP server — when enabled, Ender Turing's built-in SMTP server is used and the custom-server fields are hidden. Turn this off to point the platform at your own SMTP server.

When Use default SMTP server is turned off, the following fields become available:

  • Host — the SMTP host name.

  • Port — the SMTP port (numeric).

  • Use TLS — enable to require TLS when connecting to the SMTP server. When Use TLS is on, Login must also be filled in: outgoing email is treated as not configured when TLS is enabled without an SMTP username, even if the form saves successfully.

  • Login — the SMTP username. Required when Use TLS is enabled.

  • Password — the SMTP password. When a password is already saved, this field shows a masked placeholder rather than the stored value, so the eye icon cannot reveal the real secret. The eye icon only toggles whether the text you have typed into the field is shown as plain text, which is useful when entering a new password. To rotate the password, type the new value over the masked placeholder before saving.

  • From Email — the address used in the From header of outgoing messages. Required when a custom server is configured and validated as an email address. Use an address on your organization's own domain: addresses on enderturing.com or any of its subdomains are rejected for a custom server, because your server cannot authenticate mail for Ender Turing's domain and recipients' mail systems may mark such messages as spam or reject them. When you turn off Use default SMTP server, the field is not pre-filled with an Ender Turing address, so enter your own. The default SMTP server always sends from Ender Turing's own address, so this field applies only to a custom server.

    • If a custom server was saved earlier with an Ender Turing address, a warning at the top of the card shows that address. Email keeps going out from it until you change it, but the custom server settings cannot be saved again until From Email is an address on your own domain.

The From Name field is always shown and is used in the From header alongside the sender address. It is required.

Click Save changes at the bottom of the SMTP card to apply.

Important Notes

  • Changes you save in the General Settings card are saved separately from changes in the SMTP Settings card. Each card has its own Save changes button.

  • Most settings take effect immediately for new activity and are not applied retroactively — for example, changing Convert spoken numbers in transcripts does not rewrite existing transcripts. Audio retention is the exception: see the next note.

  • Lowering the audio retention is destructive for already-stored audio. The scheduled cleanup reads the current Max days to store recognized audio files value each time it runs and deletes every non-playlist audio file older than that value. If you reduce the retention from 365 days to 30 days, audio recorded more than 30 days ago can be removed on the next normal cleanup. Conversation transcripts, review scores, feedback, and playlist audio are kept independently and are not affected. Confirm with stakeholders before lowering this value, especially in cloud (multi-tenant) deployments.

  • The audio retention field accepts whole days only. Fractional values such as 1.9 are rejected; values such as 365 and 365.0 are accepted.

  • The audio retention warning above 365 days only appears in cloud (multi-tenant) deployments. It is informational — it does not block saving.

  • In cloud (multi-tenant) deployments, fields that are read-only for your role still show the current value so you can confirm how the workspace is configured before asking for a change.

Did this answer your question?