/next-best-action

name: next-best-action
description: "Design and implement next-best-action engines that surface proactive, prioritized recommendations to advisors based on portfolio, life, market, and compliance events. Use when the user asks about building event-driven advisor alerts, designing trigger logic for portfolio drift or large cash movements, prioritizing competing actions across a book of business, routing NBA recommendations to the right team member, measuring NBA acceptance rates, or automating compliance-driven actions like annual review reminders. Also trigger when users mention 'next best action', 'advisor nudges', 'proactive outreach', 'what should I do for this client', 'event-driven triggers', 'action queue', 'client contact gap', 'RMD reminder', or 'advisor productivity tool'."

Next-Best-Action — Event-Driven Advisor Recommendations

Core Concepts

Next-Best-Action Framework

Next-best-action is an advisor productivity and client service methodology that analyzes client data across systems to surface the single most valuable action an advisor should take for each client at any given time. The concept originates in CRM and marketing automation — industries that have long used event-driven recommendation engines to guide customer-facing personnel toward high-value interactions — but its application in wealth management addresses a distinct set of challenges: advisors managing hundreds of client relationships cannot manually monitor every portfolio, life event, compliance deadline, and practice touchpoint across their entire book of business.

NBA differs fundamentally from traditional task management. Traditional task management is reactive and manual: advisors create their own to-do lists, respond to inbound client requests, and rely on memory or periodic reviews to identify outreach opportunities. NBA is proactive and data-driven: the system continuously monitors client data across custodial feeds, CRM records, financial plans, compliance calendars, and market data, automatically identifying situations that warrant advisor attention and recommending specific actions with supporting context.

The core components of an NBA system are:

• **Event detection** — Continuous monitoring of data sources to identify triggering events (portfolio drift, large cash movement, life milestone, compliance deadline, market dislocation).
• **Action identification** — Mapping detected events to a catalog of recommended actions (schedule review, propose rebalancing, discuss tax-loss harvesting, update beneficiaries).
• **Prioritization** — Scoring and ranking competing actions across all clients to ensure advisors focus on the highest-value activities given limited time.
• **Routing** — Directing each action to the appropriate person based on role, expertise, relationship, and availability.
• **Delivery** — Presenting recommendations through the channels advisors actually use (dashboard, mobile notification, email digest, CRM task).
• **Tracking** — Recording action outcomes (accepted, deferred, rejected, completed) to close the feedback loop and improve future recommendations.

Event Detection and Trigger Types

The quality of an NBA system depends on the breadth and reliability of its event detection. Events fall into five categories, each requiring different data sources and detection logic.

**Portfolio events** are detected from custodial data feeds, portfolio management systems, and market data:

• Drift beyond threshold — A client's actual allocation has deviated from the target model beyond the firm's tolerance band (e.g., equity allocation at 72% vs. 65% target with a 5% tolerance). Requires real-time or daily position data and model assignment.
• Large cash deposit or withdrawal — A significant cash movement (typically defined by absolute amount or percentage of portfolio) has occurred. Detected from custodial transaction feeds. A $200,000 deposit into a $1 million account signals an investment opportunity; a $200,000 withdrawal from the same account may signal a liquidity event requiring plan reassessment.
• Concentrated position — A single holding has grown to exceed a concentration threshold (e.g., 10% or 15% of portfolio value), whether through appreciation, additional purchases, or stock compensation vesting. Detected from position-level holdings data.
• Tax-loss harvesting opportunity — Unrealized losses in taxable accounts exceed a significance threshold, particularly near year-end or after market declines. Requires lot-level cost basis data and market prices.
• Required minimum distribution (RMD) due — A client with a traditional IRA or inherited IRA is approaching or has reached an RMD deadline. Requires account type data and client date of birth. RMD deadlines are absolute (December 31 for most, April 1 of the following year for the year the owner turns 73).
• Margin call — A client's margin account has breached maintenance requirements. Requires margin balance and equity data from the custodian. Margin calls are time-sensitive and typically require same-day or next-day resolution.

**Life events** are detected from CRM data, client-reported information, and public records:

• Birthday milestones — Age-based financial triggers: 59-1/2 (penalty-free IRA withdrawals), 62 (early Social Security eligibility), 65 (Medicare eligibility), 70-1/2 (qualified charitable distributions from IRAs), 73 (RMD beginning age under SECURE 2.0 for those born 1951-1959). Detected from client date of birth in CRM.
• Marriage, divorce, death of spouse — Major life transitions requiring comprehensive financial plan review, beneficiary updates, account re-titling, and potentially revised investment strategy. Typically detected through advisor-reported CRM updates or client-initiated contact.
• New child or grandchild — Triggers discussions about education savings (529 plans), life insurance review, estate plan updates, and beneficiary designation changes.
• Job change or retirement — Inco