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.
What a reseller admin can do
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
| Item | Lives at | What it does |
|---|---|---|
| Users | Company, assigned to one or more locations | The people who sign in and read calls. Each user sees calls for their own lines, or for all lines at their locations. |
| Groups | Location | Named sets of users. Alert groups decide who receives which alert. The Insights Hub Access group decides who opens that location's Insights Hub. |
| Connectors | Location | The 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 rules | Location | First Alert conditions: words or phrases, sentiment, conversation topic, or a combination. Each rule names the groups that receive it. |
| Products | Company, location and user | After 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. |
| Branding | Reseller, with company overrides | Display 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.
| Role | Where | What they do |
|---|---|---|
| Reseller admin | Your reseller account | Creates and changes companies, locations, connectors, groups, rules, users, branding and single sign-on. |
| Reseller support | Your reseller account | Sees the same configuration, read only. For your support desk. |
| Company admin | One customer | Manages that company's users and settings. The customer's primary contact becomes its first company admin. |
| User | One customer, on one or more locations | Reads calls, receives alerts and opens Insights Hub, as their products, lines and groups allow. Managers and frontline staff are both users. |
Three ways to manage configuration
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.
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.
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.
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.
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.
Getting started: information we need from you
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 need | Notes |
|---|---|
| Each admin: name and work email | We invite each one as a reseller admin. Tell us who should be read-only (reseller support) instead. |
| Primary contact: name, email and phone | One contact phone number for your reseller account. |
| Billing contact: email | Where account and billing correspondence goes. |
| Your phone platform: which platform carries your customers' calls, and its API address | For 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 need | Format |
|---|---|
| Display name | Your 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 logo | Image file |
| Favicon | Image file, square |
| Email logo | Image file, shown in the header of every email |
| Login background | Image file |
Legal and support
| We need | Format |
|---|---|
| Support email | The address your customers write to |
| Support portal URL | https:// address |
| Copyright text | Up to 500 characters, for example © 2026 Example Communications, Inc. |
| Privacy policy URL | https:// address |
| Terms of service URL | https:// address |
Access and configuration choices
| Choice | Options | What we need |
|---|---|---|
| Your product address | 1. app.intelligence.cloud as-is2. A subdomain on ours, such as yourbrand.intelligence.cloud3. 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 delivery | 1. 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-on | Per customer: company login through any OpenID Connect provider, or email and password | For 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 emails | On: 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 notice | The customer's recorded greeting or notice | It 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 need | Why |
|---|---|
| Your teams, for example Support, Billing, Sales, Onboarding, Management, and the extensions on each | Each 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 it | Frontline 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 team | Fills the alert groups: customer threats, upset customers, departing customers, billing disputes, competitor mentions. |
| Your own account on the phone platform | The account we connect in step 5: for NetSapiens, your domain. |
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.
Configuration steps
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
Your reseller account
We create it with your admins and branding.
Firewall
Open the path between your phone platform and us.
Your domain
Optional. Your product on your address.
Email delivery
Optional. Mail from your own server.
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.
| # | Change | Owner |
|---|---|---|
| a | Allow 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 subscription20.125.140.248 reading call records, recordings, user and voicemail detailsInclude a separate recording server or a load balancer in front of the API. | You |
| b | Allow 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 |
| c | Send 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 |
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.
| Option | You do | We do |
|---|---|---|
1. app.intelligence.cloud | Nothing | Nothing. Ready from step 1. |
2. A subdomain on oursyourbrand.intelligence.cloud | Send us the label | Create the address and its certificate |
3. A subdomain on your domainintelligence.example.com | Add the DNS records below and send us the hostname | Add the hostname, issue the certificate, confirm sign-in works |
Option 3: DNS records
| Record | Name | Value | When |
|---|---|---|---|
| CNAME | intelligence.example.com | app.intelligence.cloud | Required. DNS only (not proxied), TTL 300. Use a subdomain, not the apex of your domain. |
| CNAME | _acme-challenge.intelligence.example.com | The value we send you | Optional. 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. |
| CAA | example.com | 0 issue "ssl.com"0 issue "letsencrypt.org"0 issue "pki.goog" | Only if your domain already publishes CAA records. |
- 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.
- 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.
- 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.
- 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.
| Option | What the recipient sees | What we need |
|---|---|---|
| Our default sender | From Tresic <noreply@mail.intelligence.cloud>. Your display name, logo and colours appear in the message itself. | Nothing beyond your branding. |
| Your SMTP server | From your sender name and address, delivered through your mail service. | The six settings below. |
| Setting | Notes |
|---|---|
smtp_host | Your relay's hostname, for example smtp.example.com |
smtp_port | Use 587 (STARTTLS) or 465 (TLS). On any other port your password and message content can travel unencrypted. |
smtp_username | The relay account |
smtp_password | By secure transfer. Stored encrypted and never shown again. |
sender_name | The name in the From line, up to 200 characters |
sender_email | The 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.
| # | Step | Who | How |
|---|---|---|---|
| 5.1 | Create 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.2 | Single sign-on, if the customer wants it. See the SSO steps below. | You Customer IT | UI API |
| 5.3 | Configure 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 Tresic | UI Skill API |
| 5.4 | Create 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 provider | Your phone platform |
| 5.5 | Configure 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 Tresic | UI API |
| 5.6 | Configure 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. | You | UI Skill API |
| 5.7 | Configure 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. | You | UI Skill API |
| 5.8 | Configure 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. | You | UI API |
| 5.9 | Create 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. | You | Your own document |
| 5.10 | Configure 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. | You | UI Skill API |
| 5.11 | Train 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. | You | Getting-started guide |
| 5.12 | Configure 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. | You | UI Skill API |
| 5.13 | Train 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. | You | Getting-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.
| Value | Example | Notes |
|---|---|---|
| API base URL | https://<your-host>/ns-api/v2 | HTTPS, ending in /ns-api/v2. The same for every domain on the platform. |
| Domain | yourcompany.example | Exactly as it appears in NetSapiens. |
| API key | Entered 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.
| Setting | Value |
|---|---|
| Scope | Domain 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-only | No. We create, renew and remove our call-record subscription with this key. |
| Allowed models | cdrs, domains, recordings, subscriptions, users, voicemails. Grant only these. Use * only where your platform can't list models. |
| IP restriction | 20.150.140.37 and 20.125.140.248. Use * only where your platform can't restrict by IP. |
| Without | What breaks |
|---|---|
domains | The connection test fails, so the connector cannot be saved. |
subscriptions | No call-record subscription, so no calls arrive. |
cdrs | Call records cannot be read, so no conversation is created. |
recordings | No audio, so no transcript or summary. |
users | Participant names are missing from calls. |
voicemails | Caller voicemails are not picked up. |
| Read-only set to Yes | The 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.
| # | Step | Owner |
|---|---|---|
| 1 | Claim 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 |
| 2 | Publish the TXT record, then run the check. It usually passes within minutes and can take up to three days. | Customer IT publishes You check |
| 3 | Register 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 |
| 4 | Send 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 |
| 5 | Connect the provider on the company's Single Sign-On screen and run the test. | You |
| 6 | Invite 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.
Products and capabilities
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.
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.
- 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
- 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
- One location
- API access
- Your branding, domain and email sender
The two Seat alerts
| Alert | Priority | Fires when | Goes to |
|---|---|---|---|
| Upset Customer | High | The call's sentiment is below −40. | Manager Alerts group |
| Customer Threat | Critical | The 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.
"What happened on that call?" A written record of every conversation, without anyone starting it.
- 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
- 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
- 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
"Which customer needs a call back today?" An alert within minutes of the call that needs one, routed to the person who can act.
- 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
- 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
- One HTTPS webhook per location for alerts, with a test button
- Alerts readable through the API
"What is this business spending its conversations on, and what changed?" The topic view of every conversation, with the calls behind every number.
- Trending topics with movement against the previous period
- Topic distribution across the period
- Total, answered and unanswered conversations
- Date presets and custom ranges
- 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
- 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
"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.
- 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: 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
- 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
| Capability | Base Intelligence Seat | Full products |
|---|---|---|
| Locations | One | As many as the business needs: teams, departments, sites |
| After Call Co-Pilot | Full product. End users on their own line, managers on every end user's line | Full product, with any line visibility per user |
| First Alert rules | Two: Upset Customer and Customer Threat | Any number per location, built for the business |
| Alert triggers | Set for you: sentiment, and customer-threat phrases with sentiment | Words or phrases, sentiment, conversation topic, combined with any or all |
| Alert groups | One: Manager Alerts | As many as the business needs, per location |
| Alert email and digests | Yes, for managers | Yes, per person and per alert type |
| Alert webhook | Alerts through the API | One HTTPS webhook per location, plus the API |
| Insights Hub | Basic dashboard and Instant Insights for the one location | Every location the person covers, one, several or all combined |
| API access | Included | Included |
| Your branding, domain and sender | Yes | Yes |
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.
Example customer configurations
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.
| Person / role | Locations | Groups | Products | Sees calls for |
|---|---|---|---|---|
| Practice owner (Manager) | Main | Manager Alerts, Insights Hub Access | After Call, First Alert, Insights Hub | All lines at Main |
| Office manager (Manager) | Main | Manager Alerts, Insights Hub Access | After Call, First Alert, Insights Hub | All lines at Main |
| Front desk (End user, ×2) | Main | None | After Call | Own line |
| Treatment coordinator (End user) | Main | None | After Call | Own line |
| Billing coordinator (End user) | Main | None | After Call | Own line |
Setup at a glance
- 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.
- Groups: Manager Alerts and Insights Hub Access.
- First Alert: Upset Customer and Customer Threat, both to Manager Alerts, watching every line at the location.
- Insights Hub: access for Insights Hub Access, monitor all numbers on.
- 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.
Groups at each team location
| Group | Who is in it | Locations |
|---|---|---|
| Customer Threats | The team lead and the VP Customer Experience | Every team |
| Upset Customers | The team lead | Every team |
| Departing Customers | The VP Customer Experience | Support and Billing |
| Competitor Mentions | The sales manager | Every team |
| Billing Disputes | The billing team lead | Billing |
| Low Sentiment Calls | The support lead, as call-quality reviewer | Support |
| Insights Hub Access | The team's managers and the executive | Every team |
| Person / role | Locations | Groups | Products | Sees calls for |
|---|---|---|---|---|
| VP Customer Experience | Support, Billing, Sales, Onboarding, Management | Customer Threats and Insights Hub Access at every team; Departing Customers at Support and Billing | All three | All lines at their locations |
| Support lead | Support, Management | Customer Threats, Upset Customers, Low Sentiment Calls, Insights Hub Access at Support | All three | All Support lines, plus own line |
| Billing lead | Billing, Management | Customer Threats, Upset Customers, Billing Disputes, Insights Hub Access at Billing | All three | All Billing lines, plus own line |
| Sales manager | Sales, Management | Customer Threats, Upset Customers, Insights Hub Access at Sales; Competitor Mentions at every team | All three | All Sales lines, plus own line |
| Onboarding lead | Onboarding, Management | Customer Threats, Upset Customers, Insights Hub Access at Onboarding | All three | All Onboarding lines, plus own line |
| Agents and specialists | Their team | None | After Call | Own 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.
Locations
| Location | What goes in it | Alert rules |
|---|---|---|
Riverbend - Northside - ReceptionRiverbend - Lakeshore - Reception | Front desk, operator and main lines, call-park slots | Yes |
Riverbend - Northside - ServiceRiverbend - Lakeshore - Service | Service advisors, parts, cashier lines | Yes |
Riverbend - Northside - SalesRiverbend - Lakeshore - Sales | Sales floor and internet sales lines | Yes |
Riverbend - Northside - FinanceRiverbend - Lakeshore - Finance | Finance office lines | Yes |
Riverbend - Home Office | Head-office and back-office lines, including the company customer-support line | Yes |
Riverbend - Management | Managers' and executives' own lines | None |
Alert groups at every department location
| Group | Who gets it |
|---|---|
| Legal Threats | The store's general manager and the executives, as they happen |
| Customer Threats | The store's general manager |
| Upset Customers | The department manager. At Reception: the service manager. At Home Office: the executives. |
| Service Follow-up | The service manager and one named backup (customers saying nobody called back, or a long wait) |
| Insights Hub Access | The 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 / role | Locations | Groups | Products | Sees calls for |
|---|---|---|---|---|
| Dealer principal, CFO (executives) | Every location | Legal Threats everywhere; Upset Customers at Home Office; Insights Hub Access everywhere | All three | All lines at every location |
| Northside general manager | All four Northside departments, Management | Legal Threats, Customer Threats, Insights Hub Access at each Northside department | All three | All Northside lines, plus own line |
| Northside service manager | Northside Service and Reception, Management | Upset Customers, Service Follow-up and Insights Hub Access at Service and Reception | All three | All Northside Service and Reception lines, plus own line |
| Northside sales manager | Northside Sales, Management | Upset Customers, Insights Hub Access at Sales | All three | All Northside Sales lines, plus own line |
| Service advisor | Northside Service | None | After Call | Own line |
| Receptionist | Northside Reception | None | After Call | Own 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.
- How many physical locations (stores, offices, sites) take customer calls?
- Does each location run several departments (for example reception, service, sales, finance) with their own managers?
- Should an alert go to the manager of the department that took the call, rather than to one manager for the whole location?
- Should department managers see only their own department's calls, while location managers see their whole location and head office sees everything?
| Answers | Pattern |
|---|---|
| One location, one team | Single location. The shape the Base Intelligence Seat is built for. Example A. |
| One location, several teams, each with its own alerts | One location per team, plus Management. Example B. |
| Several locations, each run as one team, or departments that can share one manager's alerts | One location per physical location, plus Management. Departments inside a site are separated by groups. |
| Several locations, several departments each, alerts and call access by department | Corporate - location - department. The default for dealer groups and any multi-site business whose sites run several departments. Example C. |
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.
Next steps and help
Send us your information
Admins, branding, legal links and access choices from chapter 02.
Open the firewall
Allowlists in both directions before the first connector.
API and Integration Guide
Credentials, the Seat lifecycle, conversation and alert reads, webhooks and SDKs.
Integration Recipes
Thirteen ready-to-run integrations for your customers' developers.
Partner Launch Guide
What each team owns for launch, from naming to support.
| You need | Go to |
|---|---|
| Help with a configuration or a customer | support@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 secrets | security@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 exposed | security@tresic.cloud, straight away, copying your Tresic contact. Rotate what was exposed. |
| A vulnerability in Intelligence Cloud or the SDKs | security@tresic.cloud, with the steps to reproduce it. See the vulnerability disclosure policy. |
| Security documentation: certifications, penetration test summary, data location, subprocessors, BAA | security@tresic.cloud |
| Joining the admin skill beta, a new domain, a pattern decision | Your Tresic partner contact |