Skip to main content
The Account Settings section of the Telzino Dashboard lets you manage your organization’s identity, team access, security policies, email integration, API credentials, NetSapiens user base claims, and custom domains.

General

The General Settings page controls your organization’s basic identity. Display Name — The name shown throughout the dashboard and in any customer-facing contexts. You can update this at any time. Slug — A URL-safe identifier for your organization, assigned when the account is created. The slug cannot be changed after creation. Embed Capability — A toggle that controls whether the embed functionality (Inline Bar, Playground, and Popup Widget) is available for agents in this account. When disabled, embed options will not be accessible in agent settings.

Members

The Members page lets you manage who has access to your organization in the Telzino Dashboard.

Current Members

A table listing all active members of the organization. Each row displays:
  • User — The member’s email address and avatar
  • Auth Method — How the member authenticates (e.g., Email, SSO)
  • Role — A dropdown to assign the member’s role (e.g., Telzino Admin, Telzino Member)
  • Actions — A three-dot menu for additional actions such as removing a member
The currently logged-in user is indicated with a “You” badge.

Pending Invitations

A table showing invitations that have been sent but not yet accepted. Columns include Email, Role, and Invited By.

Invite Team Members

To add a new member, enter their email address, select a role from the dropdown (defaults to Telzino Member), and click Send. The invitee will receive an email with instructions to join the organization.

Security

The Security Policies page manages multi-factor authentication (MFA) settings for your organization.

Multi-Factor Authentication (MFA)

Enforce Multi-Factor Authentication — A toggle that, when enabled, requires all users in the organization to verify their identity with a second factor at login. MFA Domain Exclusions — A comma-separated list of email domains that are exempt from the MFA requirement. This is useful when certain domains already enforce their own authentication policies (e.g., domains using SSO through an identity provider). MFA Providers — Select which second-factor methods your users can use:
  • One-time Password — OTP codes generated by apps like Google Authenticator or Authy
  • Security Keys — WebAuthn-compliant hardware security keys (such as FIDO2 devices like YubiKeys)
Click Save to apply changes to the MFA configuration.

Email Settings

The Email Settings page lets you configure a custom SendGrid SMTP integration for sending emails from the platform. This is used for outbound emails such as notifications, invitations, and agent-triggered messages.

SendGrid Configuration

All fields are required:
  • SendGrid API Key — Your SendGrid API key for authenticating SMTP requests
  • From Email — The sender email address that will appear on outbound emails (e.g., [email protected])
  • From Name — The display name shown alongside the sender email address (e.g., your company name)
Click Verify Configuration to send a test email to your own address before saving. You can save without verifying, but verification is recommended to confirm your settings are correct.
Click Save Configuration to store the SendGrid settings.

API Keys

The API Keys page lets you create and manage API keys for machine-to-machine access to the Telzino API.

Create API Key

Enter a descriptive name for the key (e.g., “My Reporting Tool”), choose its Access — the whole account, or a single reseller or organization — and click Create API Key. The full API key will be displayed once after creation — copy it immediately, as it cannot be retrieved again. A key limited to one reseller or organization can only read and change that reseller’s or organization’s data, and cannot call account-level endpoints such as the billing report. See Scoped API keys.

Existing API Keys

A table listing all API keys for the organization, with columns for:
  • Name — The descriptive label you assigned to the key
  • Client ID — The public identifier for the key
  • Access — Whole account, or the reseller or organization the key is limited to
  • Created At — The date the key was created
  • Actions — Rotate replaces the key’s secret while keeping its Client ID; Delete permanently revokes the key
Reseller admins have their own API Keys page listing the keys their partner issued for them, where they can rotate a key.

Retry Policies

The Retry Policies page holds the account’s rulebooks for redialling outbound calls that were not answered. Each policy sets, per outcome (no answer, busy, voicemail, failed), how long to wait, how many attempts to make and whether the wait stays the same or doubles each time; optional contact limits cap calls per number per day and per week and set a minimum gap between attempts; and When attempts run out chooses whether to stop quietly, call a webhook or send an email. Assign a policy to an outbound agent as its Default retry policy, or pass its ID when triggering a call through the API. See Retry Policies.

Suppression List

Shown once an organization under the account has an outbound agent. The Outbound Suppression List is an organization-level do-not-call list: pick the organization, add a number with a reason and optional notes, or remove one. Every outbound call is checked against the list before it is placed and refused if the number is on it. See Outbound Compliance.

User Base Claims

The User Base Claims page links your Telzino organization to specific NetSapiens User Bases. This association allows the Connect App to identify which Telzino account an end user belongs to when they access the app through the NetSapiens User Portal. To get started, click Create User Base Claim and enter the NetSapiens User Base identifier. Once claimed, the user base will appear in a table on this page where you can manage or remove the association.

Custom Domains

The Custom Domains page lets you serve the Telzino Connect integration from your own branded URL instead of the default Telzino domain. This requires DNS configuration on your end. For example, instead of the default URL, your customers could access the Connect App at connect.yourdomain.com.

Adding a Custom Domain

Click + Add Domain and enter the domain you want to use. Telzino will provision an SSL certificate and a CloudFront distribution for the domain. You will need to create the appropriate DNS records (typically a CNAME) pointing your domain to the provided CloudFront distribution.

Domain Status

Each domain in the table shows:
  • Domain — The custom domain name
  • Certificate — The SSL certificate status (Pending Validation, then Issued)
  • CloudFront — The CDN distribution status (Pending, then Active). Once the domain is active, the dialog shows the Extra JS URL to paste into the UCaaS portal
  • Created — The date the domain was added
  • Actions — Options to refresh status, view DNS configuration details, or delete the domain