Everything you need to launch an intelligence business

Launching this is a short project with five or six owners across your business. Each chapter is written for the team that owns that part, and tagged so you can filter this page and forward just what applies.

Nothing is filled in here. Every question and every field lives in one workbook, which you complete and return before the launch coordination meeting.

Who this is for

What happens next

Trained, branded, and in market within thirty to sixty days of contract, where your platform is one we already connect to. Three lanes run in parallel from the day you sign.

One licensed seat that attaches to a seat you already sell. It runs on the phones your customers already have. Nothing to install, nothing to migrate, and no second system for the end user to learn.

Every seat carries all three capabilities below, plus 300 processing minutes per seat per month, pooled across the account, and API access included in the seat price.

Four things to confirm before a rep quotes. These belong in your qualification script rather than being discovered at provisioning.

If the account already pays for transcription

Some customers already have transcription switched on at the platform level. Most do not. Where they do, they are about to pay for it twice, and the usual answer is to turn the platform transcription off.

• There is no connector that imports existing transcripts. We work from the recording. Transcripts already sitting on the platform stay where they are.
• Retrieval is the actual upgrade. Accounts that have been recording and transcribing for years typically cannot find anything in it. For them the pitch is not transcription. It is being able to find and act on what was said.

This is your product. Your name, your brand, your customer. Our name appears nowhere your customers can see it. Three decisions, and all three are needed before we configure anything.

The product name

You choose it. Intelligence Cloud is available to use as-is if you want it, and several partners do. If you want your own name, nothing about the configuration changes.

Whatever you pick has to work in four places at once, which is the real constraint:

The access URL

Your users need somewhere to sign in. You choose the full address and it is yours entirely.

Keep the product name recognizable in the address. Your support team and your customers will both need to remember it.

Notification email

The product sends invitations, alerts, and digests. Those need a from-address, and you choose whose infrastructure they leave from.

If mail should leave from your domain, give us the address and the credentials to relay through, and we point notifications there.

The word that will cost you: conversational

Two phrases in this market differ by three letters and mean opposite things.

Published market research under the conversational AI heading is chatbot and virtual-agent research, sized around automated customer interaction (Research and Markets, 2026). Name your product conversational anything and four things follow:

1. Your reps sell it as automation, because that is what the word means to them.
2. Your customers expect something to answer their phone. It does not.
3. Your first churn conversation is about a promise nobody made.
4. Your legal exposure changes shape. The active litigation concerns AI that participates in the call. Post-call analysis sits in a smaller risk category, and there is no reason to name yourself into the larger one. See Chapter 08.

Avoid: conversational AI, conversational intelligence, AI receptionist, AI agent, voice AI, virtual agent.

Other language worth keeping out

You buy at wholesale and set your own retail. We publish no retail price, for you or for anyone. Two decisions sit here: how it is packaged, and what it costs.

Packaging or add-on

Both work, and plenty of providers do both. Tell us which you are leading with before the meeting, because the enablement differs.

Expansion revenue is available either way. Expanded access is bought at the account level when a customer asks for it, and packaging the base seat does not close that door.

Setting your price

Your price is yours to set and we do not advise on it. The band above is context, not a recommendation.

Your wholesale rate improves as your book grows

Markup is a ladder rather than a flat rate, and the rung is set by your committed monthly volume across your whole book, not by any one customer's invoice. Your rungs and your entry terms are on your order form. Worth knowing before you set retail, because the next rung changes what you can afford to discount.

Working out the minutes

The minute mechanic is simple, and it is worth walking through once so it never becomes a surprise on an invoice.

What to do with that before you price

Pull three months of minutes per account from your platform and divide by seats. That single number tells you which of three situations you are in.

The pooling matters here. A single heavy user inside an otherwise quiet account is usually absorbed. It is the whole account running hot that creates a bill.

Selling a minute pack of your own

There is no wholesale minute pack to buy. Your cost for anything above a customer's pool is the flat per-minute rate on your order form, and it does not change as your markup ladder improves.

What you can do is build a pack as a retail item of your own. If you sell on a promise that the customer's bill does not change month to month, per-minute overage breaks that promise. Price a block of minutes, absorb the variance against your contracted rate, and keep the breakage. It is the cleanest answer for a heavy account, and the arithmetic is entirely yours because your input cost is fixed.

A rep who cannot build the quote stops selling. Everything below is ready to copy into your quoting tool.

Items to create

Two items get you selling. The three expansion items are worth creating at the same time, because customers ask for them early and a request that has nowhere to go tends to die. Item 3 is optional and is a retail construct of your own rather than something you buy from us.

Item names are placeholders. Replace them with your own product name and adjust the wording to match how your catalog reads. Your wholesale rates are on your order form. Item 3 is the exception: there is no wholesale pack behind it. You price it yourself against your contracted per-minute rate.

Considerations for your sales process

Two documents arrive each month: a usage detail showing what every one of your customers consumed, and an invoice. Both are shown below so your billing team can map them before the first one arrives.

The usage detail

One row per customer, per item. This is what you rebill from. Each customer carries its own pool of minutes, so overage is rated per customer rather than across your book.

The invoice

The invoice is the greater of your minimum monthly commitment or your actual seat billing, plus usage. In the month shown here, seat billing has passed the minimum, so the minimum no longer appears as a charge.

This chapter and the next describe current law and active litigation. We are not your counsel, and neither is legal advice. What we can offer is where every provider before you has been surprised, and what your counsel will want in front of them.

The agreement you signed with us governs the relationship between us and you. The relationship between you and your customer is separate, and that is the one that matters, because your customer is the one talking to consumers. This is the item most likely to hold up a launch late.

Your customer agreement

Your existing terms may not permit what this requires. Your counsel is checking for three permissions:

• Can you store recorded conversations on behalf of your customer?
• Can you process those recordings for transcription and analysis?
• Can you use AI in that processing?

If any answer is no or unclear, an addendum is needed before the first seat is sold. We supply model language your counsel adapts into your own template.

The responsibility boundary

Compliance with recording and AI law in the jurisdictions where your customers operate is your customer's obligation and yours. It is not ours. This is in your agreement with us and it needs to flow through to your agreement with them. Chapter 08 covers what your customers do about it.

Insurance and liability

Adding conversation processing to your service changes your risk profile, and it is worth confirming your existing cover still fits before the first customer goes live rather than after.

Three things for your team or your broker to look at:

• Technology errors and omissions, and cyber liability. Confirm the policy responds to claims arising from processing customer conversation data, and that the limits are appropriate to the size of the base you intend to attach.
• Your customer agreements. Confirm the limitation of liability and indemnity provisions still hold once conversation processing is part of what you deliver.
• Vendor flow-through. Confirm that a claim brought against you by a customer does not, by the terms of your own paper, pass straight through to your suppliers, ourselves included.

We are not prescribing limits or naming a carrier. This is a checkpoint on the launch plan so it is not discovered late.

Healthcare

We have not completed a HIPAA audit, and we would rather say so now than have you find out later. We serve healthcare accounts, and we would rather they were not the first thing you lead with while that is true.

If you intend to sell into healthcare at all:

• We need a subcontractor business associate agreement with you. One agreement covers your whole base, not one per customer.
• Your contract with us already requires that protected health information is not sent to us before that agreement is signed.
• The chain has to be unbroken: your healthcare customer to you, and you to us. If your instance is hosted by Crexendo, confirm the agreement with them as well.

The agreement is staged after the reseller agreement deliberately, so signing us does not mean reviewing two documents at once.

What we do with the conversation

The next chapter tells you to ask every vendor in this category, including us, what they do with your customer's conversations. Here is our answer, so you do not have to ask.

Card data is redacted before anything is analyzed. Personal and health information is stored and analyzed rather than removed, because content removed from a transcript is content no analysis can read. It is held under scoped access, with retention split on identifiability: identifiable content follows the customer's own requirements, and derived, unidentifiable content is governed by us. We retrieve a copy of the recording, hold it under the stated retention schedule, and serve playback from it. We do not train models on customer conversations. The sub-processors that see conversation content are available on written request.

Disclosed vendors

If you maintain a vendor list under a customer agreement, a certification, or a procurement obligation, we belong on it. Disclosure is also the most effective defense against the litigation described in the next chapter.

Your reps will be asked about this in the field. This chapter gives them something better than a shrug. It is current as of August 2026 and the ground is moving, so check the review date at the top of the page.

Two things that surprise almost everybody

Sources: Cooley, April 2026; Hunton, May 2026.

One-party and all-party consent

Federal law is the floor and requires one party to consent (The Lyon Firm, June 2026). States may be stricter and a number are.

The published lists disagree with each other, which is itself the finding. Counts range from nine states to fifteen depending on how the compiler treats statutes that split between telephone and in-person, or that have been narrowed by case law.

Three compilations that do not agree: Recording Law, SIPNEX, Layer3 Labs, August 2026.

The risk that is genuinely new: the vendor as a third party

Plaintiffs are arguing that an AI vendor processing a call is not a tool of the business but a separate third party listening in. Claims run under the federal Wiretap Act and state statutes such as California's Invasion of Privacy Act (Holland & Knight, May 2026).

Three conclusions for your team:

1. Nondisclosure is the common thread. Case after case turns on nobody being told a third party was processing the conversation. Disclosure is the defense, not a nicety.
2. Whether the vendor uses the data for its own purposes is doing real work in these rulings. Ask every vendor in this category, including us, whether they retain your customer's audio and whether they train models on it. Get the answer in the contract.
3. Relief is not arriving from the legislature. California's SB 690 was expected to create a broad commercial purpose exemption. The July 2026 amendment dropped it and narrowed the bill to pen register claims, leaving the core wiretap provisions untouched (National Law Review, July 2026).

Biometrics

Voiceprints are regulated biometric identifiers in Illinois, Texas, and Washington. Illinois is the loud one because its statute carries a private right of action (NJ SaaS Law, July 2026). Texas has no private right of action, and its attorney general has still recovered more than $2.7 billion combined from two technology companies (RatedWithAI, July 2026).

The question is narrower than it sounds: does the system create a voice template. Some courts have found that telling speakers apart in a transcript can create a voice embedding sufficient to trigger the Illinois statute. In May 2026 nine coordinated class actions were filed in Illinois against major technology companies over voiceprints allegedly extracted from recordings to train voice models (American Bar Association, July 2026).

Where there is no IVR

The most common question your reps will get, and the one that stalls deals: a call center announces recording through an IVR, but most businesses do not run their people through one. Someone dials a direct number, a person picks up, and nothing plays.

One more point worth making to a customer who raises this: the obligation exists the moment they turn on call recording. Adding conversation intelligence does not create it. What it adds is a second thing to disclose, which is the processing.

Model disclosure language

Starting points, not finished language. Your counsel approves them before they go live.

Two design points matter more than the wording:

• Disclose the processing, not only the recording. The complaints above are about undisclosed processing by a third party. "This call may be recorded" was written for a world where recording was the whole activity.
• Your customer decides what happens when a caller declines. A disclosure with no alternative is not consent, so their call path needs a route that does not record. Worth stating plainly to them: a conversation that is not recorded produces no record in the platform, so nothing about it will appear in summaries, alerts, or reporting.

What to tell your customer about their own staff

Two facts answer most of what employees raise, and both belong in front of your customer before go-live:

• Alerts go only to the people the business nominates. There are two triggers in the base seat, and neither is a performance measure.
• Individual conversations are not scored, graded, or ranked.

An employee notice template is in Chapter 15.

We retrieve the recording and the call detail record from your platform as soon as a conversation completes. This chapter covers what makes that work on the first attempt.

API keys

Keys come 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, or a spreadsheet, including the launch workbook. Tell us before you rotate a key rather than after.

Platform connection

For NetSapiens-based platforms we confirm the hosting model, API version, allow listing, and the recording configuration once, and it holds for every customer after that. Older API versions we have not worked with before are the one thing worth flagging early rather than at activation.

NetSapiens is the connector that is live today. Other platforms are connector work we scope with you, and each connection is handled individually: some combination of call detail retrieval, recording retrieval, and an API connection. Raise it early rather than at activation so it can be scoped against your launch date.

Recording

Recording must be enabled for every user or line carrying a seat. Beyond that we need to know the retention period, whether the recording API is publicly reachable, and any restrictions in place such as encryption or signed URLs.

Other platforms in your base

Tell us what else your customers run on: SIP-only endpoints, Microsoft Teams, SIPPIO, Intermedia, or anything else, along with whether those calls route through your primary platform today. Native Microsoft Teams call support is not available at launch, so if a meaningful part of your base is on Teams it is worth saying so and having it weighed against other demand.

Identity and user management

Single sign-on is available in early Q4 2026.

API access is included in the seat price. What it covers is an event stream out and a conversation record read: webhook push when a conversation is processed and when an alert fires, plus query and retrieval of the conversation record. Every read is scoped to the user the integration authenticates as. Your team builds against it with a user credential. Customer-managed API keys are not available yet, and user and customer provisioning is done in the admin console rather than through the API.

Setup tasks

Your solutions engineers write the proposals and run the implementations, which makes them the internal owners of this product in practice. Their track goes deeper than the sales track and covers configuration, not just positioning.

The configuration decisions on every account

Three answers before provisioning. They belong in the proposal rather than being discovered at go-live.

What your SEs need available

• A demo account they can show without calling us.
• Their own seat, running on their own conversations. Nothing demonstrates this as well.
• The admin console, so they can configure a customer end to end.
• API and webhook documentation, for the customers who ask.

Training tracks

Configuration training is scoped to what you are actually selling.

Expansion is sellable from day one. Your reps can quote every expansion item alongside the base seat, and your solutions engineers field the detail when a customer wants to go deeper.

Nothing here waits on a roadmap. The three expansion items in Chapter 05 are live products with published wholesale rates, and they sit in your catalog next to the base seat. What tends to happen is that customers reach for them from inside the product rather than being sold them up front, which is why reps stay on the attach and the expansion conversation arrives on its own.

Where product feedback goes

Everything sent to support is logged and read. Nothing gets lost because it arrived through the wrong door.

What is most useful to us

• What customers ask for that they cannot get today.
• What your reps get asked in the field that they cannot answer.
• Which of your customers would talk to us about their experience, once they have one.
• Where the product gets in the way of your own operation.

You own the customer relationship, so you own the first call. We back you.

The three most common early tickets

1. No conversations are appearing. Nearly always recording not enabled on that user or line.
2. I got an alert and I do not know why. Alert recipients set without telling the recipient. The templates in Chapter 15 handle this.
3. Why can my manager see this. A configuration conversation that did not happen at provisioning. See Chapter 10.

All three are preventable at setup, which is why the admin console training and the communication templates matter more than they look.

We build the assets in your brand. You publish and send them. Our name appears on none of it.

What we deliver, what you deliver

The assets below are produced as part of your onboarding.

The sequence that works

The first step is the highest-return thing you can do and it costs only the seats. A rep who has watched their own conversation come back as finished work sells it differently from one reading a card.

Why now, for the net-new conversation

Analysts describe platform intelligence rather than feature count as the axis this category now competes on (Future Market Insights, February 2026), and at least one major UCaaS vendor shipped voice summaries and conversation intelligence into its platform this year (Custom Market Insights, July 2026). Your customers are being told a story. This is you telling one back.

Eight lines you can use anywhere, in any combination. These are the same lines running through the assets we build for you, so anything you write yourself stays consistent with what we hand over.

Lead lines

Capability lines

Five emails cover the whole launch. Two go to your own team, three go to customers. Fill in the bracketed fields, cut anything that does not apply, and send.

Seven gates. Each has evidence attached rather than an opinion. The full task list, with owners and dates, is the first tab of the workbook.

Every external claim in this guide, with its date. All sources are dated within six months of August 2026. Chapters 07 and 08 are re-checked quarterly at minimum.

Wiretap, eavesdropping, and AI vendor liability

Consent by state

These compilations contradict each other, which is why the guide recommends universal disclosure rather than a state-by-state policy. No single one should be treated as authoritative on any individual state.

Biometric privacy

State AI statutes

Market context