Some firms want the strongest transcription accuracy available and are comfortable with a small, clearly-scoped amount of cloud AI processing to get it — as long as they control exactly what leaves their network and when.
CoolScript AI LexaCore's Hybrid deployment keeps your infrastructure, your Filevine integration logic, and most of your call processing on-prem — the same secure pipeline as our On-Prem Only option — but lets you selectively enable higher-accuracy transcription tiers that use a named, single-purpose cloud AI vendor for that tier only.
No open-ended "AI platform" with unclear data handling.
No bundled analytics or ad-tech riders.
Just specific, named vendors, used only for the tier you turn on, only for the calls you route to them.
| Tier | What Runs It | Where Audio Goes |
|---|---|---|
| Basic | Whisper base.en, local | Never leaves your network |
| Aware | Deepgram | Audio for that call only, only if enabled |
| Premier | OpenAI | Audio for that call only, only if enabled |
| Platinum | AssemblyAI | Audio for that call only, only if enabled |
Every tier above Basic is opt-in, per client, per date range — set it in the control panel, turn it off just as easily. Filevine filing, project routing, archiving, and Zoom transcript sync work identically regardless of which tier processed the audio.
CoolScript AI automatically:
All without exporting anything beyond the specific audio needed for the specific tier you've turned on.
CoolScript AI attaches call records directly to the appropriate Filevine project — without flooding attorney activity feeds or triggering unnecessary notifications, regardless of which tier processed the call.
Instead of posting a visible note for every call, CoolScript AI can quietly:
| What Matters to Your Firm | CoolScript AI Hybrid | RingCentral / VXT |
|---|---|---|
| Where your call recordings live | On your systems; only enabled-tier audio ever leaves, to a named vendor | Stored in vendor cloud, always |
| What leaves your network | Nothing by default (Basic); a named single-purpose vendor, only for tiers you enable | Everything, to one vendor platform |
| Transcript processing model | You choose the tier — from fully local to highest-accuracy cloud | Single-pass cloud processing, no choice |
| Vendor exposure | Multiple named, swappable, single-purpose vendors — no lock-in | One vendor holds everything |
| Summary logic control | Firm-controlled formatting and structure | Vendor-defined summary format |
| Client & matter matching | Custom routing rules reduce mis-filed calls | Strict number-matching rules may require cleanup |
| Historical call archive | Backfill years of prior calls quietly into Filevine | Primarily forward-looking integration |
| Internet outage impact | Basic tier keeps running; cloud tiers pause until connectivity returns | Cloud-dependent processing, always |
| Long-term cost model | Predictable infrastructure cost, plus usage only for tiers you enable | Usage-based pricing tiers |
The same tier logic applies to Zoom meeting recordings (MP4) dropped in your intake folder — transcribed and summarized at whichever tier you've enabled, with caption files (SRT, VTT) synced via secure rsync and cataloged alongside telephone communications inside Filevine.
Only if you've enabled a tier above Basic for that client, and only the audio for calls on that tier. Basic-only clients never touch any cloud vendor.
Yes — tiers are set per client, and changes take effect immediately, no restart needed.
Yes, at any time, from the control panel. Nothing about your Filevine integration changes when you do.
Deepgram, OpenAI, or AssemblyAI — whichever tier you've enabled — see only the raw audio for the specific call being transcribed under that tier. No other case data, documents, or Filevine content is ever sent to them.
If you'd like a walkthrough of the Hybrid tiers, how the routing works, or exactly what data goes where, contact us to schedule a short call.
If your firm has no interest in any cloud AI processing, even on a named, single-purpose, opt-in basis, our On-Prem Only deployment keeps everything — transcription and summaries alike — on your own infrastructure.