Sasha, Peak Demand Legal Voice AI assistant, guiding prospective and existing-client call flows in a modern law office
Firm-Specific Caller Journeys

Custom New-Client vs Existing-Client Call Flows for Law Firms

A prospective caller asking whether the firm can help and an established client calling about an open matter should not receive the same script. Peak Demand builds Legal Voice AI that separates these journeys, asks only relevant questions, and routes each request under the firm's approved rules.

Map Your Call FlowsCompare Both Paths
Prospect-safe intakeCapture fit and contact context without promising representation.
Matter-aware supportRoute verified existing clients to the right team.
Controlled exceptionsUnclear status, sensitive requests and new matters return to staff.
First Call Decision

The first useful question is often whether the caller already has a matter with the firm.

A caller seeking representation needs a carefully controlled first-contact experience. They may not know the relevant practice area, whether the firm serves their location, or how to request a consultation. The intake should orient the inquiry without inviting unnecessary confidential details before the firm completes its review.

An existing client typically has a different goal: reach the assigned team, pass along a document-related question, request an appointment, obtain a permitted administrative update, or leave a message about an active matter. Repeating a sales-intake interview can delay that request and damage the client experience.

A custom voice flow identifies the appropriate branch early, allows uncertainty and corrections, and keeps representation, identity verification, matter disclosure and professional judgment under the firm’s control.

Different journeys, one consistent front door.

The caller should not have to know the firm’s organizational chart. A well-configured first question directs the conversation while preserving a clear fallback for ambiguous callers.

Two Journeys, Distinct Outcomes

One call-answering experience, two substantially different workflows.

Prospective and existing clients can reach the same phone number. The difference lies in what the agent asks next, what data it may access, which actions are permitted, and how the record is classified for staff.

Path A · Prospective caller

New inquiry → appropriate intake review

Identify the general service request and collect the minimum approved contact and routing details. The firm controls consultation eligibility, conflicts review, and acceptance.

  1. Ask whether this is a new inquiry or an existing matter.
  2. Capture contact details and the broad legal service sought.
  3. Use approved office or practice-area eligibility rules.
  4. Collect only permitted pre-review information.
  5. Offer an approved consultation request or staff follow-up.
  6. Label the record as inquiry pending firm review.
Path B · Existing client

Known relationship → matter-specific assistance

Use firm-approved verification and matter references before sharing restricted information. The objective is to reach the correct responsible team or create the correct task.

  1. Confirm that the caller is seeking help with an existing matter.
  2. Apply appropriate identity and authorization checks.
  3. Ask for a matter reference or contact team where appropriate.
  4. Identify message, appointment, document, billing or update intent.
  5. Transfer or create an approved staff action.
  6. Record the actual outcome, not an assumed resolution.
Prospective-Client Experience

Help a prospective client reach the right intake stage without overstepping.

A first-time caller may simply ask, “Do you handle employment matters?” or “Can I speak to someone about a separation?” The Voice AI can provide approved service information and gather enough context to route the inquiry. It should avoid eliciting a detailed account of sensitive facts before the firm’s designated conflict and intake procedures allow it.

The workflow may vary by service area, geography, office, language, or intake capacity. A potential new client may receive a consultation-request path, an approved scheduling option, a general intake form, or a staff-review task. No path should imply that the firm has agreed to act.

FIT

Service-area identification

Ask what type of help is being sought using the firm’s categories, with a general option when a caller is unsure.

MIN

Minimum necessary details

Confirm how to reach the caller and any approved locality or timing information without collecting excessive confidential substance.

REV

Review before acceptance

Keep new-matter and conflict-check steps distinct from scheduling, marketing, and representation decisions.

Prospective law firm caller intake journey from initial inquiry through practice-area identification to consultation request or staff follow-up
Different callers need different first questions.A legal front desk can guide an unfamiliar caller toward reviewed intake while directing an existing client toward their established matter workflow.
Existing-Client Experience

Existing clients need continuity, not another introductory interview.

A returning client may want their assigned legal assistant, an appointment change, a status request, or an administrative message about their matter. A good flow starts with the purpose of that call and the firm’s identity-verification policy, not an exhaustive retelling of the original case.

When system permissions allow, the assistant can direct a verified caller to the correct team or create a categorized task. Where the client or matter cannot be verified, the workflow should preserve the message but avoid disclosing confidential files, case notes, or attorney availability that the firm has not approved.

ID

Authorization first

Distinguish caller recognition from verified entitlement to receive matter details.

FILE

Matter identification

Capture the correct file, office or team where permitted; do not guess when multiple matters exist.

ACT

Action ownership

Classify requests by staff action: callback, scheduling, document follow-up, billing or approved update.

Existing law firm client verification and secure matter-specific routing to messages scheduling and assigned case teams
Preserve continuity without exposing confidential records.An established-client request can be connected to an authorized matter and responsible team only when verification and system permissions support that action.
Exceptions & Reclassification

The real test is what happens when the caller does not fit neatly into either path.

Not every caller can answer “new or existing?” with confidence. A former client might need help with a completely new legal issue. A spouse, assistant, parent, or other third party might call on behalf of a current client. A caller may be contacting the firm on two separate matters or may correct an earlier answer.

These situations deserve explicit branch logic rather than a prompt that keeps repeating the same question. The AI should preserve already confirmed details, acknowledge uncertainty, limit disclosures, and route the unresolved status to staff.

Unsure of status

Use a neutral intake path and staff verification instead of assuming an existing relationship.

Existing client, new issue

Keep relationship context but require the correct new-matter and conflicts-review process.

Calling for another client

Capture identity and authorization context; disclose nothing restricted without approval.

Several open matters

Ask which matter the request concerns; escalate unclear ownership rather than guessing.

Changed answer

Correct the branch in-session without discarding previously verified contact information.

Urgent report

Apply the separate approved urgency-routing rules regardless of initial branch.

Records & Connected Systems

Do not let “new client” and “existing client” create the same downstream record.

A prospective inquiry may belong in a lead or pre-intake queue. An existing-client request may belong as a message, task, calendar action, or permitted matter update. Mixing those destinations can create duplicate client records, misleading reporting, or misplaced communications.

Peak Demand can design the branching and structured handoff around the firm’s actual systems. Direct lookups or write actions require validated access, API capabilities, field mappings, security controls, and client approval. Without that access, the workflow can still deliver separate, clearly labeled summaries for staff to process.

LEAD

Pre-intake record

Record the incoming inquiry with its status and approved routing context, not as an accepted client by default.

TASK

Existing-matter action

Use authorized matter references and explicit task ownership only where access and verification permit.

CTRL

Outcome and audit

Separate call transferred, message captured, appointment requested and update completed; do not treat them as equivalent.

Custom Legal Voice AI branching an incoming call into new-client existing-client and uncertain-status workflows
The destination must match the caller’s relationship with the firm.Prospective inquiries remain pending review, while authorized existing-client requests can be assigned to the correct matter team with clear task ownership.
Workflow Design

Build the branch around firm policies, not a rigid yes-or-no script.

A controlled design identifies the caller’s stated relationship, asks only the questions needed for that route, permits a correction, and separates administrative assistance from legal decisions. The process should also specify what happens when an integration, verification step, or live transfer cannot be completed.

Step 01Establish caller purpose and claimed relationship
Step 02Apply authorized identity and access boundaries
Step 03Select prospective, existing or uncertain route
Step 04Capture branch-specific details without duplication
Step 05Transfer, queue, or summarize with verified status
Firm Control & Boundaries

The assistant can route conversations; the firm determines the legal relationship.

Automation must not suggest that a caller has been accepted as a client, that a new legal matter is approved, or that confidential information can be shared based on an unverified phone number. The firm defines the disclosures, access restrictions, and permitted responses for both paths.

Legal Voice AI can support
  • Ask a clear introductory routing question.
  • Collect approved prospective-client contact details.
  • Apply permitted verification and matter-reference steps.
  • Route appointment, message and follow-up requests.
  • Generate distinct new-inquiry and existing-client reports.
Firm personnel remain responsible for
  • Accepting prospective clients or new matters.
  • Clearing conflicts and determining representation.
  • Authorizing access to confidential client information.
  • Interpreting legal facts and giving professional advice.
  • Resolving ambiguous caller identity or permissions.
Custom Builds for Law Firms

Your office structure and client lifecycle should determine how the call branches.

A boutique firm may need only two simple paths and a staff inbox. A multi-office practice may require different branches by practice area, language, current matter owner, calendar availability, or service region. The goal is not more questions; it is the minimum number of relevant questions in the right order.

Peak Demand designs custom Legal Voice AI around the firm’s actual intake policies, call examples, record access, task ownership, exception conditions and post-call reporting. Where external systems are integrated, deterministic middleware can enforce approved rules rather than leaving record writes or access decisions to unconstrained conversation.

Two branches should feel like one smooth experience.

The caller should not experience a complicated decision tree. Context already provided should follow the conversation, and switching paths should not force the caller to repeat everything.

Start with the handoff, then design the dialogue.

Define what a successful prospective inquiry looks like, what a completed existing-client task looks like, and who owns every unresolved path.

Map Your Client Call JourneysExplore Legal Voice AI
New vs Existing Client FAQ

Questions about prospect screening, existing-matter routing and firm-controlled boundaries.

These questions focus on the first relationship-based branch in legal call handling and the practical rules required to avoid inappropriate assumptions about representation or access.

Why should a law firm separate new-client and existing-client calls?
Prospective callers often need an introductory intake and careful representation boundaries. Existing clients more often need a matter-specific message, scheduling support, an update request, or a connection to their team. Separating the paths reduces irrelevant questions and misrouting.
How can Voice AI tell whether a caller is a prospective or existing client?
It can ask a direct, approved question and use permitted records or references where integration exists. It should not infer an established client relationship merely from a familiar phone number.
What happens when a caller is unsure whether they are a client?
The workflow can use a neutral clarification path, collect minimal contact details, and route to staff without falsely confirming client status or treating the caller as a new lead by default.
Does answering a prospective client mean the firm has agreed to represent them?
No. The assistant should communicate the firm-approved intake disclaimer and avoid stating or implying that representation, confidentiality, or an attorney-client relationship has been accepted.
Can an AI receptionist perform a conflict check?
It can gather approved names or entity information to support a firm-led conflict-check process. The firm, not the AI, decides whether conflicts are cleared and whether a prospective client can be accepted.
What information should a prospective client be asked first?
Typically the minimum approved contact details, general practice-area category, location or jurisdiction where relevant, and a brief non-sensitive description. The firm determines exactly what can be requested before conflict clearance.
Can existing clients skip the full new-client intake?
Yes. An existing-client branch can focus on identity confirmation, permitted matter reference, purpose of the call, and the correct contact or task, without repeating an entire prospective-client questionnaire.
How is existing-client identity verified?
Verification may use firm-approved questions and permitted system data. A caller ID match is not sufficient on its own for confidential account or matter disclosures.
Can an existing client ask for a case update?
The AI can record the request and route it to the appropriate team. It should only retrieve or disclose case information when authentication, permissions, integration, and firm policy explicitly allow it.
What if an existing client calls about a completely new legal matter?
The workflow can preserve the existing relationship context while moving the new matter through the firm’s approved new-matter and conflict-review steps. It should not automatically treat the new matter as accepted.
Can a prospective caller book an attorney consultation?
When the firm permits that appointment type and approved availability is accessible, the workflow may arrange a consultation or request scheduling. A booked consultation does not itself mean representation has begun.
Can the same phone number be used for both call flows?
Yes. The Voice AI can ask an early branching question and then follow separate approved paths under one published number, subject to the phone system configuration.
What happens if someone calls on behalf of a client?
The agent can capture the caller’s identity and relationship, and follow authorization and verification rules before discussing confidential matters. Unverified representatives should be directed to an appropriate staff-review path.
How should a law firm handle callers with multiple open matters?
The workflow can ask which matter the call concerns and capture an approved reference. If the matter cannot be determined reliably, it can create a staff review task instead of guessing.
Can incoming calls route by legal practice area?
Yes. Family, estate, business, litigation, employment and other categories can use different approved intake questions, office destinations, appointment types, and fallback procedures.
How are urgent calls handled in each branch?
Urgency rules may apply to either prospective or existing clients. If an approved trigger is reported, the call follows a separate firm-defined escalation path rather than relying on the routine branch.
What if no one at the firm is available?
The system can collect the approved minimum details, set an appropriate follow-up status, notify the designated team, and apply after-hours rules. It should not claim a staff member received the request unless confirmed.
Can the AI create different CRM or practice-management records?
Potentially. With authorized integrations, the prospective path may create an intake or lead record while the existing-client path may attach a message or task to an existing matter. Without access, the assistant can generate a structured staff-ready summary.
What if a caller changes their answer during the conversation?
A custom flow should allow the classification to be corrected and move to the proper branch while retaining already confirmed information, rather than forcing the caller to start over.
Does the AI provide legal advice on either call path?
No. Both paths remain administrative. The AI should not interpret law, recommend tactics, promise outcomes, give case-specific legal guidance, or decide representation.
Can different offices use different call branches?
Yes. Firms can configure office hours, practice coverage, intake eligibility, multilingual support, staff ownership, and escalation destinations by location, subject to validation.
How is this different from urgent call triage or conflict-check pre-intake?
This page addresses the first branching decision—whether the caller is prospective, existing, or uncertain—and the different conversational paths that follow. Urgent call triage concerns priority escalation; conflict-check pre-intake concerns capturing names and entities for firm review.
What should a law firm bring to a workflow discovery meeting?
Bring examples of new-lead calls and existing-client calls, scripts or disclosures, practice areas, existing matter-routing rules, scheduling tools, identity-verification policies, operating hours, and staff handoff requirements.
Map Your Call Experience

Give prospective callers and existing clients the right next step from the first question.

We can map your intake rules, established-client requests, team destinations, scheduling permissions, conflict-review boundaries, and exception paths into one custom Legal Voice AI experience.

Book a Workflow Discovery CallExplore Legal Voice AI
Bring examples of both call types

Prospective-client calls, existing-client messages, matter identification rules, intake disclosures, office routing, scheduling permissions, unresolved-caller scenarios, and the tools staff use afterward.