Law Firm Intake Quality Assurance: A Weekly Scorecard for Calls, Chat, and SMS

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

Law-firm intake quality assurance is the recurring process of reviewing conversations, records, routing decisions, and outcomes against the firm's approved standards. A practical QA program samples calls, website chats, and text conversations, scores observable behaviors, investigates exceptions, assigns improvements, and verifies whether changes work.

QA is not a hunt for one awkward phrase. It asks whether the intake system consistently created the right next action. A conversation can sound polished and still fail because the lead was assigned to nobody, the calendar event did not save, a current client was treated as a new prospect, or a priority alert went to the wrong person.

For solo and 3-5 attorney firms, a lightweight weekly review can reveal more than a large monthly dashboard with no conversation context.

What intake QA should measure

A useful scorecard covers five dimensions:

1. Responsiveness: Was the inquiry answered or recovered quickly?
2. Conversation quality: Was the interaction clear, calm, and appropriate?
3. Intake accuracy: Were required facts collected and represented faithfully?
4. Workflow execution: Did qualification, routing, scheduling, payment, and handoff work?
5. Outcome quality: Did the inquiry reach the next step and ultimately convert or close correctly?

The firm should score only what the reviewer can observe. Avoid vague labels such as “good call.” Define the behavior that earns a pass, partial score, or failure.

The law-firm intake metrics guide provides the quantitative layer. QA adds the qualitative evidence needed to explain why a number changed.

Build a scorecard around the firm's real workflow

Start with the firm's approved intake playbook, not a generic template. The scorecard should reflect practice areas, service geography, caller types, consultation rules, escalation paths, languages, and connected systems.

A 100-point model might allocate:

• 15 points to identity, caller type, and safe contact;
• 20 points to required intake information;
• 15 points to qualification and conflicts routing;
• 15 points to priority recognition and escalation;
• 15 points to consultation, payment, or message execution;
• 10 points to record accuracy and ownership;
• 10 points to tone, clarity, and next-step explanation.

Weights should follow risk and business impact. A criminal-defense firm may weight priority routing heavily. An estate-planning firm may place more weight on consultation type and family relationships. An immigration firm may emphasize language continuity and attorney review of stated dates.

Define critical failures separately

Some failures should not be averaged away by a high total score. Create a critical-failure list that triggers immediate review. Examples include:

• legal advice or an unsupported legal conclusion;
• a promise of representation or outcome;
• a missed firm-defined safety or timing indicator;
• sensitive information sent to the wrong person;
• an opposing party invited to disclose unnecessary facts;
• an appointment described as confirmed when it failed;
• a payment recorded incorrectly;
• a current-client request attached to the wrong matter;
• a priority transfer dropped without recovery;
• a record created with no owner or next task.

The firm's AI receptionist security checklist can help identify privacy, access, recording, retention, and integration events that deserve critical treatment.

Sample intelligently, not conveniently

Do not review only successful daytime calls. A balanced weekly sample should include:

• new prospects and current clients;
• qualified, unqualified, uncertain, and abandoned inquiries;
• calls, website chats, and SMS;
• business hours, after hours, weekends, and peak periods;
• successful and failed transfers;
• booked, unbooked, rescheduled, and no-show consultations;
• English, Spanish, and other supported languages;
• each major practice area and lead source;
• short, long, interrupted, and corrected conversations;
• low-scoring or exception-flagged interactions.

For a small firm, 10 to 20 interactions per week may be enough to expose patterns if the sample is intentionally varied. The number is a proposed operating range, not an industry benchmark. High-volume firms should use risk-based and random sampling together.

Review the conversation and the downstream record

Quality exists across the entire chain. For each sampled interaction, compare:

1. what the caller or visitor said;
2. what the summary reported;
3. which fields were written;
4. which qualification or routing rule fired;
5. which appointment, payment, message, or transfer action occurred;
6. who received the task or alert;
7. what happened next.

The Clerx integrations directory shows the practice-management, CRM, scheduling, payment, messaging, and automation systems that may participate in the workflow. QA should test the handoff that the firm actually uses, not merely the visible conversation.

If staff repeatedly correct the same field, investigate the prompt, validation rule, mapping, or source data. If the summary is accurate but nobody acts, the problem is ownership rather than conversation quality.

Score phone calls, website chat, and SMS consistently

Channels behave differently, but the core standards should remain aligned.

On calls, review interruptions, background noise, name spelling, spoken dates, transfer recovery, and whether the caller understood the next step. The Clerx AI Receptionist should follow the same firm-approved logic across covered hours.

For Clerx Website Chat, review how quickly contact information is captured, whether questions fit the page and inquiry, and whether a visitor can reach scheduling or human review without looping.

For Clerx Text Messaging, review identity confirmation, consent and opt-out handling under firm policy, sensitive previews, response gaps, link accuracy, and continuity from another channel.

Do not reward a channel for collecting more information than necessary. Progressive intake often creates a better client experience and a safer record.

Evaluate qualification without turning it into legal judgment

QA should verify that the intake applies the firm's operational rules: practice area, geography, broad matter category, language, consultation format, fee, referral source, and other approved criteria.

It should also confirm that uncertain cases enter a review path instead of receiving an invented answer. The law-firm intake-form guide explains how staged questions reduce friction and overcollection.

For conflicts, review whether required names and roles were collected, spelling was confirmed, possible matches were flagged, and the system stopped at the right point. The AI intake and conflict-check workflow makes clear that automation may support collection and search while the firm retains final analysis.

Review booking, payment, and transfer outcomes

High-value failures often occur after a good conversation. Check whether:

• the correct attorney and consultation type were selected;
• availability, buffers, time zone, and location were respected;
• the correct fee and payment path were used;
• confirmation and reminders were sent;
• a failed payment or calendar action triggered recovery;
• a warm transfer connected to the approved recipient;
• a failed transfer returned to a safe fallback;
• the final outcome was written to the record.

The paid-consultation workflow and missed-call text-back guide provide useful QA scenarios for revenue and recovery steps.

Use a weekly review meeting with clear ownership

Keep the meeting short and evidence-based. A 30-minute weekly agenda can be:

1. Review the score trend and any critical failures.
2. Listen to or read two strong examples and two failed examples.
3. Identify the root cause of each failure.
4. Assign one owner and deadline for every change.
5. Decide how the change will be tested.
6. Recheck the prior week's changes.

The root cause may be a question, script, knowledge source, availability rule, system mapping, staff process, or policy gap. Avoid changing the AI prompt when the real problem is that nobody owns weekend callbacks.

Use the firm's intake SLA to connect QA findings with response targets and escalation responsibility.

Turn findings into controlled improvements

Every improvement should follow a small cycle:

1. Describe the observed failure.
2. Identify the likely cause.
3. Make one bounded change.
4. Test it with normal and edge-case scenarios.
5. Monitor the next live sample.
6. Keep, revise, or reverse the change.

The AI receptionist go-live testing guide remains useful after launch. Regression testing matters because a new rule can solve one scenario and disrupt another.

Maintain a change log with date, owner, reason, affected workflows, test results, and approval. This makes quality improvement auditable and prevents teams from forgetting why a rule exists.

Build a dashboard that connects quality to conversion

Combine scorecard results with funnel outcomes:

• answer and recovery rate;
• intake completion;
• qualified rate;
• time to human review;
• booking and payment completion;
• show rate;
• transfer success;
• duplicate and correction rates;
• lead-to-client conversion;
• revenue by source where appropriate.

Look for relationships, not just averages. A source may produce fewer leads but stronger intake scores and conversions. After-hours inquiries may score well yet convert poorly because callbacks are late. One practice area may book many consultations but have a low show rate.

Do not claim causation from a small sample. Use the patterns to choose what to investigate, then test changes over time.

Protect privacy during QA

Quality review itself creates access to sensitive information. Limit who can review calls, transcripts, messages, and records. Define retention, redaction, download, sharing, and deletion rules. Use representative examples without circulating unnecessary client details.

ABA Model Rule 1.6 requires reasonable efforts to prevent unauthorized access to information relating to a representation. ABA Formal Opinion 512 discusses competence, confidentiality, supervision, and lawyer responsibility when AI tools are used.

QA should confirm that automation supports intake rather than legal judgment. Attorneys remain responsible for the firm's professional decisions, policies, and supervision.

Frequently asked questions

What is law-firm intake quality assurance?

It is a recurring process for reviewing intake conversations, records, routing, and outcomes against defined standards, then assigning and verifying improvements.

What should an intake QA scorecard include?

Include responsiveness, caller identification, required information, qualification, conflict routing, priority handling, booking or messaging, record accuracy, ownership, tone, and next-step clarity.

How many interactions should a small firm review weekly?

A proposed starting range is 10 to 20 deliberately varied interactions, supplemented by every critical exception. Firms should adjust for volume, risk, and practice mix.

What is a critical intake failure?

It is an event that requires immediate review regardless of the total score, such as legal advice, wrong-recipient disclosure, missed priority routing, false confirmation, or an unowned task.

Should firms review only calls?

No. Review calls, website chat, SMS, and the downstream records and actions. The same prospect may move across multiple channels.

How should AI intake accuracy be checked?

Compare the original interaction with the summary, fields, classification, routing, appointment, payment, task, and final outcome.

Who should own intake QA?

Assign one operational owner with attorney oversight. Participants may include the managing attorney, intake lead, administrator, and technology owner.

How often should the scorecard change?

Change it when firm services, risks, channels, workflows, or systems change, but keep stable definitions long enough to measure trends.

How does QA improve conversion?

It identifies the specific breakdowns behind lost opportunities, such as missed priority indicators, confusing questions, failed bookings, slow callbacks, or poor handoffs.

Can QA replace attorney supervision?

No. It is a tool for supervision and improvement. Lawyers retain responsibility for legal judgment, ethics, policies, and professional obligations.

Book a demo with Clerx today.