Partner Configuration Guide

Set up your customers the way they work

The reseller admin guide for Intelligence Cloud. What you configure, what we need from you, the setup steps in order, what each product does, and worked examples your sales, solutions and support teams can copy.

Reseller Admin GuideUpdated November 2026
Chapter 01

What a reseller admin can do

Everyone

As a reseller admin you build and run your customers' accounts: the companies, their locations, who signs in, which alerts go to whom, and how everything looks under your brand.

The hierarchy

ResellerYouYour admins, your branding, your domain and email sender. Every customer you sell to sits under you.
CompanyEach customerIts products, its users, its sign-in settings (including single sign-on) and optional branding of its own.
LocationEach team, department or siteIts phone-system connector and lines, its user groups, its First Alert rules and its Insights Hub setup.
ItemLives atWhat it does
UsersCompany, assigned to one or more locationsThe people who sign in and read calls. Each user sees calls for their own lines, or for all lines at their locations.
GroupsLocationNamed sets of users. Alert groups decide who receives which alert. The Insights Hub Access group decides who opens that location's Insights Hub.
ConnectorsLocationThe link to the customer's account on its phone platform, and the lines (extensions and numbers) that location captures. An extension belongs to exactly one location.
Alert rulesLocationFirst Alert conditions: words or phrases, sentiment, conversation topic, or a combination. Each rule names the groups that receive it.
ProductsCompany, location and userAfter Call Co-Pilot, First Alert Co-Pilot and Insights Hub. A product is switched on for the company, then for the location, then for each user who gets it. All three levels must be on.
BrandingReseller, with company overridesDisplay name, colours, logos, legal and support links. A company's own values win where set; yours apply everywhere else.

Admins configure. Users read calls.

An admin account manages configuration and does not open conversations. Anyone who needs to read calls, receive alerts or open Insights Hub is set up as a user, on the locations and lines they cover. That includes managers and executives, and it includes your own staff when they look at your own company's calls.

RoleWhereWhat they do
Reseller adminYour reseller accountCreates and changes companies, locations, connectors, groups, rules, users, branding and single sign-on.
Reseller supportYour reseller accountSees the same configuration, read only. For your support desk.
Company adminOne customerManages that company's users and settings. The customer's primary contact becomes its first company admin.
UserOne customer, on one or more locationsReads calls, receives alerts and opens Insights Hub, as their products, lines and groups allow. Managers and frontline staff are both users.
Chapter 01 · continued

Three ways to manage configuration

AdminsSolutions engineeringDevelopers

Every setting in this guide, except your SMTP relay, can be made in the Admin UI. The admin skill and the API do the same work faster when you run it at volume or from your own systems. Mix them freely: they all change the same configuration.

Admin UI
Intelligence Cloud, signed in as a reseller admin

Point-and-click screens for every object: companies, locations, connectors, groups, alert rules, users, branding, custom domains and single sign-on.

Use this when you are setting up one customer, making a one-off change, or checking what is configured.
Admin skill · beta
The Intelligence Cloud admin skill for Claude Code

Your solutions engineer describes the change in plain language. The skill reads the customer's setup sheet, picks the configuration pattern, shows a plan with every change listed, applies it only after you approve, verifies it, and gives you a one-step revert.

The skill runs in your own Claude Code account. What it reads, the customer's setup sheet and configuration, is processed under your own agreement for that tool.

Use this when you are onboarding a customer with many locations, users or alert rules, or rolling a standard alert set across sites. Ask your Tresic contact to join the partner beta.
API
The Intelligence Cloud REST API

Create and manage companies, locations, groups, rules and users from your own portal or billing system, and read conversations, alerts and Insights Hub data for the users your integration signs in as.

Use this when customers buy through your own systems, such as Base Intelligence Seat sign-ups, or you want call data in your own tools. See the API and Integration Guide and the API reference, and Integration Recipes for ready-to-run examples.
API credentials

Today an integration signs in with the username and password of a dedicated integration user, with the second factor at sign-in switched off for that user's company. API keys are being released in December 2026. The API and Integration Guide covers both.

Chapter 02

Getting started: information we need from you

ExecutiveMarketingITSolutions engineering

Send us these before we build your reseller account. Most of it is a sentence or a file; the access choices take a short conversation with your IT team.

Your admins and contacts

We needNotes
Each admin: name and work emailWe invite each one as a reseller admin. Tell us who should be read-only (reseller support) instead.
Primary contact: name, email and phoneOne contact phone number for your reseller account.
Billing contact: emailWhere account and billing correspondence goes.
Your phone platform: which platform carries your customers' calls, and its API addressFor NetSapiens, the API base URL, for example https://<your-host>/ns-api/v2. It is the same for every domain on the platform.

Branding

We needFormat
Display nameYour product name as your customers see it, or Intelligence Cloud as-is. Up to 200 characters.
Primary accent colour#RRGGBB, for example #1F4C82
Secondary accent colour#RRGGBB
Main logoImage file
FaviconImage file, square
Email logoImage file, shown in the header of every email
Login backgroundImage file

Legal and support

We needFormat
Support emailThe address your customers write to
Support portal URLhttps:// address
Copyright textUp to 500 characters, for example © 2026 Example Communications, Inc.
Privacy policy URLhttps:// address
Terms of service URLhttps:// address

Access and configuration choices

ChoiceOptionsWhat we need
Your product address1. app.intelligence.cloud as-is
2. A subdomain on ours, such as yourbrand.intelligence.cloud
3. A subdomain on your own domain, such as intelligence.example.com
Option 2: the label you want. Option 3: the hostname, then one DNS record from you (step 3).
Email delivery1. Our default sender
2. Your own SMTP server
Option 2: the six SMTP settings in step 4. The password travels by secure transfer.
Single sign-onPer customer: company login through any OpenID Connect provider, or email and passwordFor each customer who wants it: their login provider, their IT administrator's name and email, and the email domains their staff use.
Call details in emailsOn: summaries and alert details travel in the email.
Off: the email links to the call behind sign-in.
Your choice for each customer. It is set per customer, so tell us, or set it, as you add each one. For healthcare customers, choose Off.
Recording noticeThe customer's recorded greeting or noticeIt covers recording, transcription and analysis of calls. The customer is responsible for it, and for any consent the law requires where the caller and the business are.

Your internal teams and users

Your own company is your first customer, so your teams use the product before they sell or support it. We configure them when we create your account.

We needWhy
Your teams, for example Support, Billing, Sales, Onboarding, Management, and the extensions on eachEach team becomes a location, so alerts and reports go to the right lead. Managers' own lines go in Management.
Your people: name, work email, team, and whether they lead itFrontline staff get After Call Co-Pilot on their own lines. Leads and executives also get First Alert Co-Pilot and Insights Hub for the teams they run.
Who receives which alert at each teamFills the alert groups: customer threats, upset customers, departing customers, billing disputes, competitor mentions.
Your own account on the phone platformThe account we connect in step 5: for NetSapiens, your domain.
Sending keys and secrets

API keys, SMTP passwords and single sign-on client secrets go to security@tresic.cloud by secure transfer: a password manager share, a one-time secret link, or encrypted email. Never in a chat message, a ticket, a spreadsheet or a setup sheet. Tell us before you rotate a key rather than after.

Chapter 03

Configuration steps

AdminsITSolutions engineering

Five steps take you from a signed agreement to your own teams reading their calls. Steps 1 to 4 are done once. Step 5 is the pattern you repeat for every customer you add.

You your team   Tresic our team   Customer IT the customer's IT administrator  ·  UI Admin UI   Skill admin skill   API API

1
Your reseller account

We create it with your admins and branding.

2
Firewall

Open the path between your phone platform and us.

3
Your domain

Optional. Your product on your address.

4
Email delivery

Optional. Mail from your own server.

5
Your first customer

Your own company, set up the way you will set up every customer.

Step 1 · We configure you as a reseller

We create your reseller account from chapter 02, apply your branding, and invite your admins. Each admin gets an email, sets a password and signs in.

  • From then on you can change branding yourself on the White-labeling page UI. Display name, colours and links can also be set through the API API; logos and images are set in the Admin UI, or by your Tresic contact.
  • A customer can carry its own display name, colours, logos and legal links. Its values override yours for that customer only.
  • You can require a second factor at sign-in for any customer, or for all of them at once.

Step 2 · Open firewall connectivity to your phone platform

Done once per phone platform. Every customer on the platform uses it after that. The same three rules apply whichever platform carries the calls.

#ChangeOwner
aAllow our two addresses to reach your platform's API and recording servers, if you restrict access or API keys by IP.
20.150.140.37 connection test, and creating and renewing the call-record subscription
20.125.140.248 reading call records, recordings, user and voicemail details
Include a separate recording server or a load balancer in front of the API.
You
bAllow your platform to send to us. It posts call records to Intelligence Cloud over HTTPS on port 443; for NetSapiens, to https://app.intelligence.cloud/cdrs. If you filter outbound traffic, allow the hostname. It has no fixed IP and answers on IPv4 and IPv6, so use a hostname rule, not an IP rule.You
cSend us the public IPv4 and IPv6 addresses your platform sends call records from, every node in a cluster or failover pair. We add them to our allowlist. Tell us before they change.You send
Tresic adds
Set the allowlist before the connector goes live

We accept call records only from addresses on our allowlist. A record that is refused is not re-sent by your platform, so finish 2c before you connect the first customer in step 5.

Step 3 · Configure your domain

Your customers can reach the product on any of three addresses. You can change later without interrupting calls.

OptionYou doWe do
1. app.intelligence.cloudNothingNothing. Ready from step 1.
2. A subdomain on ours
yourbrand.intelligence.cloud
Send us the labelCreate the address and its certificate
3. A subdomain on your domain
intelligence.example.com
Add the DNS records below and send us the hostnameAdd the hostname, issue the certificate, confirm sign-in works

Option 3: DNS records

RecordNameValueWhen
CNAMEintelligence.example.comapp.intelligence.cloudRequired. DNS only (not proxied), TTL 300. Use a subdomain, not the apex of your domain.
CNAME_acme-challenge.intelligence.example.comThe value we send youOptional. Lets the certificate issue before the first CNAME switches over, and keeps renewals hands-off. Without it, the certificate issues once the first CNAME points at us.
CAAexample.com0 issue "ssl.com"
0 issue "letsencrypt.org"
0 issue "pki.goog"
Only if your domain already publishes CAA records.
  1. Add the records and tell us the hostname. Keep the CNAME in place: the certificate renews automatically for as long as it points at us.
  2. We add the hostname and the certificate issues, usually within minutes. If the records are not in place within seven days, ask us to restart validation.
  3. Test sign-in and an invitation on the new address before you add users. Sign in as an admin, then invite a test user and accept the invitation from the email.
  4. Set the address as the one used in email links, on White-labeling › Custom Domains UI, or ask your Tresic contact. Invitations, password resets and digests then link to your address instead of app.intelligence.cloud.

The address serves HTTPS only, with TLS 1.2 or later, and redirects plain HTTP. Single sign-on keeps working on every option with no extra setup.

Use a hostname that serves nothing else. Remove the CNAME when you stop using the address.

Step 4 · Configure email delivery

Invitations, password resets, call summaries, alerts and digests need a sender. Settings apply to every customer under your reseller account.

OptionWhat the recipient seesWhat we need
Our default senderFrom Tresic <noreply@mail.intelligence.cloud>. Your display name, logo and colours appear in the message itself.Nothing beyond your branding.
Your SMTP serverFrom your sender name and address, delivered through your mail service.The six settings below.
SettingNotes
smtp_hostYour relay's hostname, for example smtp.example.com
smtp_portUse 587 (STARTTLS) or 465 (TLS). On any other port your password and message content can travel unencrypted.
smtp_usernameThe relay account
smtp_passwordBy secure transfer. Stored encrypted and never shown again.
sender_nameThe name in the From line, up to 200 characters
sender_emailThe From address, for example noreply@example.com
  • Who sets it: you, through the API API, or your Tresic contact. Saving runs a live connection and sign-in test and refuses settings that fail.
  • Deliverability is yours: publish SPF, DKIM and DMARC for the sender domain so your relay is authorised to send as sender_email.
  • Confirm with a real send. The save test proves we can sign in to your relay. Send yourself an invitation to prove the relay accepts the sender address.
  • Fallback: a temporary failure is retried three times with increasing delay. If your server still refuses, or rejects the message outright, the email goes out from our default sender so it is never lost.
  • Sign-in codes for password users are always sent by our sign-in service, not through your server.

Step 5 · Configure your own company as the first customer

Your business goes live before any customer's. Your support, onboarding and sales teams read their own calls and alerts for a few weeks, and that experience is what makes the first customer launch go well. Every customer after that follows the same sequence.

#StepWhoHow
5.1Create the company. Company name, primary contact name, email and phone, and the products the company has. The primary contact is invited automatically as the company's first admin. A contact email can belong to only one account on the platform.Tresic for yours
You for customers
UI Skill API
5.2Single sign-on, if the customer wants it. See the SSO steps below.You Customer ITUI API
5.3Configure your teams as locations. One location per team, plus a Management location for managers' own lines, with no alert rules. Name them <Company> - <Team>. Each location needs an address and an industry. Switch on the products the location uses. Start every location with an empty rule list. See Choosing a pattern. A Base Intelligence Seat customer is a single location, with no Management location: managers' own lines are not captured.You TresicUI Skill API
5.4Create the platform credential. The connector signs in to the customer's account on its phone platform with a credential you create there. For NetSapiens it is an API key for the customer's domain: see the NetSapiens connector. Send it by secure transfer.You or your platform providerYour phone platform
5.5Configure the connector at each location. Choose the platform, enter its connection values, run the connection test and save, then choose the extensions that location captures. Each location gets its own connector and its own extensions. See Connectors.You TresicUI API
5.6Configure user groups at each location: one per alert role (for example Customer Threats, Upset Customers, Billing Disputes) and one Insights Hub Access group. Put the people who act on an alert in its group, not the people who took the call.YouUI Skill API
5.7Configure First Alert for each location. Choose the lines it watches, then build the rules: a name, a priority (critical, high, medium or low), one or more triggers (words or phrases, a sentiment threshold, a conversation topic), any or all logic, and the groups that receive it. Create rules switched off and switch them on last. Optionally add an HTTPS webhook address for the location's alerts and send a test. Management locations get no rules.YouUI Skill API
5.8Configure Insights Hub for each location. Give the Insights Hub Access group access, choose the lines it covers, or switch on monitor all numbers so Insights Hub users see every call at the location.YouUI API
5.9Create a getting-started guide for the customer: how to sign in, set notifications and time zone, then what managers and frontline staff do first. Your Tresic contact can send you the service-provider guide to start from.YouYour own document
5.10Configure managers. Users on every location they run, plus Management for their own line. All three products. Lines: all lines at their locations. Groups: the alert groups they act on and Insights Hub Access. Alert email on, and a daily or weekly digest if they want one.YouUI Skill API
5.11Train managers. Opening an alert and reading the evidence behind it, playing the recording, calling the customer back, tuning their own alert email and digest, reading Insights Hub topics and using Instant Insights.YouGetting-started guide
5.12Configure end users. Users on their own location. After Call Co-Pilot. Lines: their own extension. Alert email off. End-of-day recap at their local time if they want it.YouUI Skill API
5.13Train end users. Reading the summary after each call, working their follow-up tasks, searching past calls before calling a customer back, and copying a call into the ticketing system or CRM.YouGetting-started guide

Invite users once their lines are mapped. Each user gets an email, sets a password (or signs in with single sign-on) and lands in the product. Invitations last seven days and can be re-sent.

Connectors (5.4 and 5.5)

A connector links a location to the phone platform that carries its calls. Each platform has its own credential and connection values; everything else works the same way on every platform. Intelligence Cloud connects to NetSapiens today.

  • Watch the status after saving. The connector shows Connecting while it registers with the platform, then Active. The connection test proves the credential reaches the customer's account; the permission check runs after saving. If the status turns to an error about permissions, fix the credential's settings on the platform, update the connector and restart it.
  • Confirm calls are flowing. Place a call of a minute or more on a recorded, captured extension and hang up. Within a few minutes it appears in After Call Co-Pilot for the users on that location, with its summary, transcript and recording. A connected status means the credential reaches the platform; the first call is the signal the customer is live.
  • Recording must be on for every line that carries a product. A line that is not recorded has nothing to read.
  • Map people's phone lines, and leave out system entries such as auto attendants and trunks.
  • An extension belongs to exactly one location. Before you add one to a location, check that no other location captures it. Mapping a user to an extension another location already captures is refused with a conflict: the extension is already captured at another location. Release it there first.
  • Stopping a connector: deactivate it. Connectors are not deleted.
  • Rotating a credential: tell us first. Create the new credential with the same settings, update it on every connector that uses it, run the connection test, then retire the old one.
  • When the customer leaves: deactivate the connectors, then revoke the credential on the platform.

The NetSapiens connector

Connection values. The same three values on every location's connector for the domain. Find the extensions to capture in your NetSapiens portal.

ValueExampleNotes
API base URLhttps://<your-host>/ns-api/v2HTTPS, ending in /ns-api/v2. The same for every domain on the platform.
Domainyourcompany.exampleExactly as it appears in NetSapiens.
API keyEntered on the connector and never shown again.

The API key. Use one domain-level key per customer domain. A reseller-level key reaches every domain on your platform, so use one only where your platform can't issue domain-level keys.

SettingValue
ScopeDomain level on the customer's domain. Use Reseller level with the domain set only where your platform can't do otherwise: a reseller-level key reaches every domain under that reseller. User-, site- and call-centre-level keys are refused.
Read-onlyNo. We create, renew and remove our call-record subscription with this key.
Allowed modelscdrs, domains, recordings, subscriptions, users, voicemails. Grant only these. Use * only where your platform can't list models.
IP restriction20.150.140.37 and 20.125.140.248. Use * only where your platform can't restrict by IP.
WithoutWhat breaks
domainsThe connection test fails, so the connector cannot be saved.
subscriptionsNo call-record subscription, so no calls arrive.
cdrsCall records cannot be read, so no conversation is created.
recordingsNo audio, so no transcript or summary.
usersParticipant names are missing from calls.
voicemailsCaller voicemails are not picked up.
Read-only set to YesThe subscription cannot be created, renewed or removed.

Single sign-on (5.2)

Staff sign in with the company login they already use, through any OpenID Connect provider. It is set up per customer, by you or by Tresic; the customer's IT administrator makes two changes on their side. Users are still invited by name: single sign-on decides how people sign in, not whether they can.

#StepOwner
1Claim the customer's email domain on the company's Single Sign-On screen. It shows one TXT record: name _ic-verify.<domain>, with the value on screen. Send it to the customer's IT administrator. Several domains can be claimed. Never remove and re-add a claim: that issues a new value.You
2Publish the TXT record, then run the check. It usually passes within minutes and can take up to three days.Customer IT publishes
You check
3Register the application in the identity provider with the reply URL https://app.intelligence.cloud/api/v1/auth/sso/idp/callback. Make it a single-tenant application whose issuer is the customer's own, never a shared multi-tenant issuer, and require user assignment so only assigned staff can sign in. Get written confirmation it is saved.Customer IT
4Send the connection details: the issuer, the OpenID configuration URL (ending /.well-known/openid-configuration), the client ID, and the client secret only if their application uses one. A secret travels by secure transfer. Note the secret's or certificate's expiry date and send a new one before it expires.Customer IT
5Connect the provider on the company's Single Sign-On screen and run the test.You
6Invite users with the sign-in method set to single sign-on, and test one sign-in together. After signing in at their provider, the user lands on the address the customer's identity provider is configured to send them to: your product address.You Customer IT
  • One identity provider per company. OpenID Connect only.
  • For Microsoft Entra ID: register the reply URL under Web when the app uses a client secret, or under Mobile and desktop applications when it does not. It cannot sit under both.
  • Single sign-on is set up by reseller admins or Tresic. Customer admins do not see or change the setup.
  • When a customer leaves, disconnect the provider and remove the domain claims.

When people and lines change

  • Moving an extension: remove it from the old owner's lines, add it to the new owner's, then update every manager whose lines include it, and the First Alert and Insights Hub lines at the location. Calls already captured stay with the old owner.
  • Someone leaves: remove their groups and lines and take their extension out of every manager's lines, First Alert and Insights Hub, then deactivate the user. Deactivation alone keeps groups and lines.
  • Someone is promoted: add the locations they now run, all lines at those locations, Insights Hub, First Alert and their alert groups.
Chapter 04

Products and capabilities

SalesSolutions engineeringSupport

Three products read the same calls, and every conversation on a captured line is processed. The Base Intelligence Seat packages them for one location and two user types. The full products remove those limits.

Package
Base Intelligence Seat

Built for a business that wants the essentials on top of its phone service. One location, two alerts, a basic Insights Hub, and API access. Each seat is one of two user types.

A business with several sites can choose the Seat too. It is set up as one location, so everyone is treated as one team, with no view by site.

End user
  • After Call Co-Pilot on their own line
  • A summary, key points, follow-up tasks, transcript and recording for every call
  • Search and replay of their own past calls
  • Optional end-of-day recap
Manager
  • After Call Co-Pilot on every end user's line
  • First Alert Co-Pilot with two alerts: Upset Customer and Customer Threat
  • Insights Hub basic dashboard and Instant Insights for the location
Included
  • One location
  • API access
  • Your branding, domain and email sender

The two Seat alerts

AlertPriorityFires whenGoes to
Upset CustomerHighThe call's sentiment is below −40.Manager Alerts group
Customer ThreatCriticalThe caller uses a customer-threat phrase (threats to leave, threats of legal or regulatory action, threats of a public complaint) and the call's sentiment is below −20.Manager Alerts group

Your Tresic contact supplies the standard customer-threat phrase list, and the admin skill applies it for you.

Full product
After Call Co-Pilot

"What happened on that call?" A written record of every conversation, without anyone starting it.

After every call
  • A factual summary: who, why, what, and how it ended
  • Key points, sentiment and topics
  • Follow-up commitments captured as tasks
  • Summary by email for users who opt in
Working the calls
  • Tasks assigned to a teammate, with status and due date
  • Search by name, number, summary or anything said on the call
  • Recording playback and transcript in the app
  • One-click copy of the call into a CRM or ticket
  • End-of-day recap at each user's local time
Integration
  • One HTTPS webhook per location, posting each call's summary as it completes
  • A test delivery from the admin screen
  • Full conversation record through the API
Full product
First Alert Co-Pilot

"Which customer needs a call back today?" An alert within minutes of the call that needs one, routed to the person who can act.

Rules
  • As many rules per location as the business needs
  • Triggers: words or phrases, sentiment threshold, conversation topic
  • Any or all logic to cut false alarms
  • Four priority levels
  • Duplicate a rule, edit it, switch it on when it is right
Routing and delivery
  • Groups per location carry each rule's alerts
  • Each alert links the call, the matching excerpt and the recording
  • Email per person and per alert type
  • Daily and weekly digests in each person's time zone
  • Alert list with search and filters, and an alert dashboard
Integration
  • One HTTPS webhook per location for alerts, with a test button
  • Alerts readable through the API
Full product
Insights Hub

"What is this business spending its conversations on, and what changed?" The topic view of every conversation, with the calls behind every number.

Dashboard
  • Trending topics with movement against the previous period
  • Topic distribution across the period
  • Total, answered and unanswered conversations
  • Date presets and custom ranges
Drill-through and Instant Insights
  • Any topic opens the conversations inside it
  • Each conversation with its summary, sentiment, recording and transcript
  • Instant Insights: a catalogue of ready questions, each answer with the records behind it
Scope
  • Every location the person covers: one, several or all of them combined
  • Access through the Insights Hub Access group at each location
  • Data readable through the API
Insights Hub
Extended Insights Hub Reports

"Which customers are at risk, what are they unhappy about, and who would vouch for us?" Reports tuned to the customer's industry and built from the context of each call, not from keywords and sentiment alone. Each one is available for the whole company and for each location, and every finding links to the calls behind it.

Risk
  • Churn Watch: customers who signal they may leave, with what they said
  • Competitive Insights: competitors named on calls, and what customers said about them
Complaints
  • Complaints: Product: the top complaint drivers about what the business sells, with every call behind each one
  • Complaints: Service: the top complaint drivers about how customers were served, with every call behind each one
Advocacy
  • Referenceable Calls: calls where a customer praised the business or a person by name
  • Referenceable Customers: customers who would make good references, reviewers or case studies
  • Saved Calls: calls where an unhappy or departing customer was turned around

Seat vs full products

CapabilityBase Intelligence SeatFull products
LocationsOneAs many as the business needs: teams, departments, sites
After Call Co-PilotFull product. End users on their own line, managers on every end user's lineFull product, with any line visibility per user
First Alert rulesTwo: Upset Customer and Customer ThreatAny number per location, built for the business
Alert triggersSet for you: sentiment, and customer-threat phrases with sentimentWords or phrases, sentiment, conversation topic, combined with any or all
Alert groupsOne: Manager AlertsAs many as the business needs, per location
Alert email and digestsYes, for managersYes, per person and per alert type
Alert webhookAlerts through the APIOne HTTPS webhook per location, plus the API
Insights HubBasic dashboard and Instant Insights for the one locationEvery location the person covers, one, several or all combined
API accessIncludedIncluded
Your branding, domain and senderYesYes

Move a Seat customer to the full products when they want more than the two alerts, alerts routed to different people by kind, or a view by site, team or department.

Chapter 05

Example customer configurations

SalesSolutions engineeringSupport

Three customers, from a single office on the Base Intelligence Seat to a multi-site group with departments at every site. In every pattern teams and departments are locations and groups decide who gets which alert. In every full-product pattern, managers' own lines sit in a Management location. A Base Intelligence Seat customer is a single location, and managers' own lines are not captured.

A · Base Intelligence Seat: Northgate Dental

One dental office on your UCaaS service, with Tresic added to its seats. Two managers take the alerts and read Insights Hub; four front-office staff get their own call write-ups.

Northgate Dental 1 location: Northgate Dental - Main
Practice ownerManagerManager Alerts · Insights Hub Access
Office managerManagerManager Alerts · Insights Hub Access
Front desk (2)End user
Treatment coordinatorEnd user
Billing coordinatorEnd user
Person / roleLocationsGroupsProductsSees calls for
Practice owner (Manager)MainManager Alerts, Insights Hub AccessAfter Call, First Alert, Insights HubAll lines at Main
Office manager (Manager)MainManager Alerts, Insights Hub AccessAfter Call, First Alert, Insights HubAll lines at Main
Front desk (End user, ×2)MainNoneAfter CallOwn line
Treatment coordinator (End user)MainNoneAfter CallOwn line
Billing coordinator (End user)MainNoneAfter CallOwn line

Setup at a glance

  1. Company with After Call Co-Pilot, First Alert Co-Pilot and Insights Hub; one location, Northgate Dental - Main, with the same three products and the connector to the office's phone platform.
  2. Groups: Manager Alerts and Insights Hub Access.
  3. First Alert: Upset Customer and Customer Threat, both to Manager Alerts, watching every line at the location.
  4. Insights Hub: access for Insights Hub Access, monitor all numbers on.
  5. End users: After Call on, own extension, alert email off. Managers: all three products, every end user's line, both groups, alert email on. Managers' own lines are not captured.

The API and Integration Guide walks the Base Intelligence Seat lifecycle call by call.

B · Full products, several teams at one site: Harborview Communications

A managed service provider with one office and four teams that each own a kind of call. Pattern: one location per team, plus Management. Each team gets its own alerts, its own owners and its own Insights Hub view.

Harborview Communications 5 locations: Support · Billing · Sales · Onboarding · Management
VP Customer ExperienceExecutive · every locationCustomer Threats (all teams) · Departing Customers · Insights Hub Access (all teams)
Support leadHarborview - SupportCustomer Threats · Upset Customers · Low Sentiment Calls · Insights Hub Access
Billing leadHarborview - BillingCustomer Threats · Upset Customers · Billing Disputes · Insights Hub Access
Sales managerHarborview - SalesCustomer Threats · Upset Customers · Competitor Mentions (all teams) · Insights Hub Access
Onboarding leadHarborview - OnboardingCustomer Threats · Upset Customers · Insights Hub Access
Support agentsSupport
Billing specialistsBilling
Account executivesSales
Onboarding specialistsOnboarding

Groups at each team location

GroupWho is in itLocations
Customer ThreatsThe team lead and the VP Customer ExperienceEvery team
Upset CustomersThe team leadEvery team
Departing CustomersThe VP Customer ExperienceSupport and Billing
Competitor MentionsThe sales managerEvery team
Billing DisputesThe billing team leadBilling
Low Sentiment CallsThe support lead, as call-quality reviewerSupport
Insights Hub AccessThe team's managers and the executiveEvery team
Person / roleLocationsGroupsProductsSees calls for
VP Customer ExperienceSupport, Billing, Sales, Onboarding, ManagementCustomer Threats and Insights Hub Access at every team; Departing Customers at Support and BillingAll threeAll lines at their locations
Support leadSupport, ManagementCustomer Threats, Upset Customers, Low Sentiment Calls, Insights Hub Access at SupportAll threeAll Support lines, plus own line
Billing leadBilling, ManagementCustomer Threats, Upset Customers, Billing Disputes, Insights Hub Access at BillingAll threeAll Billing lines, plus own line
Sales managerSales, ManagementCustomer Threats, Upset Customers, Insights Hub Access at Sales; Competitor Mentions at every teamAll threeAll Sales lines, plus own line
Onboarding leadOnboarding, ManagementCustomer Threats, Upset Customers, Insights Hub Access at OnboardingAll threeAll Onboarding lines, plus own line
Agents and specialistsTheir teamNoneAfter CallOwn line

C · Full products, several sites with several departments: Riverbend Auto Group

A dealer group with two stores, each running Reception, Service, Sales and Finance, and a home office. Pattern: corporate - location - department. Alerts go to the department that took the call, and call access follows the org chart: head office sees everything, a general manager sees their store, a department manager sees their department, frontline staff see their own calls.

Riverbend Auto Group 10 locations: 2 stores × 4 departments · Home Office · Management
Dealer principal and CFOExecutives · every locationLegal Threats (every location) · Upset Customers at Home Office · Insights Hub Access (every location)
Northside store
General managerEvery Northside departmentLegal Threats · Customer Threats · Insights Hub Access
ReceptionReceptionists · end users
ServiceService manager + backup · Upset Customers (Service and Reception) · Service Follow-upService advisors · end users
SalesSales manager · Upset CustomersSalespeople · end users
FinanceFinance manager · Upset CustomersFinance staff · end users
Lakeshore store
General managerEvery Lakeshore departmentLegal Threats · Customer Threats · Insights Hub Access
ReceptionReceptionists · end users
ServiceService manager + backup · Upset Customers (Service and Reception) · Service Follow-upService advisors · end users
SalesSales manager · Upset CustomersSalespeople · end users
FinanceFinance manager · Upset CustomersFinance staff · end users

Locations

LocationWhat goes in itAlert rules
Riverbend - Northside - Reception
Riverbend - Lakeshore - Reception
Front desk, operator and main lines, call-park slotsYes
Riverbend - Northside - Service
Riverbend - Lakeshore - Service
Service advisors, parts, cashier linesYes
Riverbend - Northside - Sales
Riverbend - Lakeshore - Sales
Sales floor and internet sales linesYes
Riverbend - Northside - Finance
Riverbend - Lakeshore - Finance
Finance office linesYes
Riverbend - Home OfficeHead-office and back-office lines, including the company customer-support lineYes
Riverbend - ManagementManagers' and executives' own linesNone

Alert groups at every department location

GroupWho gets it
Legal ThreatsThe store's general manager and the executives, as they happen
Customer ThreatsThe store's general manager
Upset CustomersThe department manager. At Reception: the service manager. At Home Office: the executives.
Service Follow-upThe service manager and one named backup (customers saying nobody called back, or a long wait)
Insights Hub AccessThe managers at that location

Frontline staff are not in their own department's groups: the alert is about their call, and it goes to the manager who can help.

Who sees what, up and down the hierarchy

Person / roleLocationsGroupsProductsSees calls for
Dealer principal, CFO (executives)Every locationLegal Threats everywhere; Upset Customers at Home Office; Insights Hub Access everywhereAll threeAll lines at every location
Northside general managerAll four Northside departments, ManagementLegal Threats, Customer Threats, Insights Hub Access at each Northside departmentAll threeAll Northside lines, plus own line
Northside service managerNorthside Service and Reception, ManagementUpset Customers, Service Follow-up and Insights Hub Access at Service and ReceptionAll threeAll Northside Service and Reception lines, plus own line
Northside sales managerNorthside Sales, ManagementUpset Customers, Insights Hub Access at SalesAll threeAll Northside Sales lines, plus own line
Service advisorNorthside ServiceNoneAfter CallOwn line
ReceptionistNorthside ReceptionNoneAfter CallOwn line

Choosing a pattern

Agree the pattern with the customer at kickoff. It decides the locations, who gets which alert and who can see which calls, and changing it later means moving extensions between locations.

  1. How many physical locations (stores, offices, sites) take customer calls?
  2. Does each location run several departments (for example reception, service, sales, finance) with their own managers?
  3. Should an alert go to the manager of the department that took the call, rather than to one manager for the whole location?
  4. Should department managers see only their own department's calls, while location managers see their whole location and head office sees everything?
AnswersPattern
One location, one teamSingle location. The shape the Base Intelligence Seat is built for. Example A.
One location, several teams, each with its own alertsOne location per team, plus Management. Example B.
Several locations, each run as one team, or departments that can share one manager's alertsOne location per physical location, plus Management. Departments inside a site are separated by groups.
Several locations, several departments each, alerts and call access by departmentCorporate - location - department. The default for dealer groups and any multi-site business whose sites run several departments. Example C.
What every pattern shares

In every full-product pattern, a Management location holds managers' own lines and has no alert rules. A Base Intelligence Seat customer is a single location, and managers' own lines are not captured. Each location has its own connector and its own lines, and an extension belongs to exactly one location. Every location of the same kind gets the same alert and group names, so alerts and reports line up across the business. Builds of more than five locations go in two stages: one pilot location first, then the rest.

Chapter 06

Next steps and help

Everyone
You needGo to
Help with a configuration or a customersupport@tresic.cloud or your Tresic contact, with the company, location and what you expected to see. For a sign-in problem, include the person's email and the time they tried.
Keys, passwords and client secretssecurity@tresic.cloud, by secure transfer only: a password manager share, a one-time secret link, or encrypted email
A suspected security incident, or a key, password or secret that was exposedsecurity@tresic.cloud, straight away, copying your Tresic contact. Rotate what was exposed.
A vulnerability in Intelligence Cloud or the SDKssecurity@tresic.cloud, with the steps to reproduce it. See the vulnerability disclosure policy.
Security documentation: certifications, penetration test summary, data location, subprocessors, BAAsecurity@tresic.cloud
Joining the admin skill beta, a new domain, a pattern decisionYour Tresic partner contact
Every conversation, set up the way your customer works. © 2026 Creo Solutions, Inc. d/b/a Tresic · API and SDK Terms · Other names are trademarks of their respective owners.