Everything you need to roll out IntellaOne

One page with the requirements, setup steps, integrations, plan details, and security specs your team, IT, and procurement need before going live.

To roll out IntellaOne, configure a Workspace with your team's Context sources and review the messaging reps will use. Live Guidance brings that information into calls as Cards and suggested Next Best Move wording. Public-source research is not team-approved messaging and needs review before use.

System & browser requirements

IntellaOne runs in the browser. There's nothing to install. Live call features rely on the Web Speech API, which currently has the best support in Chrome.

Browsers

Chrome 110+ — required for live mic, speech detection, and zero-click voice flow
Edge 110+ — full support for everything Chrome supports
Safari 16+, Firefox 115+ — the IntellaOne dashboard, setup, and review work; live call mic features are limited

Operating systems

macOS 12 (Monterey) or later
Windows 10 or later
ChromeOS (current channel)
Linux with Chrome or Chromium 110+

Hardware

4 GB RAM minimum, 8 GB recommended
Any modern dual-core CPU (2018+)
Working microphone for live calls

Network

5 Mbps down / 2 Mbps up minimum
HTTPS access to *.intellaone.com
Access to accounts.google.com for OAuth

Mobile support: The IntellaOne dashboard and call review are mobile-friendly. Live call guidance with mic capture requires a desktop browser today. A native mobile app is on the roadmap.

Account setup in four steps

The guided setup takes you from sign-up to a live, shareable Workspace.

Create your account (~1 minute) — Sign in with your Google account, or create an account with your email and a password.
Build your first Workspace (~10 minutes) — Run the guided setup wizard: company info (auto-extracted from your URL), competitors, win/loss outcomes, buyers, and positioning. AI drafts positioning, discovery prompts, and objection responses for your team's review; approved content can surface in-call.
Share the rep link (~30 seconds) — One unguessable link opens the live call workspace — no login or setup for reps. Drop it into Slack, your CRM, or onboarding docs.
Go live on calls (same day) — Reps open the link, grant mic permission once, and start the call. IntellaOne listens and surfaces the right guidance hands-free.

Source governance

A concise Workspace source review sequence

Use this six-step sequence to keep permitted context, public research, generated guidance, and company-approved messaging distinct. It describes the current review path; the seller and the responsible human reviewer remain in control.

Step 1: Select or create the correct Workspace
Confirm the intended Workspace before changing sources. Workspace selection scopes the server-side source and guidance records, so a source is not implicitly shared with every team.
- Choose the existing Workspace that owns this motion, or create a separate one when a genuinely separate source scope is needed.
- Do not treat a call link or a configured Workspace as proof that its source content is approved.
Step 2: Connect only permitted Context
Review provider permissions, explicit consent, and selected folders, pages, or other scopes before data enters the Workspace. Select only authorized, team-reviewed material: a permitted connector selection may sync documents directly as approved Context, while the picker itself is an import scope rather than a human approval gate.
- After sync, verify which documents and chunks entered the Workspace. Generated guidance is a separate object and can remain a pending draft even when its source Context is approved.
- For connector-managed source fields, update the upstream system and then allow the connector's normal sync path; do not assume instant sync.
Step 3: Agree who reviews the source and guidance
A human reviewer owns the decision about evidence, audience, and wording. Workspace owners and admins can record an owner and review date in the source detail drawer; Workspace members can view them. These fields record responsibility, not assignment routing or notifications. A review date does not automatically expire content or block its use.
- Open a source in the Context library, enter its owner and review date under Source responsibility, and choose Save responsibility. Leave a field blank to clear it. Inspect the supporting source before calling generated language approved.
- Keep the reviewer responsibility explicit; connected source selection is not a promise of a human approval gate for every source.
Step 4: Review drafts in the approval queue
Treat pending, approved, and rejected as meaningful review states. AI and public-source research produce drafts or research leads; they never become approved team messaging just because they sound polished.
- Review public URL or otherwise unknown-provenance guidance individually. Company-provided guidance may be eligible for the existing bulk approval path, while unknown and public sources are not.
- Edit or reject a draft when its evidence, scope, or wording is not ready. Draft generation does not auto-approve it.
Step 5: Test representative questions yourself
Use the seller workflow with realistic questions rather than treating generation as a test result. There is no dedicated test button in this public sequence; the seller reviews what appears and decides what to say.
- Try generic prompts such as “How are you different from our incumbent?” and “Can this support our workflow?”
- Also test missing evidence, such as “Which plan includes this feature?”, and conflicting evidence, such as “Which version or metric is current?” Escalate or follow up instead of guessing.
Step 6: Correct upstream, re-sync, and verify again
Replace or re-add corrected manual material, or update a connector-managed source upstream, then re-sync and review generated guidance again. Do not treat deleting a source as proof that every related claim disappeared.
- Deleting a sole-source item can remove its guidance. Multi-source guidance can remain approved verbatim with only the deleted source ID stripped; review, edit, or reject surviving guidance before using it.
- There is no separate retire action or promise of automatic expiry, stale-source blocking, new controls, Workspace publishing, or a paywall bypass. Keep the human review loop in place.

Connector status legend

Use the catalog as the current status source; do not collapse these states into one “Unavailable” label.

Available available: The catalog marks this connector available; check its current scope and permissions. Examples in the current catalog: Zoom (Live), Google Meet, Microsoft Teams, plus 8 more.
Beta beta: The catalog marks this connector beta; verify the behavior and scope your team needs. Examples in the current catalog: HubSpot, Chorus, Notion, plus 2 more.
Planned planned: The catalog marks this connector planned; do not treat it as available for this workflow. Examples in the current catalog: PSTN / SIP & Dialers, Highspot, Seismic, plus 23 more.
Coming soon coming_soon: The catalog marks this connector coming soon; do not treat it as available for this workflow. Examples in the current catalog: Gmail, Google Calendar, Outlook & Outlook Calendar, plus 4 more.
Built in built_in: The catalog marks this capability built in rather than as an external connector. Current catalog entries: IntellaOne Web Intelligence.

Google Drive — Available (available): Selected folders are read as citable context; selection is not approval.
Slack — Available (available): This catalog entry is outbound curated sharing, not Slack history imported as source context.
Chorus — Beta (beta): Read-only historical conversation context rather than a live transcript source.

Open the full integrations catalog

Integrations: required vs. optional

All you need to get started is an account. Every integration is opt-in and unlocks richer context.

Required — An IntellaOne account

Sign in with Google OAuth (Gmail or Google Workspace) or any work email and password
No additional admin consent required for individual reps

Optional but recommended — Revenue stack

Salesforce & HubSpot — Account, contact, and opportunity context. CRM write-back requires explicit rep initiation or approval: proposal approval authorizes proposal writes, while forwarding notes occurs only after an explicit rep action.
Zoom (Live) & Google Meet — Live and post-meeting transcripts as conversation context
Microsoft Teams, Gong, Chorus, Claap & Zoom Recordings — Prior-call transcripts and insights as live context
Google Drive, Notion, SharePoint & Confluence — Approved documents as cited answer sources
ZoomInfo — Company and contact enrichment as call context
Slack & monday.com — Follow-up commitments and curated insights, delivered to tools you authorize

What's included in each plan

Use Live Guidance free during calls. Pay only when you want to save and standardize. Save and Team are $79/user/month. Integrations are included on every plan. Enterprise is custom — talk to us for advanced security, dedicated onboarding, and procurement-friendly terms. See full pricing.

Security, privacy & technical specs

No stored call audio — Depending on the call mode, speech recognition runs in the browser or audio streams to our speech provider in real time and is discarded after transcription. Audio is never recorded or stored.
Clear data handling — Transcript text and the deal context you enter are processed by our servers to generate guidance. Connected tools sync under your own credentials. Newly saved connector credentials are encrypted before storage. CRM write-back requires explicit rep initiation or approval: proposal approval authorizes proposal writes, while forwarding notes occurs only after an explicit rep action.
No model training on your data — Customer input is never used to train or fine-tune foundation models. Your messaging stays yours.
Infrastructure — Hosted on US-based cloud infrastructure. PostgreSQL with encrypted connections. HTTPS-only with HSTS and modern security headers.
SOC 2 readiness — Logging, access controls, and audit trails are in place. Formal SOC 2 Type II audit is on the Enterprise roadmap.
Auth & sessions — Google OAuth or email/password sign-in with PostgreSQL-backed session management. AE share tokens are scoped per workspace and revocable.

For the fuller factual overview of access, data flows, and retention limits, see our Security & Data Handling page.

FAQ

What do I need to use IntellaOne?

A modern desktop browser (Chrome recommended for live mic features), an account (Google sign-in or work email), and a stable internet connection. No installs, no plugins.

Does IntellaOne work on mobile?

The IntellaOne dashboard and reviewing call output work on mobile. Live call guidance requires desktop Chrome for microphone and speech detection.

Do I have to connect Salesforce or Gong?

No. No third-party integration is required. CRM (Salesforce, HubSpot), Conversation (Zoom (Live), Google Meet), Conversation Intelligence (Microsoft Teams, Gong, Chorus, Claap, Zoom Recordings), Context (Google Drive, Notion, SharePoint, Confluence), Data (ZoomInfo), Workflow (Slack, monday.com) connectors are all optional and unlock richer context.

Is my call audio sent to the cloud?

IntellaOne never records or stores call audio. Depending on the call mode, speech recognition runs in the browser or audio streams to our speech provider in real time and is discarded after transcription. Transcript text is processed server-side to generate guidance, and customer input is never used to train models.

How long does setup take?

The guided setup wizard walks you from sign-up through creating a shareable Workspace and going live.

Can I deploy IntellaOne across my whole sales org?

Yes. The Team and Enterprise plans add shared libraries, messaging guardrails, and an admin dashboard. Integrations are included on every plan; SSO is on the Enterprise roadmap.

Try Live Guidance free or request a demo.

Need a printable handout for procurement or IT? Download the IntellaOne specs PDF — a single-page summary of everything above.