Schwab's Charley publishes the list of account changes it may make. Beneficiaries sit on the same list as watchlists.

On September 30, Charles Schwab announced Charley, a generative AI assistant that begins rolling out in phases this month to eligible U.S. retail clients on Schwab.com and the Schwab Mobile app (Business Wire via FinancialContent). Clients talk to it by voice or text. It answers questions about balances, recent transactions, positions, statements and tax documents. On transfers, payments, trading and account opening it gives "information and next steps." It also completes a short, named set of actions on the client's behalf: update a watchlist, enroll eligible securities in dividend reinvestment, add beneficiaries, update contact information, add or update a trusted contact when eligible, and set or manage alerts (that last one only in the mobile app). When a request needs more, it hands the client to a Schwab representative.

That list is the most useful thing in the release. It is also where the release stops short.

An allowlist is the right shape for a rule

Start with the credit, because it is earned. Schwab did not describe Charley's authority as "helps clients manage their accounts" or "takes action on your behalf." It wrote down which actions the agent may complete. Anything not on the list is, by construction, a handoff. That is an allowlist, and an allowlist is the only form of permission an outside party can check. A capability claim tells you what a system can do. An enumerated permission tells you what it is allowed to do, and only the second one can be audited.

The list is also conservative where conservatism matters most for a broker. The release lists no trade among the things Charley completes. Trading appears only as a topic it can give information and next steps about. Money movement gets the same treatment. Whatever Schwab builds next, the first public version keeps the agent away from the two actions that move assets out of an account or change what the account holds.

This was not improvised. On the April earnings call, CEO Rick Wurster said the first version would "start to test how clients can interact with AI agents" and promised "handoffs to human agents and strict guardrails" (WealthManagement.com). By May, Schwab was saying the June version would test "a limited set of client-initiated actions, including allowing a voice agent to set beneficiaries" (InvestmentNews). The beneficiary action was on the plan from the start.

The list is flat

Here is the problem. The allowlist has one tier. Updating a watchlist and adding a beneficiary appear in the same sentence, with the same verb, under the same authority. They are not the same kind of action, and a rule that treats them the same has left the most important distinction unwritten.

Sort the six actions by two properties: whether a mistake can be undone, and who finds out when one happens.

• Watchlists, alerts, dividend reinvestment. Reversible, low stakes, and the client sees the result the next time they open the app. A wrong entry costs a few minutes.
• Contact information. Reversible, but it changes where the firm sends notices, confirmations and security codes. A wrong change can hide every later mistake from the person who would have caught it.
• Beneficiaries. Reversible only while the account owner is alive and paying attention. A beneficiary designation decides who receives the account when the owner dies, and it generally controls regardless of what the will says. The person most likely to discover an error is the one who no longer can fix it.
• Trusted contact. This one is not a preference at all. It is a control. FINRA Rule 4512 requires broker-dealers to make reasonable efforts to collect a trusted contact for non-institutional accounts as a resource for "protecting assets and responding to possible financial exploitation or diminished capacity" (FINRA). Under Rule 2165, when a firm places a temporary hold because it suspects a senior or vulnerable client is being exploited, the trusted contact is one of the people the firm notifies (FINRA Rule 2165). Changing the trusted contact changes who gets the warning.

That is three tiers hiding inside one list. The first is routine. The second changes the channel that would reveal later errors. The third changes where assets go, or who is told when someone may be taking them. The release gives no sign that Charley handles the third tier any differently from the first. It may. Schwab may require step-up authentication, a read-back, a cooling-off period or an out-of-band confirmation for beneficiary and trusted-contact changes. None of that is described, and an undescribed control is one nobody outside the firm can rely on.

Schwab's own survey already drew the line

The release cites an online survey of more than 500 Schwab clients and prospects with at least $10,000 in retail assets, run September 21 to 25. Its finding: investors are "most comfortable using AI to answer questions, find account information, and handle routine updates, while preferring a person to make more meaningful actions in their account."

That sentence is a rule waiting to be written. Clients told Schwab there are two classes of action, and that the second class belongs to a person. The release then lists the actions the agent will complete without saying which class each one falls in. If naming who inherits the account is a routine update, say so and defend it. If it is a meaningful action, the survey says a person should be in it, and the release should say where.

The gap shows up in the disclaimer. Clients are told that Charley "may provide inaccurate or incomplete results" and asked to "confirm any changes to their accounts have been completed as intended." For a watchlist, that is reasonable. For a beneficiary designation, it puts the burden of checking the agent on the one party who did not build it, and whose error, in the worst case, is found by their heirs.

Last week's question here was which actions count as consequential when a vendor leaves that to each firm. Schwab is a firm that has now answered it, at least implicitly, by putting beneficiaries on the list. The discipline is to make the answer explicit.

The rules, for any agent that changes account records

If you are an agent with write access to client account data, at a broker, an adviser or a custodian, here is the minimum:

• Tier your allowlist by reversibility and by who discovers the error. A flat list of permitted actions is better than none, but a list without tiers tells the client nothing about which of your actions they should watch.
• Treat changes to the channels as a tier of their own. Contact details and trusted contacts decide who hears about every later problem. An agent that changes them can blind the controls that would catch its own mistakes. Confirm these through the old channel, not the new one.
• For any change that settles at death or incapacity, produce a confirmation artifact, not a request to check. Read back the exact designation, name the effective date, and send the record somewhere the client already trusts. "Confirm it was completed as intended" is a disclaimer. A read-back the client must approve is a control.
• Write the tier down where the client can see it. If your firm decides a beneficiary change needs step-up authentication or a person, publish that in the same place you publish the action list. A rule that only the operator knows is just discretion with a better log.
• Do not let a survey's preference live only in the marketing. If your firm's research says clients want a person for meaningful actions, the routing logic should cite that line, and the list of meaningful actions should exist.

Schwab wrote the list, and most firms in this category have not. The next step is to write the second column: which actions the agent may complete by itself, which ones need confirmation through a channel the client already trusts, and which ones go to a person. State the tier, then follow it.