7 Accessibility Tests for a Law Firm AI Receptionist

By Michael Brunman, Co-Founder & CEO of Clerx, Former Litigator

An accessibility test for a law firm AI receptionist checks whether a person can reach the next step when the usual way of speaking, hearing, reading or booking does not work for them. Run the tests from the public phone number and website. Follow each scenario through to the staff handoff or appointment confirmation.

Voice recognition is one part of the experience. The caller also needs a way to ask for help, recover after a misunderstanding and use a different channel when necessary. A good test tells the firm where a journey breaks, what the caller hears and who can resolve it.

The U.S. Department of Justice's effective communication guidance explains that the appropriate aid or service depends on the nature, length, complexity and context of the communication and the person's usual method. The tests below are operational exercises. Have the firm determine its legal obligations and accommodation process separately.

1. Check whether the first prompt makes room for a real answer

Call from a normal phone, wait several seconds before answering and try a short response. Then repeat with a deliberate pause between phrases. Check when the system interrupts, how it handles silence and whether it gives the caller a clear way to continue after a missed answer.

A caller might say, “I need a moment to explain,” or “Please ask me one question at a time.” The test passes when the caller can finish and the receptionist confirms the next action. A long prompt followed by a short response window can turn an ordinary pause into an abandoned call.

Start with the firm's actual greeting and routing rules. The prelaunch receptionist test guide covers general readiness. Add accessibility cases with different pacing and interaction needs to the normal new-client and existing-client scenarios.

2. Check how the receptionist recovers from a misunderstanding

Use fictional names that can be spelled more than one way, and give a callback number at a natural pace. Correct a name, phone number or appointment detail after the receptionist repeats it. Observe whether the system keeps the correction and whether staff receive the right value.

A useful recovery is short and specific. “I may have the last two digits wrong. Can you repeat them?” gives the caller a manageable task. Repeating the whole intake questionnaire creates avoidable work. If the error persists, the caller should get a firm-approved way to reach a person or switch channels.

Test the stored result as well as the spoken response. A correction can sound successful while the old value remains in the record. Ask staff to find the resulting lead, identify the confirmed contact method and see whether anything remains uncertain. The intake metrics guide can help the firm include staff corrections and repeat contacts in its review.

3. Test the firm's relay-call procedure

Some callers use telecommunications relay services. The DOJ's guidance discusses accepting relay calls. Establish the firm's approved handling with qualified staff and the provider, then test through an appropriate method. Ask how the receptionist identifies a relay-assisted call, allows for conversational pauses and reaches a person when needed.

A transfer should preserve the caller's purpose and the fact that the caller is using an assisted route where appropriate. Do not make the caller explain a diagnosis as a condition of reaching staff. If the team cannot handle an interaction in its current configuration, the test should surface that gap before launch.

The transfer, booking and message guide is useful for defining the destination and fallback. Confirm what happens if the first person does not answer. A transfer that ends with silence gives the caller no way to tell whether the request was received.

4. Give the caller a usable way to switch channels

Test a caller who says, “I can read the details more easily than I can hear them,” and another who says, “I can’t use a text message.” The receptionist should offer an option the firm can deliver. Ask which method the caller prefers, confirm it and preserve it for staff. Avoid assuming that the same channel works for every caller.

A web chat or text option can help when a phone conversation is difficult, provided the route reaches someone who can act. Test whether the next channel can identify the inquiry without asking the person to start over. Use only the firm's approved verification and information-sharing rules.

Review Clerx website chat and Clerx text messaging against the workflow you want to offer. Verify which channels the firm has enabled, who owns replies and what happens outside ordinary staffing hours. An alternative that exists only as a link or an unmonitored inbox does little for the person who needs help now.

5. Check the website and booking experience with assistive tools

Start on the firm's home page. Using only a keyboard, find the contact option, open chat or the booking page, move through fields, correct an error and reach confirmation. Repeat a representative journey with a screen reader or with accessibility testing support. Check whether buttons and fields have useful names, whether focus remains visible and whether error messages tell the user what to fix.

The W3C WCAG quick reference provides criteria and techniques for web testing. Use it to guide the evaluation of actual pages, including third-party booking or payment pages the user has to complete. A handful of tests can expose barriers. Use a proper evaluation before making conformance claims.

Clerx Scheduling & Payments supports a configured appointment and payment flow. If your firm uses one, test the entire route with the actual meeting type and selected payment configuration. A caller who can select an appointment but cannot complete a required form or payment still needs a workable way to book.

6. Test an accommodation request separately from language routing

An accessible route and a multilingual route can overlap. A person may request a language interpreter, a sign-language interpreter, captions, a written confirmation or a different way to attend the meeting. Ask for the communication arrangement needed and give the request to the person authorized to coordinate it.

Do not automatically mark the request as resolved when a receptionist can switch languages. The multilingual receptionist testing guide covers a separate question: whether the first conversation and its handoff work in each supported language. Test what the firm will do when the attorney meeting needs an accommodation the voice system cannot provide.

Give the caller a clear status. “The team will contact you about that arrangement before confirming the meeting” conveys a real next step if someone is assigned to do it. Add the contact preference and owner to the staff record while limiting unnecessary sensitive details.

7. Run the fallback when your usual staff member is unavailable

Call after hours and request a person. Try an unstaffed extension, a failed transfer and a caller who cannot use the default booking route. Listen for what happens next. A pass means the caller hears a truthful description of how the firm can help and staff can find the request afterward.

The Clerx AI receptionist can follow configured intake and routing rules. Give the proposed setup concrete failure cases before relying on it. Ask the provider to show which actions are supported, what the team receives and which accommodation requests remain staff work.

Record the outcome for each test in plain language. Include the starting channel, the request, what the caller heard, what staff received and the fix owner. Use the script change approval process to track corrections and retest after changing the greeting, scheduling page or transfer destination.

What a test result should show

Suppose a fictional caller asks to receive appointment options by text after struggling to hear the dates. A useful result shows that the firm confirmed the preferred contact method, the caller received the options in the approved way and the person responsible could find the request. If the text arrives but does not support a reply, test how the caller can accept an option. The work ends when the person can complete the next action.

Use a few real staff members to perform the same scenario independently. Where appropriate, arrange feedback from people who use the communication methods being tested. Give the firm a way to correct a recurring barrier even when the voice transcript appears accurate. The point is reliable access to the next step across the actual phone, web and staff experience.

Frequently asked questions

What makes a law firm AI receptionist accessible in practice?

The person can understand the prompt, communicate a request and reach a workable next step through a suitable channel or staff route.

Should the test include relay calls?

Yes, when planning the firm's relay-call handling. Test it under the firm's approved procedure and confirm how staff receive the handoff.

What if the caller needs more time to answer?

Test pauses and interrupted responses. Configure a recovery or alternative route that gives the caller time to complete the conversation.

Does multilingual reception resolve an accessibility request?

Check the actual request and arrange the communication method the person needs. Reception language is one part of that decision.

Should booking and payment pages be tested too?

Yes. If the person must use those pages to complete the appointment, they are part of the intake journey.

What belongs in the staff note?

Record the requested communication arrangement, preferred contact method, action taken and owner. Limit details to what the team needs to act.

Does passing these tests establish compliance?

These scenarios identify operational issues. The firm should evaluate its obligations and any formal conformance claims separately.

When should the firm retest?

Retest after changing a script, phone route, chat widget, appointment workflow or the team responsible for following up.

Book a demo with Clerx today.

About the author

Michael Brunman is Co-Founder & CEO of Clerx, helping law firms improve client intake and communication. A former litigator, software engineer, and McKinsey consultant with an MBA from Harvard Business School, he brings legal, technical, and business experience to the challenges of running a law firm.