The 2024 client portal was a static window into the household's account balances and a download link for the quarterly statement. The 2026 AI-augmented client portal is an active interface — answering questions, routing to the advisor, surfacing AI-extracted insights from the client's planning data, and operating 24/7. The challenge is not building the portal; eMoney, RightCapital, MoneyGuidePro, Wealthbox, Salesforce FSC, Redtail Engage, and several vertical SaaS providers ship credible portal AI capabilities by mid-2026. The challenge is the disclosure architecture that holds the experience together — what clients see, what they don't, when AI answers, when it routes to the advisor, and the FINRA Rule 2210 + Marketing Rule 206(4)-1 + Reg BI §240.15l-1 supervisory architecture that keeps the whole thing compliant. This lesson installs the design framework and the supervisory architecture.

What Clients See, What They Don't

The portal's design decisions determine what the client experiences as the firm's "AI service." Three categories.

Visible AI Features

Conversational interface that answers client questions about their accounts ("what's my Roth contribution room?", "when is my next RMD?", "how is my retirement plan tracking?"); AI-extracted insights from the client's planning data (RightCapital, eMoney, MoneyGuidePro projections); next-best-action prompts ("you may want to schedule a tax-loss harvesting review"); document summary on demand (1040 summary, trust summary, statement summary); educational content personalized to the household's planning context. Each visible AI feature is labeled "AI-assisted" or similar per L5 Ch3 L3 disclosure framework's per-output labels.

Invisible AI Features (Advisor-Facing Only)

Pattern detection on transaction histories that surfaces unusual activity to the advisor (not to the client until advisor triages); next-best-action prompts for the advisor about the client (not exposed to client until advisor acts); AI-summarized meeting notes that feed advisor preparation (client sees the post-meeting recap, not the prep brief); compliance review flagging that surfaces to principal under Rule 2210. These features run on the household's data without client-facing visibility because the AI's role is to support the advisor's work product, not to engage the client directly.

What Clients Explicitly Do Not See

Internal supervisory metrics (principal-review queue exception logs, AI Risk Register entries); cross-household pattern mining (without opt-in per L5 Ch3 L3); firm-internal compliance work product; firm-internal training material. The boundary is enforced at the data-access layer per L5 Ch3 L2 data governance — the portal's AI does not query firm-internal RAG vault content beyond what the household's engagement letter and ADV Part 2A AI disclosure cover.

When AI Answers, When It Routes to the Advisor

The routing logic is the most operationally consequential design decision in the portal.

AI Answers — Low-Stakes Factual

"What's my account balance?", "when is my next RMD?" (under IRC 401(a)(9), pulled from custodian feed with Cardinal Rule L1 Ch2.3 source-system verification), "what's my Roth contribution limit this year?" (2026 IRS limits applied to household's age + income), "where can I find my 1099?" (links to custodian portal). Cardinal Rule L1 Ch2.3 verification applies — source-system data with disclaimed "AI-assisted" labels per L5 Ch3 L3 per-output labels.

AI Routes — Recommendation or Judgment Required

"Should I do a Roth conversion this year?", "is my retirement plan on track?", "should I take this RSU exercise?" — any question implicating Reg BI §240.15l-1 Care Obligation or fiduciary duty under the Advisers Act of 1940. The AI routes: "Great question — let me connect you with [advisor name]. In the meantime, here's some general background on Roth conversion considerations." The routing message references the L1 Ch1 framing: AI cannot exercise professional judgment under CFP Code or Reg BI Care Obligation; the registered, licensed advisor owns the recommendation.

AI Routes — Emotional or Difficult Conversation

"I'm worried about the market drop", "I'm thinking about divorce" — emotional content routes to the advisor with appropriate empathy preamble. The L5 Ch7 L1 drawdown coaching protocol pulls each household's eMoney/RightCapital/MoneyGuidePro Monte Carlo position and generates the advisor's prepared response; the AI does not deliver the drawdown coaching directly.

AI Routes — Compliance-Sensitive

"Can I have my friend trade in my account?" (POA / authorization), "I want to change my beneficiary" (legally significant — opt-in agentic per L5 Ch3 L3 may be allowed, with explicit per-update confirmation), "I think there's been fraud" (immediate routing + L4 Ch3 L4 incident response if Reg S-P 17 CFR Part 248 NPI compromise). These route to advisor + may trigger Section 6 IRP of L5 Ch3 L1 policy.

Integration With eMoney, RightCapital, MoneyGuidePro Client Portals

The major planning platforms each ship their own client-portal AI capabilities by 2026; the firm's design decision is whether to use the platform-native portal (lower switching cost, faster deployment, vendor maintains the AI updates) or build a custom layer (more control, brand consistency, prompt-library integration with the firm's own prompts). The 2026 winning pattern at mid-sized RIA scale is to use platform-native portal AI with firm-specific configuration — prompt library elements that match the firm's L5 Ch2 L1 proprietary workflows are injected into the platform's AI context where the vendor permits; the firm's branding overlays where the vendor permits; the substantiation file per L4 Ch7 L1 captures the vendor's AI capability descriptions and the firm's specific configuration.

Custom layer is rare at mid-sized RIA scale (more common at aggregators with $5B+ scale + L5 Ch2 L1 proprietary infrastructure already deployed). The custom layer uses the firm's enterprise LLM (Microsoft Copilot, OpenAI Enterprise, Google Gemini Enterprise) plus RAG vault per L5 Ch2 L1 three-layer architecture; the planning platform feeds household-specific data via the L5 Ch3 L2 mesh interface; the custom portal builds on top.

The Supervisory Architecture That Keeps It Compliant

FINRA Rule 2210 Principal Review

The portal's AI outputs to clients are communications under FINRA Rule 2210; the principal-review queue per L4 Ch3 L2 covers AI-drafted content with risk-based sampling — higher sampling for new prompt versions in their first 30 days, AI-to-AI red-team first-pass screening with exception routing to registered principal. The portal AI's high volume (potentially hundreds of interactions per day at a 200-advisor firm) makes the risk-based sampling architecture essential — 100% review is operationally infeasible; risk-based + AI red-team produces the supervisory adequacy.

SEC Marketing Rule 206(4)-1

Every portal AI output is a marketing communication subject to Rule 206(4)-1's "clear and prominent" disclosure standard + January 2026 SEC staff FAQs framework + 2024-2025 Delphia/Global Predictions AI-washing precedent. The L4 Ch7 L1 substantiation file per L5 Ch4 L1 AI Compliance Specialist maintenance covers any claim the portal AI makes externally; the per-output labels per L5 Ch3 L3 framework satisfy "clear and prominent." Performance claims, third-party-rating mechanics, hypothetical scenarios, testimonials — all subject to specific Rule 206(4)-1 provisions.

Reg BI §240.15l-1

The portal AI does not make recommendations under Reg BI — the routing architecture sends any recommendation question to the advisor. But the portal AI's content may influence client decisions; the Care Obligation §240.15l-1(a)(2)(ii) implications require the portal to (a) clearly identify content as AI-assisted, (b) route recommendations to advisor, (c) not present scenarios as personalized recommendations without advisor signoff, (d) integrate with the advisor's Reg BI documentation when escalation occurs.

FINRA Rule 4511 + SEC Rule 204-2 Retention

Every portal interaction is retained per FINRA Rule 4511 + SEC Rule 204-2: client question + AI response + any routing decision + advisor signoff if escalated. Smarsh or Global Relay holds the immutable retention layer per L5 Ch3 L2 data architecture. The retention includes the prompt + retrieved context + LLM response + edits + signoff chain per L5 Ch4 L1 Prompt Librarian's library standards.

Reg S-P 17 CFR Part 248

The portal accesses Class 4 NPI per L5 Ch3 L2 data classification — household account data, transaction history, planning data. Consent enforcement at the data-access layer per L5 Ch3 L2 mesh interface ensures the portal AI only queries household data with engagement-letter and ADV Part 2A AI disclosure coverage. Reg S-P incident response per Section 6 of L5 Ch3 L1 policy + L4 Ch3 L4 IRP framework + May 2024 amendments' 30-day notification clock + NY DFS 23 NYCRR 500 72-hour notification if NY-resident affected.

Agentic Portal Features — The 2027-2028 Trajectory

The 2026 baseline limits portal AI to drafting + routing — not action-taking. The 2027-2028 trajectory per L5 Ch3 L3 + L5 Ch6 L1 expands to client-initiated agentic actions opt-in by category:

• Beneficiary update: client-initiated change via portal triggers AI draft, advisor review, electronic signature, custodian processing — agentic per L4 Ch3 L3 WSP with kill-switch + post-action review.
• Rebalancing request: client-initiated portfolio review via portal triggers AI assessment against IPS, advisor review, agentic execution if within IPS bounds.
• RMD election: client-initiated RMD distribution amount or destination preference via portal triggers AI calculation per IRC 401(a)(9) + Cardinal Rule L1 Ch2.3 source-system verification + advisor review + agentic processing.
• ACATs initiation: client-initiated transfer request via portal triggers AI validation + advisor review + agentic ACATs submission.

Each agentic portal feature requires opt-in per L5 Ch3 L3 + L4 Ch3 L3 agentic-AI WSP framework + Rule 4511 agent action log retention + kill-switch + post-action review queue under Rule 2210 + Reg BI Care Obligation documentation if recommendation-influencing.

The Portal Disclosure Language Template

The firm's portal disclosure language sits in three places: the portal's standing "About AI in This Portal" landing page (always accessible from the footer); the per-output label that accompanies every AI-generated response; and the engagement letter addendum the client signs at portal activation. The template language refined across the L5 Ch3 L3 disclosure framework and the L4 Ch7 L1 Marketing Rule audit:

Standing "About AI" page: "This portal uses artificial intelligence to help you find information about your accounts, answer common questions, and surface insights from your planning data. The AI is a tool we use to make your experience faster and more useful — it is not your advisor and it does not replace the relationship you have with [Advisor Name]. The AI's responses are drafted by software trained on financial information and your household's own planning data, and reviewed under our written compliance procedures. The AI cannot provide personalized investment advice or recommendations; any question that involves a judgment about what is right for your specific situation will route to your advisor. Every conversation in this portal is recorded and retained under SEC and FINRA recordkeeping rules. Your data is protected under our written privacy policies and our agreements with software vendors; we do not share your information with public AI services. You can request a human-only experience at any time by updating your portal preferences. For details about how we use AI, see our Form ADV Part 2A on our website."

Per-output label on each AI response: "AI-assisted response. Generated [timestamp]. Source data: your accounts as of [date], your planning data as of [date]. For questions about your specific situation, contact your advisor [Advisor Name] at [direct line]."

Engagement letter addendum (signed at portal activation): "Client acknowledges that the Firm's client portal includes artificial intelligence features that may draft responses to questions, summarize documents, and surface planning insights. Client understands that AI-generated content is reviewed under the Firm's written supervisory procedures consistent with FINRA Rule 2210 and the SEC Marketing Rule, that AI does not provide investment recommendations or fiduciary advice, that recommendation-related questions route to the Firm's registered advisor, and that all portal interactions are retained under SEC Rule 204-2 and FINRA Rule 4511. Client consents to the Firm's use of AI features as described in the Firm's Form ADV Part 2A and the portal's standing disclosures, and may opt out of AI features at any time by request."

The AI-to-Human Routing Logic — Implementation Detail

The routing classifier sits between the user's question and the AI response. Each inbound question is scored across five dimensions: (1) Recommendation-likelihood — does the question implicate a specific decision the client might take? Trained on the firm's historical client-question corpus with labels. Scores 0.0-1.0; above 0.6 routes to advisor. (2) Compliance-sensitivity — does the question touch beneficiary, POA, fraud, complaint, or other Reg S-P / Reg BI / Marketing Rule territory? Rule-based on keyword and pattern matching plus LLM classifier; positive flags route immediately. (3) Emotional valence — does the question carry markers of distress, anger, fear, or crisis? Sentiment classifier; negative valence above threshold routes with empathy preamble. (4) Complexity — does the question require multi-step reasoning, multi-account synthesis, or judgment about household-specific facts the AI does not have? LLM classifier; high complexity routes. (5) Account-action implication — would answering the question naturally lead to a transaction the firm should supervise? Rule-based on intent recognition; positive routes.

A question scoring high on any single dimension routes to the advisor. A question scoring low on all five — "what's my Roth contribution room?" "when is my next RMD?" "where do I find my 1099?" — is answered by the AI with the per-output label. The classifier itself is reviewed quarterly by the AI Compliance Specialist for accuracy drift; misroutes in either direction (AI answered when it should have routed, or routed when it could have answered) are logged and fed back into the classifier training. The L4 Ch3 L2 dual-sampling protocol applies — both routed and AI-answered questions are sampled by the principal reviewer for false-negative validation.

The Rule 2210 Review Queue Architecture for Portal Content

The portal's AI generates substantially more communications per day than the advisor pod's outbound work. A 110-advisor firm with 65% portal-active households (per the case study) may generate 800-1,500 AI responses per business day plus weekend volume. The Rule 2210 principal review queue cannot scale linearly. The architecture: Tier A — pre-publication review applies to new prompt versions for their first 30 days of production use; every AI response generated from a new prompt is principal-reviewed before delivery during the validation period. Tier B — risk-based sampling applies after the validation period; AI responses are tagged with a risk score (based on the same five dimensions as the routing classifier), and the principal reviewer samples at rates ranging from 25% for high-risk content (any response containing planning data or quantitative figures) to 2% for low-risk content (account location, contact info, generic FAQ-style responses). Tier C — exception review applies to any AI response flagged by the AI-to-AI red-team layer; these route to immediate principal review before delivery. Tier D — dual-sampling validation per L4 Ch3 L2 samples both Tier-B-cleared content (false-negative validation) and Tier-C-flagged content that was approved (false-positive validation) at a 5-8% rate.

The principal reviewer's daily portal-queue workload at the $6B case-study firm settles at approximately 2-3 hours per day distributed across two or three reviewers. The supervisory log per Rule 4511 captures every response, sample selection, and disposition. The AI Compliance Specialist runs a monthly queue audit and reports to the L4 Ch6 L1 governance committee on classifier accuracy, false-positive rate, false-negative rate, and exception trends. The quarterly external audit per L4 Ch7 L1 reviews the portal queue's regulatory adequacy.

Integration Depth With eMoney, RightCapital, and MoneyGuidePro

Each major planning platform's 2026 portal AI integration has different depth and capability boundaries that the firm's design decision must navigate. eMoney advisor-portal integration in 2026 offers the deepest household-data context — the portal AI can answer questions about the household's full plan, projections, scenarios, and document vault, with API hooks for the firm to inject custom prompt-library elements via the eMoney Connect Studio. The integration supports firm-specific branding overlay, custom routing logic via webhooks to the firm's principal-review queue, and Smarsh / Global Relay archive export. The 2026 limitation: agentic features (client-initiated actions) are roadmapped for late 2026 with limited beta. RightCapital client portal AI integration in 2026 emphasizes planning insights — the portal AI surfaces planning-driven next-best-actions based on the household's RightCapital plan, with strong integration to tax-planning insights (RightCapital's tax-projection engine). Firm-specific configuration is more limited than eMoney's; the prompt-injection capability is at the planning-narrative level rather than the response level. Archive export to Smarsh is supported. MoneyGuidePro portal AI in 2026 sits between the two on configurability — strong on plan-based insights, less customizable on routing logic, with the SunGard/Envestnet integration ecosystem extending capability. Firm-specific configuration via Envestnet's APIs is accessible but requires more engineering investment.

The firm's selection depends on the existing planning-platform commitment (changing planning platforms to optimize portal AI is rarely justified), the firm's customization appetite, and the agentic-feature roadmap timing. The L5 Ch6 L1 trajectory anticipates convergence by 2027-2028; the 2026 decision is operational rather than strategic.

Case Study — $6B RIA Portal Rollout

A $6B RIA with 110 advisors rolled out an AI-augmented client portal in Q4 2025 - Q2 2026. Platform decision: eMoney native portal AI + firm-specific configuration (prompt library injection for the firm's L5 Ch2 L1 proprietary business-owner-exit workflow + ADV Part 2A AI disclosure aligned + L5 Ch3 L3 disclosure framework per-output labels). Rollout: 90 days drafting + outside counsel review + AI Compliance Specialist setup; 60 days advisor training on routing patterns + meeting introduction script integration; 30 days client communication + engagement letter refresh + portal opt-in flow setup; 30 days phased deployment (alpha cohort of 20 households, then 200, then full); total 6 months.

Q3 2026 outcomes: 65% of active households used portal at least once monthly; portal AI handled 78% of low-stakes factual questions without escalation; 22% routed to advisor (the routing-required category); 0.6% triggered compliance escalation (4 incidents handled within IRP); principal-review queue rejection rate stable at 4-6% on AI-drafted content (within target); zero Reg S-P 17 CFR Part 248 incidents related to portal; outside counsel confirmed Rule 2210 + Marketing Rule 206(4)-1 + Reg BI §240.15l-1 alignment; L4 Ch8 L1 supervisory-architecture score 8/10 → 9/10. The portal became the firm's competitive differentiator at acquisition pitches and a documented contributor to the L4 Ch5 L2 ROI dashboard's hours-recovered + close-rate metrics.

Key Takeaways

• What clients see is a deliberate design decision: visible AI features (conversational interface, planning-data insights, next-best-action, document summaries, personalized education) with L5 Ch3 L3 per-output labels; invisible advisor-facing features (pattern detection, prep briefs, compliance flagging under Rule 2210); explicitly excluded from client view (supervisory metrics, cross-household mining, firm-internal compliance work).
• Routing logic is operationally consequential: AI answers low-stakes factual (account balance, RMD date with Cardinal Rule L1 Ch2.3 verification, contribution limits); routes to advisor on recommendation or judgment (Reg BI §240.15l-1 Care Obligation territory + L1 Ch1 framing on fiduciary), emotional content, compliance-sensitive (POA, beneficiary, fraud — Reg S-P 17 CFR Part 248 + Section 6 IRP).
• 2026 winning portal architecture at mid-sized RIA scale is platform-native (eMoney, RightCapital, MoneyGuidePro client portals with firm-specific configuration); custom layer common at $5B+ aggregator scale using L5 Ch2 L1 three-layer architecture (enterprise LLM + RAG vault + prompt library) with planning platform data via L5 Ch3 L2 mesh.
• Supervisory architecture spans FINRA Rule 2210 principal review + Marketing Rule 206(4)-1 substantiation + Reg BI §240.15l-1 routing + Rule 4511 + SEC Rule 204-2 retention via Smarsh or Global Relay + Reg S-P 17 CFR Part 248 consent enforcement. Risk-based sampling per L4 Ch3 L2 with AI-to-AI red-team first-pass is essential at portal-AI volume; 100% review operationally infeasible at scale.
• Agentic portal features are 2027-2028 trajectory per L5 Ch3 L3 + L5 Ch6 L1: beneficiary update + rebalancing request + RMD election + ACATs initiation each opt-in by category with L4 Ch3 L3 agentic-AI WSP + Rule 4511 agent action log + kill-switch + post-action review + Reg BI Care documentation when recommendation-influencing.
• $6B RIA case study: 110 advisors, eMoney native portal + firm-specific configuration, 6-month rollout. Q3 2026: 65% household monthly use, 78% low-stakes handled without escalation, 22% routed to advisor, 0.6% compliance escalation handled within IRP, principal-review queue 4-6% rejection on AI-drafted content, zero Reg S-P incidents, L4 Ch8 L1 supervisory score 8/10 → 9/10. Portal became firm's competitive differentiator at acquisition pitches.