How to Switch From a Virtual Receptionist to AI Intake Without Losing Calls

By Attorney Michael Brunman, Co-Founder and CEO of Clerx

A law firm can switch from a virtual receptionist to AI intake without losing calls by treating the change as an operational migration, not a vendor toggle. Document the current call paths, define the future rules, test realistic scenarios, run controlled overlap, compare results, and keep a rollback route until the new workflow meets written acceptance criteria.

The safest sequence is:

1. inventory the current system
2. design the target workflow
3. configure and test off-line
4. route a controlled share of traffic
5. monitor quality and fix gaps
6. cut over with rollback available
7. retire the old service only after verification

This process protects continuity while giving the firm a chance to improve intake rather than merely recreate it.

The hidden risk is an undocumented workflow

Many firms believe their receptionist setup is simple: answer, take a message, transfer, or book. In reality, years of exceptions may live in emails, staff memory, vendor notes, phone settings, and calendar habits.

One partner accepts transfers during lunch. Another never does during court. Existing clients go to a paralegal, except billing calls. Spanish inquiries use a different person. Paid consultations require a payment step. Certain counties, matter types, or urgency signals receive special treatment.

If those rules are not documented, the new system cannot reproduce the useful parts or identify the broken ones.

Before changing anything, use a complete intake workflow checklist to expose dependencies.

Confirm that migration is the right decision

Different legal answering service models fit different firms. A human-first service may remain appropriate when the firm wants every interaction handled by an external person and accepts the related cost, variability, and workflow.

An AI receptionist for law firms may fit when the firm prioritizes immediate availability, consistent firm-defined questions, structured records, multi-channel alignment, and scalable coverage.

The decision should reflect actual requirements, not frustration from one bad call. Review 30 to 60 days of data: volume, time of day, caller type, transfers, booking, message quality, languages, fees, overages, and complaints.

Phase 1: inventory the current state

Create a single source of truth for:

• primary and published phone numbers
• carrier and phone-system ownership
• forwarding rules and schedules
• overflow, after-hours, and holiday routes
• voicemail destinations
• transfer targets and fallback numbers
• greetings and disclosures
• new-lead questions
• existing-client handling
• calendars and meeting types
• payment steps
• CRM or practice-management destinations
• languages
• escalation rules
• vendor contract and notice dates

Do not cancel the current service yet. Confirm who controls each number and whether the setup uses forwarding or a number owned by the provider. The FCC explains that number portability may allow consumers to keep an existing number when changing providers, but the precise process depends on the carrier and service arrangement. Never assume a number can be moved on the desired date without verification.

Export reports, scripts, call recordings where permitted, message templates, and historical data before access ends.

Phase 2: design the target workflow

Migration is an opportunity to simplify.

Start with caller categories:

• new prospect
• existing client
• court or government contact
• opposing counsel or another attorney
• vendor
• job applicant
• personal or other call

Then define the approved action for each category: transfer, message, intake, scheduling, information, or decline. Add fallbacks for unanswered transfers and unavailable calendars.

For prospects, specify accepted services, geographic scope, preliminary conflict identifiers, qualification questions, consultation types, fees, and human-review points. Clerx's guide to a good intake call can help keep questions concise and connected to action.

Finally, map the output fields. A summary should make the next step obvious. A transcript alone is not a workflow.

Phase 3: configure before touching live routing

Donna for inbound calls can be configured around the firm's approved questions, scheduling, transfer, and escalation rules. Written channels can be added when they belong in scope.

The firm should verify:

• exact firm name and pronunciation
• office hours and holidays
• attorney and staff names
• service descriptions
• prohibited statements
• transfer order and timeout
• backup notification
• calendar duration, buffers, and eligibility
• fee language
• privacy and AI disclosure language
• CRM field mapping
• duplicate-contact behavior

Connect systems in a test environment or controlled workflow where possible. Review the Clerx integrations relevant to the practice-management, scheduling, payment, and communication stack.

Phase 4: test realistic calls

Do not test only the happy path. Build a scenario set from actual call history.

Include:

• a qualified new lead
• an inquiry outside scope
• an existing client with a routine message
• an existing client with a firm-defined urgent signal
• a caller who gives an unclear name
• a bilingual or multilingual caller
• someone who refuses a required question
• a consultation request when the calendar is full
• a failed transfer
• a caller who asks for legal advice
• a repeat caller already in the system
• spam or solicitation

For each test, record expected and actual behavior. Acceptance requires more than pleasant conversation. Check routing, field accuracy, summaries, calendar events, notifications, transfers, and fallback.

The distinction between automation and human roles should be visible in every scenario. Legal advice, final fit, conflict decisions, and unusual judgment remain human.

Use a controlled parallel run

A parallel run means the new and old systems operate during an overlap period, with traffic divided by time, number, or routing condition. It does not mean two services answer the same call simultaneously.

Practical options include routing after-hours traffic to the new system first, using overflow when staff do not answer, or directing a secondary marketing number during a test window. The best method depends on the firm's carrier and phone setup.

Compare equivalent periods. Weekend traffic may have a different mix from weekday traffic. A new advertising campaign may change volume. Note these differences before drawing conclusions.

An overlap of several business days may be enough for a low-volume, simple workflow. A higher-volume or complex firm may need longer. Duration should be driven by scenario coverage and evidence, not a fixed industry rule.

Set written cutover criteria

Before testing, decide what must be true for full migration.

Criteria can include:

• calls route successfully
• required information is captured accurately
• existing clients follow the correct branch
• transfers and fallbacks work
• consultation rules are honored
• records reach the right system
• notifications arrive promptly
• legal questions are not answered
• escalation scenarios follow policy
• error rates remain below the firm's threshold

Use intake quality metrics rather than judging from a few memorable calls.

Keep a rollback plan

A rollback plan is a documented way to restore the prior safe route if the cutover exposes a serious problem. It should identify who can change forwarding, where calls will go, how quickly the change can happen, and how missed records will be reconciled.

Keep the old service active until the new route has been verified across normal business hours, after hours, transfers, booking, and system handoff. Schedule the final cutover when responsible staff can monitor it, not immediately before a weekend or holiday unless that is the specific test.

Monitor the first two weeks

Review a sample of interactions daily. Look at both correct outcomes and failures.

Track:

• answer and connection rate
• caller abandonment
• new-lead completion
• correct caller classification
• transfer success
• fallback success
• booking accuracy
• summary and field accuracy
• human escalation
• staff correction time
• complaints and confusion

Categorize issues. A telephony problem requires different action from a script problem. A scheduling error differs from a CRM mapping error. Change one variable at a time where possible.

Maintain a change log with the date, issue, adjustment, owner, and result. This matters when several people can edit scripts, calendars, forwarding, or CRM fields. Without a log, a fix in one layer can look like a new failure somewhere else, and the firm may not know which configuration produced the better outcome.

The objective is not zero human involvement. It is a reliable system that directs human attention to the right work.

Ethics and supervision

ABA Formal Opinion 512 discusses duties lawyers should consider when using generative AI, including competence, confidentiality, communication, supervision, and fees. ABA Model Rule 5.3 addresses responsibilities involving nonlawyer assistance. Firms must also apply their jurisdiction's rules and their own security requirements.

Practical safeguards include disclosure that the caller is interacting with AI, approved content boundaries, minimum necessary data collection, access controls, human escalation, vendor review, and ongoing supervision.

The system should never claim to be a lawyer, provide legal advice, guarantee an outcome, or imply representation has begun.

The bottom line

Switching from a virtual receptionist for law firms to AI intake can be safe when the firm controls the migration. The essential steps are documentation, configuration, realistic testing, controlled overlap, measured acceptance, and rollback.

Clerx helps law firms apply structured intake across supported channels. The reason firms explore replacing virtual receptionists with AI may be cost, consistency, availability, or integration. The reason a migration succeeds is disciplined operational ownership.

Frequently asked questions

Can a law firm keep its phone number?

Often, but it depends on who owns the number, the carrier, and the current arrangement. Verify portability and forwarding before canceling service.

How long should systems overlap?

Long enough to test representative volume, hours, caller types, transfers, booking, and handoff. Complexity and volume should determine the duration.

What should be exported from the old provider?

Export permitted scripts, reports, recordings, messages, templates, routing rules, and historical data before access ends.

How should scripts be converted?

Translate scripts into caller categories, questions, decisions, actions, fallbacks, and output fields. Remove obsolete exceptions.

What calls need human escalation?

The firm should define this by practice area, urgency, caller type, legal question, and operational risk.

How should existing clients be routed?

Use a separate branch with identity collection, message categories, transfer rules, and priority signals approved by the firm.

What should be tested?

Test qualified and disqualified prospects, existing clients, legal questions, full calendars, failed transfers, unclear information, languages, repeat callers, and system handoff.

What determines readiness for cutover?

Written thresholds for routing, capture accuracy, transfer, booking, handoff, escalation, and correction rates.

Is a rollback plan necessary?

Yes. It limits disruption if a serious phone, routing, scheduling, or integration problem appears.

What remains human-led?

Legal advice, conflicts, final fit, engagement, exception judgment, supervision, and quality ownership remain human.

Book a demo with Clerx today