Keep Your Law Firm’s Phone Number: Forwarding Rules for AI Receptionist Coverage

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

The direct answer

Call forwarding sends calls from an existing number to another answering destination according to the phone provider’s rules. Number porting moves control of a number between providers. They are different changes. A firm evaluating an AI receptionist should establish whether forwarding can provide the desired coverage before assuming that its public number must move.

Clerx AI Receptionist supports configured call handling, but the exact telephone arrangement depends on the firm’s provider and setup. Confirm the route, trigger, caller identification, transfer behavior, and recovery steps during implementation.

A successful setup preserves the number callers recognize and delivers calls where the firm intends. It should be tested from outside the office, not inferred from a settings screen.

Choose the coverage trigger

The firm may want all calls answered by the service, calls forwarded after a period without an answer, calls forwarded when the line is busy, or a scheduled after-hours route. Those are distinct operating choices.

Check which triggers the current provider supports and how they interact. Do not assume every phone system uses the same menu names, dial codes, or conditions.

The call-overflow guide addresses staffing coverage. This article focuses on the telephone configuration that makes that coverage real. A sound intake script cannot fix a forwarding rule that sends the wrong calls to it.

Establish who controls the number

Identify the account owner, authorized administrator, and support route for the telephone service. Keep the information accessible to the people responsible for coverage.

If porting is proposed, ask why it is required and review the operational consequences. Do not approve a port merely because forwarding and porting were described as the same step.

The FCC’s number-porting guidance explains the general distinction involved when changing providers. It does not establish which forwarding configuration your firm has or whether a particular AI service requires a port.

Test what the caller experiences

Place an external call during each coverage condition. Listen to ring time, greeting, disclosure, silence, voicemail, and the transition to the receptionist.

A mobile test on the same network may reveal only part of the experience. Where practical, include another outside line and ask the implementer which scenarios matter for the provider.

The pre-launch testing guide provides a framework for documenting observed results. Record whether the intended trigger actually occurs rather than simply noting that forwarding is enabled.

Verify caller identification and record matching

Forwarded calls may carry caller information differently depending on the telephone arrangement. Confirm what the receptionist receives and what reaches the firm’s records.

If every call appears to come from the firm’s own forwarding number, contact matching may behave differently from the intended design. Treat that as a test requirement, not a universal claim about phone providers.

For firms using MyCase or Clio, demonstrate the actual downstream contact and call summary. A working telephone connection does not independently prove correct record association.

Inspect the transfer path back to staff

A transfer can accidentally return to the public number that forwards to the receptionist. That may create a loop instead of reaching a person.

Use a staff destination approved for the purpose and test answered, unanswered, and busy outcomes. The warm-transfer framework helps evaluate these branches.

Confirm what the caller hears and what staff see. A transfer attempt should not be recorded as a successful connection merely because the telephone system initiated it. Keep a useful alternative available when nobody answers, according to the firm’s approved policy.

Keep texting separate from voice routing

Forwarding voice calls does not by itself establish that SMS moves to the same destination. A firm may have distinct voice and messaging arrangements for the public number.

If Clerx text messaging is part of the proposed setup, test incoming texts, replies, sender identity, and staff visibility independently. Do not tell callers to text the number until the actual written route is verified.

The SMS operating guide provides broader context. Telephone coverage and written intake need coordinated instructions even when the technical routes differ.

Document a restoration route

Before activation, record the prior settings and who can restore them. Agree a temporary destination if the new path is unavailable. Confirm whether the phone provider, the firm, or the implementer must make the change.

The ownership framework can identify who handles ordinary configuration changes and urgent routing corrections. Do not turn an internal restoration goal into an uptime or response guarantee.

A recovery plan should include an external verification call. Reverting a setting without checking the result may leave the team believing calls are back at the desk when they are still routed elsewhere.

A Texas solo-practice example

Consider a fictional Texas criminal-defense lawyer who wants office staff to answer first during business hours and AI coverage when they cannot pick up. The practice already advertises one main number.

The implementation should establish whether the phone provider supports the desired no-answer route and how existing voicemail interacts with it. Test that the receptionist receives calls before the original voicemail captures them, using the actual agreed timing.

Next, test a caller requesting staff. The transfer destination should reach the intended person without returning to the same forwarding loop. After hours, test the separate availability wording and message path.

Finally, send a text to the advertised number. If messaging has not been configured, voice forwarding should not be presented as proof that texts are covered. The firm can launch the verified voice route while keeping its public messaging claims accurate.

Define completion and review after launch

The setup is ready when outside calls follow the intended branches, staff transfers work, records are usable, and a restoration route is known. Keep the settings, test results, and owner together.

The weekly quality guide can support sampling during early operation. Include missed, short, and transferred calls rather than reviewing only completed intake conversations.

Track unexpected voicemail, loops, missing caller identity, and coverage gaps. Those observations support targeted corrections. They do not establish that any provider can offer unlimited capacity or uninterrupted service.

Check existing voicemail and office hours

The original telephone provider may still apply voicemail, holiday schedules, or simultaneous-ring rules before or after forwarding. The implementer should explain the order of those actions for the actual service.

Test an unanswered office call and note which system answers. Then test a busy condition and an after-hours condition. Similar settings can produce different caller experiences, so do not approve the route based only on one successful call.

Include a temporary office closure in the configuration review. Decide who can change the route, which greeting applies, and how the old arrangement is restored. Keep the wording consistent with staff availability so callers do not hear that the office is open when it is using an unstaffed fallback.

Inspect the staff recipient’s experience

A transfer test should include the receiving person, not just the caller. Ask what number appears, whether they understand that it is a transferred inquiry, and how they receive the available intake context.

If staff screen unknown numbers, a technically successful transfer attempt may go unanswered. Resolve that through the firm’s approved phone settings or operating instructions rather than counting every attempt as a connection.

Also test what happens when staff decline or miss the call. The caller should reach the intended next branch instead of an unexpected personal voicemail or a dead end. Confirm the wording and record the observed outcome.

Keep a compact configuration record

Retain the provider, public number, forwarding destination, trigger, staff transfer destination, voicemail interaction, administrator, and restoration steps. Do not include credentials in a general operating document.

Use exact descriptions from the provider’s current interface or support guidance. Telephone settings can change, so a generic instruction copied from another business may be misleading. The authorized administrator should be able to locate the relevant controls without guessing.

Before expanding coverage, repeat only the tests affected by the change. Adding weekend routing warrants weekend checks; changing a staff destination warrants transfer checks. This keeps maintenance practical while still verifying meaningful behavior.

The firm should also know which party supports each part. Its phone provider controls some routing functions, the receptionist provider controls some intake behavior, and the firm owns staffing decisions. A clear support boundary makes faults easier to isolate without promising that any one vendor can control the entire telephone network.

Review changes without touching live callers unnecessarily

Use a planned configuration window where appropriate and agree how the firm will verify the result. A small routing edit can affect the public number immediately, so the administrator should know the intended setting and restoration route before making it.

This does not require a complex release process. It requires a clear owner, the relevant provider instructions, and outside verification calls after the change. Preserve the previous configuration so the firm can explain what was altered.

If the public number is used for several services, review those dependencies. A line used for voice, text, and marketing tracking may have arrangements that are not visible in one phone menu. Ask the authorized administrator to identify them rather than assume every feature follows the voice forwarding rule.

Keep the caller-facing explanation accurate during any transition. Staff should know which route is active and what to say if a caller reports unexpected voicemail or a failed transfer.

Once the configured path passes its relevant checks, avoid repeatedly changing settings without a new reason. Stable coverage and a maintainable record are more valuable than frequent adjustments based on one unusual call. Investigate the actual failure before modifying the whole route.

Keep the final routing record accessible to the authorized administrator so a coverage change does not depend on one person’s memory.

Frequently asked questions

Is forwarding the same as porting?

No. Forwarding routes calls; porting changes the provider controlling the number. Confirm which action is proposed.

Must a firm change its advertised number?

Not necessarily. Evaluate the supported forwarding arrangement with the current phone provider and implementer.

Can AI answer only when staff are busy?

That depends on the provider’s supported routing triggers and configuration. Test the desired conditions.

Does call forwarding include SMS?

Do not assume so. Voice and text routing should be configured and tested separately.

What causes a transfer loop?

One possible cause is transferring back to a number that forwards into the same receptionist route. Test staff destinations explicitly.

Will caller ID always pass through?

Verify the actual arrangement. Do not infer downstream identity behavior from a successful voice connection.

Who should keep the old settings?

The authorized firm owner or administrator should preserve them alongside the restoration process and support contacts.

What should a launch test prove?

Correct routing under each trigger, understandable caller experience, working staff transfers, usable records, and a verified restoration route.

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.