What should an RIA record when a client complaint reaches the wrong person?

When a client complaint reaches the wrong person, preserve the concern accurately, identify the appropriate owner and record whether the handoff was received. Do not let a forwarded message look like a completed response. The first record should distinguish what the client said, what the recipient knows and what still needs review.

This is operational guidance, not legal or compliance advice and not advice about any particular firm's obligations. It supplies no rule interpretation, retention period or mandatory response timetable. The firm's qualified reviewers handle those questions separately.

What should the first recipient record?

Start with what arrived, how it arrived and what the client is asking to have reviewed. Keep observations separate from conclusions.

In a fictional example, a client says a recent explanation was unclear and asks someone to look at it. The recipient records that concern rather than rewriting it as a confirmed mistake. A short record can preserve the issue without judging it prematurely.

Use the client's actual wording where the firm's approved process permits it. If you summarize, label the summary and keep the appropriate reference to the original. Do not add a motive, diagnosis or emotional description that the person did not supply.

The record belongs in the firm's appropriate system with access suited to the information. A public worksheet or ordinary content-planning file is not the place for real client details. All examples in this guide are fictional.

How do you separate the concern from the interpretation?

Give the concern, known facts and open questions different fields. That prevents a plausible explanation from becoming the record's version of events.

"The client says the statement was unclear" is a concern. "The first recipient has not reviewed the underlying exchange" is a known limit. "Which explanation is being referenced?" is an open question. None is a conclusion about what happened.

Do not fill a missing date, document or person from memory. Mark it unknown and identify who can check it. A clean-looking record with guessed facts is harder to use than an honest record with a visible gap.

The Parliamentary and Health Service Ombudsman's complaint-handling principles discuss clear roles and a fair approach in their own public-body setting. This article borrows the organizing idea only. Those principles are not presented as rules for US advisory firms.

Who should own the next step?

Use the firm's actual routing process to identify the person responsible for review. The first recipient should not invent a role or promise that an unconfirmed person will act.

If the owner is unknown, record that as an unresolved routing issue. Find the appropriate internal contact without spreading the complaint to a wide audience. A message sent to several people can leave everyone assuming somebody else owns it.

Record whether the receiving person accepted the handoff. Sending a message establishes only that it was sent. It does not show that the concern was read, assigned or resolved.

A fictional handoff might say, "This concern is awaiting review by the designated owner; receipt has not yet been confirmed." That is not final client-facing wording. It is an internal state that tells the team what remains open.

What should an acknowledgment avoid?

An acknowledgment can recognize that a concern was received without deciding its merits or promising a remedy. Use the firm's reviewed wording and actual authority.

A recipient who has not checked the facts should not say an error has been proved. Someone without authority to decide an outcome should not promise reimbursement, a policy exception or a particular result. Nor should the person dismiss the concern merely because it came through the wrong channel.

The Ombudsman's guide to clarifying a complaint stresses understanding the concern and the outcome sought in its NHS context. The general communication lesson is to establish what the person wants reviewed, not to assume it. This is context, not an imported requirement.

Keep any requested outcome separate from an agreed outcome. "The client asks for an explanation" and "the firm has supplied an explanation" should not occupy the same completed field.

What does the receipt-and-routing worksheet contain?

The worksheet should show enough for an authorized reviewer to find the concern, understand the handoff and see the gaps. It should not turn into a second uncontrolled copy of the client file.

This is an original organizing aid, not a regulatory template. It does not establish that the firm's process satisfies any legal or compliance duty. Qualified reviewers should assess the real process separately.

How much information should move with the handoff?

Give the appropriate owner the information needed to understand the concern through the firm's reviewed channel. Do not send more private material merely to make the message feel complete.

Identify the record rather than attaching a full client history by default. Check the actual recipient and access scope. If the correct channel or audience is unclear, keep that gap visible and ask the responsible person to settle it before disclosure.

A forward to a personal address, broad group or unfamiliar account is not a harmless substitute for an internal handoff. The operational choice of channel deserves review because another person receives the information.

This guide does not specify the firm's security architecture. It asks the recipient to avoid treating convenience as proof that a disclosure is appropriate.

What if the concern changes during the handoff?

Keep the original concern and the later clarification distinguishable. A new detail should not silently overwrite the reason the record was opened.

In a fictional example, the client first asks for an explanation and later identifies a different document. The owner can record the clarification and check whether it changes the review. That does not mean the original record was wrong or that every earlier statement should disappear.

If a different person becomes responsible, record the new handoff and its receipt. Do not leave the old and new owner fields looking equally current. The useful question is who has the next step now, with what information and what remains unresolved.

When the responsible reviewer records a conclusion, distinguish that conclusion from the client's requested outcome and any further question. A record marked complete should not conceal a still-unconfirmed delivery or another open concern. This is a way to make work inspectable, not a definition of legal closure.

How should the process be tested?

Use a harmless fictional concern and synthetic records. Test whether someone can find the owner without relying on the usual recipient being present.

Try an unclear reference, an unavailable contact and a missing acknowledgment. Can the reviewer see each gap? Does an unresolved handoff remain open? The test is about operational clarity, not proving that every possible complaint will be handled correctly.

The service-calendar worksheet addresses named responsibility for ordinary work. The prospect-information guide addresses staged information requests. This guide has a narrower purpose: preserving and routing a concern that arrived at the wrong person.

The first recipient does not need to settle the complaint to make the next step clearer. A useful record keeps the concern intact, the owner explicit and the unresolved work visible.