TrueVow is designed for solo and small PI firms that need structured intake, template-based intake flows, onboarding settings, firm-controlled recording policies, and clear boundaries around automation, legal advice, and case data.
See Benjamin Live → How TrueVow WorksFirm-controlled recording • Template-based intake paths • No legal advice • Approval required
A potential client call is not ordinary business data. It may include injuries, treatment history, liability facts, insurance details, deadlines, admissions, and emotional information from someone who may become your client.
So the right question is not:
The right question is:
That is what this page explains.
TrueVow is designed around controlled legal intake. Benjamin can support flexible caller responses, but the live intake path is governed by the selected intake template, routing settings, escalation logic, recording policy, and product boundaries.
That matters because intake is not ordinary automation. It touches potential clients, injuries, deadlines, insurance facts, and sensitive case information.
Approved firms choose an intake template during onboarding. Routing, booking, alerts, and recording settings are configured before go-live. Fully custom workflows require separate scoping and pricing.
Template questions, routing settings, escalation handling, and recording preferences are reviewed during onboarding.
Benjamin collects and structures intake information. It does not give legal advice or replace attorney judgment.
The core business record is structured intake data, scores, bookings, and risk flags — with recordings/transcripts optional by firm policy.
When enabled by the firm, Benjamin answers routed calls and follows the intake template selected during onboarding, along with configured routing, booking, alert, and recording settings.
Benjamin is not designed to freestyle legal advice, negotiate with callers, or make attorney judgment calls.
Benjamin helps collect and organize intake facts. Your firm remains in control.
Some firms want recordings and transcripts for quality review. Others do not. TrueVow supports both approaches.
Audio recordings and transcripts are optional. If enabled by the firm, TrueVow can retain them temporarily according to firm policy and help export them to the firm’s approved cloud storage.
The system relies on structured intake facts, scores, booking details, and risk flags as the core business record. Lowest-risk option for firms that do not need audio.
| Option | Availability |
|---|---|
| Recording/transcripts disabled | Available — lowest-risk option |
| 14-day retention when enabled | Included — enough for QA without becoming long-term custodian |
| Export automation to firm storage | Included with INTAKE |
| 30-day retention | +$49/mo |
| 180-day retention | +$199/mo |
| Long-term retention | Custom only |
If recordings are enabled, every relevant call flow should include a disclosure prompt. U.S. call-recording rules vary by state; some require all-party consent.
Example disclosure: “This call may be recorded and transcribed for intake quality and firm review. By continuing, you consent to this recording.”
For stricter states, explicit consent handling can be configured. If the caller does not consent, the call can continue without recording or route according to firm policy.
TrueVow is not intended to be the firm’s permanent archive for recordings or transcripts unless separately configured and agreed. The architecture is: record → transient TrueVow storage → export to firm storage → delete from TrueVow. The firm controls recording policy. The system keeps the business record structured.
Benjamin is designed around deterministic intake controls. That means the live-call path follows the selected intake template, configured routing and booking settings, and defined escalation logic. Custom branches require separate scoping, validation, and testing.
Generative AI, where used, is limited and controlled. It does not act as the authority for:
The live intake flow remains predictable, reviewable, and auditable.
Benjamin can handle flexible caller responses, but the system does not improvise legal guidance.
During onboarding, approved firms choose from TrueVow’s available intake templates, including a standard PI template and a more detailed PI template where available. The selected template is reviewed with the firm before activation. Routing, booking, alert, language, and recording settings are configured during onboarding.
Some firms may prefer the standard template. Others may choose the more detailed template during onboarding. The point is not one universal script.
Fully custom intake workflows are separate from standard onboarding. They require rewriting prompts, reorganizing the workflow, validating edge cases, testing routing behavior, and confirming that the custom flow behaves correctly before activation. Custom workflows are scoped and priced separately.
Random chatbot behavior. Unapproved legal language. Uncontrolled intake drift.
Depending on firm configuration, TrueVow may store:
The core operational record is the structured intake record, not a messy pile of raw conversation data.
That structured record helps your firm review:
LEVERAGE and SETTLE are designed to support case-value structure and settlement decision support using relevant case facts and comparable signals.
Client identifiers are not required for many case analysis workflows.
That means the firm can work with structured case information such as:
without unnecessarily exposing names or direct identifiers where they are not needed.
No client identifiers required for case analysis workflows.
TrueVow is a technology provider. It is not a law firm.
Benjamin supports intake. LEVERAGE supports case structure. SETTLE supports settlement decision context.
The attorney remains responsible for legal judgment.
Approved firms access TrueVow through the customer portal.
Access is role-aware. Not every user needs access to everything.
May need intake visibility and booking details.
May need full case review, risk flags, and settlement context.
Admin may need billing and user settings.
TrueVow does not claim universal bar compliance across every jurisdiction. Rules vary by state, and each firm remains responsible for its own professional obligations.
The better framing is: built for bar-conscious workflows.
That means TrueVow is designed around practical guardrails:
Your firm remains responsible for its own professional obligations, advertising rules, client communications, conflicts checks, engagement letters, and jurisdiction-specific requirements.
Unclear product boundaries create legal and operational risk.
Captures and screens calls through Benjamin, assigns intake priority, books consultations, and alerts the firm.
Helps structure case facts, damages, deadlines, and demand readiness. It does not replace case management or legal strategy.
Provides confidence-labeled settlement intelligence based on available comparable signals. It does not guarantee settlement value or replace attorney judgment.
Recording and transcript generation are optional. If enabled by the firm, recordings and transcripts are retained for 14 days by default, then automatically deleted unless the firm configures export or extended retention. Export automation to firm-controlled storage is included with INTAKE. If disabled, the system relies on structured intake facts, scores, booking details, and risk flags as the core business record.
Only if transcript generation is enabled by the firm. Transcripts are retained for 14 days by default. Extended retention (30-day, 180-day) is available as a paid configuration. Transcript retention follows the firm’s configured policy.
No. TrueVow is not a zero-knowledge architecture. That would be misleading because the system may process and store structured intake data, contact details, optional transcripts, optional recordings, and case-related facts depending on firm configuration. The better promise is controlled data handling, firm-configured retention, and structured records.
Benjamin is designed around deterministic intake controls and template-based intake paths. Where flexible caller responses or limited AI-assisted processing are used, they do not control legal advice, attorney judgment, or live-call legal decisions.
No. Benjamin is not a free-form chatbot. It follows the selected intake template, configured routing settings, and escalation logic.
Approved firms choose from available intake templates during onboarding. The selected template and operational settings are reviewed before go-live. Fully custom intake workflows are available only through separate scoping and pricing because they require rewriting, validation, and testing.
Yes, where the selected template includes them. Benjamin can support yes/no questions, structured responses, and approved open-ended prompts. The system captures the caller’s response into a structured intake record.
No. Benjamin is not designed to provide legal advice, make legal judgments, or create an attorney-client relationship. It collects intake information and routes qualified matters for firm review.
The law firm’s configured policy controls whether recording and transcript features are enabled, how long those materials are retained, and whether they are exported to firm-controlled storage. The default retention period is 14 days when enabled. Extended retention is available only by explicit firm configuration and billed separately. TrueVow is not intended to be the firm’s permanent archive.
No. SETTLE provides confidence-labeled settlement intelligence based on available comparable signals. It does not guarantee a specific outcome or replace professional judgment.
No. LEVERAGE is not case management software. It is a case value discipline layer that helps structure facts, damages, deadlines, and demand readiness.
Experience Benjamin live and see how intake logic, recording settings, lead grading, and structured records work before you commit.
See Benjamin Live (8 min) →