Relationship managers can adopt AI by giving it a bounded role in preparation and documentation, while preserving the customer's choice about capture, the accuracy of the shared record and the firm's authority over financial decisions. Make it possible to correct an error wherever it has travelled, including the next meeting brief. Faster notes are useful only if they remain a faithful basis for the relationship.
This article focuses on client meetings and records in wealth management. It uses a US firm example and a notice addressed to member firms of the Financial Industry Regulatory Authority (FINRA). The requirements for another banking business or jurisdiction need to be established for that particular use. The aim here is a workable adoption process, rather than investment recommendations or a universal recording rule.
Give customers a workable choice about capture
A customer's willingness to talk with a relationship manager does not settle whether an AI service may process the conversation. Before using a meeting tool, establish the firm's approved purpose, handling arrangements and applicable requirements. Explain the actual capture and use in language the customer can understand, with an ordinary route for questions or refusal.
That customer perspective is easy to miss in an internal productivity trial. In a January 2026 discussion about an adviser requesting AI transcription, a Reddit user asked about privacy and security. One reply questioned where the opportunity to review or flag errors appeared. Other participants were more comfortable with the idea. The anonymous discussion does not verify the firm's arrangements or show how common those views are. It identifies a useful customer question: how can I correct the record you are creating about me?
Have a permitted alternative ready when the customer declines capture, the tool is unavailable or the meeting moves outside its approved scope. That might be the firm's established manual note process. Staff should know how to continue the service and record the relevant choice without improvising a different recorder or moving the conversation into an unapproved tool.
Do not promise that the alternative collects nothing or that deleting one recording removes every related record. Those statements depend on the actual process and applicable obligations. The customer and supplier constraints guide explains how to resolve a handling restriction without losing the practical task.
Preserve uncertainty about what the customer intends
Suppose Sam Taylor is a relationship manager in a wealth team. During a review, Alex Morgan mentions that an adult son may buy a home. Alex has not decided whether to help with a deposit. No amount or date has been agreed.
The generated recap says, “Alex will fund the home deposit in June.” That turns a family possibility into an apparent financial commitment. If it becomes a fixed field in the customer record, the next colleague may prepare a meeting around a funding need that Alex never confirmed.
Sam needs to preserve both the subject and the uncertainty. The son is considering a purchase; Alex is considering whether to help. A discussion of a possible need is not an instruction to act. The corrected record should make the open question visible instead of inventing an amount, deadline or course of action.
Keep these permissions and decisions distinct:
| Part of the workflow | What needs to be established | What it does not establish |
|---|---|---|
Capture the meeting | The permitted tool, purpose, handling and required customer choice | Permission for every other use of the information |
Update the shared record | An accurate account of the conversation through the firm's accepted review process | That an inferred intention has become a confirmed customer goal |
Give advice or carry out an action | The requirements and authority for that particular financial service | Authority arising merely because a generated note lists an action |
Use the firm’s established process to clarify material ambiguity with the customer. An assistant's confidence or polished phrasing cannot supply missing instructions. Equally, permission to take notes should not be treated as authority to change a financial profile, recommend a transaction or execute one.
Learn from a firm's workflow without importing its results
Morgan Stanley's June 2024 Debrief announcement describes meeting notes and action items generated with client consent, an email draft for the adviser to edit and send at their discretion, and a note saved into the customer relationship management system, or CRM.
In the same announcement, adviser Zach Goldberg described reviewing, editing and sending a summary while the meeting was still fresh. This is a company-selected employee account, rather than an independent comparison of accuracy, workload or customer trust. The useful detail is the place for review in the actual job. It is not evidence that another firm can remove checking or achieve the same benefit.
The firm's announcement also warns that AI output can be inaccurate, incomplete or biased and should be verified. Treat the linked workflow as a dated company example, not approval for a particular tool or a substitute for your firm's arrangements.
For US FINRA member firms, Regulatory Notice 24-09, published in June 2024, explains that existing obligations continue to apply when using generative AI, including third-party technology. It highlights supervision and public-communication standards and says evaluation depends on the actual business use. The notice creates no new requirements and does not relieve firms of existing obligations. Its scope should not be extended into a worldwide banking rule.
For a different service boundary, the UK banking assistance example shows why an explanation, a recommendation and an account action need separate consideration. A successful note-taking trial cannot settle all three.
Follow a correction into the records people will use
An error can outlive the message in which it first appeared. Correcting Alex's recap is necessary, but it may leave a CRM field, a colleague's task or a future briefing unchanged.
In an October 2026 LinkedIn article, Hany Tadros, who describes his work in AI enablement and governance, warns that an erroneous CRM update can be repeated in later meeting briefs. This is a practitioner's design recommendation, not a measured customer outcome. It gives a concrete reason to examine where a corrected fact has already been copied.
Suppose Alex points out the invented June commitment after receiving the recap. Sam should acknowledge the correction and follow the firm's process to establish the accurate current position. Keep the correction traceable under the firm's access and recordkeeping arrangements, rather than silently rewriting history or assuming every copy will update itself.
One customer clarification can affect three destinations
Alex has not decided whether to help with the deposit. No amount or date is agreed.
Keep the intention uncertain
Check that the current CRM context does not list a June commitment.
Correct the invented commitment
Check that the revised message reflects Alex’s clarification.
Clarify rather than arrange funding
Check the task and the next meeting brief for the same unsupported assumption.
The three destinations in the figure require separate checks. They are not additional permissions to change the customer's finances. In this example, a follow-up task can ask Sam to clarify whether Alex wants another discussion. It should not announce that funding has been arranged or direct a colleague to move money.
Follow one correction through four steps:
- A receiving person. Give the customer a clear way to report a wrong fact, with someone responsible for responding.
- An evidence check. Compare the challenged statement with the permitted source and the customer's clarification. Preserve unresolved disagreement where necessary.
- A record check. Examine the relevant current fields, recap and queued work through their authorised update processes.
- A return check. Confirm that the next permitted meeting brief reflects the corrected position rather than repeating the old claim.
Limit the search for affected records to the people and systems authorised for the task. An error report does not justify giving everyone access to the customer's conversation. The responsible owner should also distinguish correcting a factual record from making a new financial decision, which may require a different process.
Judge adoption by the service and the checking work
A team can generate many meeting notes while still creating extra work for advisers or confusing customers. Test the workflow with permitted representative cases before expanding it. Include uncertain dates, discussion about another family member, conflicting old notes and a customer who declines capture. Establish expected handling with the people responsible for the service.
Look at outcomes the trial can actually observe:
- Whether material facts, speakers and uncertainty survive into the draft.
- What the manager must correct before the record or message can be used.
- Whether a customer correction reaches relevant downstream records and work.
- Whether the ordinary alternative remains usable when capture is declined or unavailable.
- The combined preparation, review, correction and follow-up effort.
Keep first-draft quality distinct from the result after staff repair it. The output-quality guide explains how to preserve that distinction and report consequential failures separately from stylistic edits.
Where appropriate, ask customers about the actual experience:
- Did the recap reflect what they meant?
- Could they correct it?
- Did the next conversation use the correction?
Record who responded and what was asked. Silence, tool usage or a quick follow-up is not evidence of improved trust.
Expand only the particular use supported by the evidence and the firm's approval process. A manager being able to check a meeting recap does not establish that the same system may make recommendations, change customer classifications or act on accounts. Keep that next decision explicit.
Questions about relationship managers using AI
Does agreement to AI meeting notes authorise financial actions?
Agreement to a permitted capture process should not be treated as an instruction to recommend or carry out a financial action. Meeting capture, record updates and financial services have different purposes and requirements. The firm must establish the authority for the actual service. A generated task saying that a customer will fund a deposit cannot replace an instruction the customer never gave.
What should a relationship manager do if a customer declines capture?
Use the firm's permitted alternative and continue the service within its established process. Explain the actual options before capture, handle questions and record the relevant choice appropriately. Do not switch to an unapproved tool to obtain the same recording. Required disclosures, permissions and retention arrangements depend on the firm's business and jurisdiction.
Why review AI notes before they become shared customer context?
An incorrect note can influence later meetings and other colleagues' work even when it cannot execute a transaction. Check material facts, who said what, uncertainty and any supposed instructions against permitted evidence. A customer's comment about a son's possible home purchase should not become a confirmed personal funding commitment. Use the accepted review process before relying on or updating shared records.
How should a customer correction be handled?
Give the customer a clear receiving person, establish the corrected position and inspect relevant downstream records or tasks under the firm's authorised processes. Keep the correction traceable and unresolved disagreement visible. Then check that the next meeting brief reflects the current position. Editing the email alone may leave the original error in the CRM or queued follow-up.
How can a firm assess AI adoption without guessing at customer trust?
Measure observable record quality, required corrections, completed correction handling, service fallback and total staff effort. Collect appropriately scoped customer feedback about accuracy and the ability to correct a recap, with the response context retained. Treat those as bounded observations. Usage counts and staff enthusiasm alone do not demonstrate a customer-trust improvement or justify expanding financial authority.
