The Client

A Growing US Asset Manager — With Advisor Data Sitting Idle in Salesforce

AMF
US Asset Management Firm (name withheld by agreement)
Identity confidential · Full Salesforce NBA Engagement
IndustryAsset Management · Wealth Advisory
RegionUnited States — Northeast corridor, 4 offices (NYC, Boston, Chicago, Atlanta)
Team Size180+ licensed advisors and relationship managers
Volume~2,400 active advisor-client relationships managed in Salesforce
Stack BeforeSalesforce Sales Cloud (underused) + shared Outlook calendars + Excel tracking sheets
EngagementSalesforce NBA Implementation · 12 weeks · 5 phases

By the time they engaged us, this firm had been on Salesforce Sales Cloud for over two years — but the platform was functioning as little more than an expensive contacts database. Advisors were logging calls inconsistently, opportunity stages weren't reflecting actual pipeline health, and the decision of when to contact a client was still being made by gut feel and spreadsheet reminders. Senior advisors had good instincts. Junior advisors were guessing.

The firm's head of advisor operations had heard about Salesforce Next Best Action from a peer at a competitor firm but didn't know where to start. Their internal Salesforce admin was capable but had never built NBA strategy rules at this scale. The original vendor who implemented their Sales Cloud instance was no longer engaged. They needed a team that had done this before — across financial services orgs — and could move fast without breaking the data model they already had.


The Problem

Four Operational Gaps That Were Costing Real Advisor Performance

After a two-week discovery process — which included listening calls with 12 advisors across three offices — we identified four systemic problems that weren't process failures. They were system failures that the current Salesforce setup was incapable of solving without NBA.

01

No Signal for When to Contact a Client

Advisors were manually reviewing their book of business each morning to decide who needed a touchpoint. For a book of 80–120 accounts, this took 45–60 minutes of productive time daily — and still missed clients who had gone 30+ days without contact. Three of the firm's largest client losses in the prior year were traced back to engagement gaps the advisor didn't catch until it was too late.

02

Follow-Up Decisions Were Person-Dependent, Not System-Driven

The top 20% of advisors had developed personal systems — colour-coded spreadsheets, calendar blocks, reminder sequences. The bottom 60% had none. This meant advisor performance variance of over 3× between the top quartile and average, with no structural way to close the gap. Senior advisors were being asked to coach junior peers on processes that lived in their heads, not in Salesforce.

03

Email Templates Existed — But Were Almost Never Used

The marketing team had built 14 Salesforce email templates for advisor outreach. Usage data showed fewer than 3 of those templates had been sent in the prior 90 days. Advisors weren't finding the templates, weren't selecting the right one for context, and were defaulting to personal Gmail accounts — creating compliance gaps and breaking email attribution entirely.

04

Opportunity Stalls Were Invisible Until Deals Went Cold

Opportunities sitting in the same stage for 14+ days weren't being flagged. There was no alert, no nudge, no action surfaced to the advisor. 43% of closed-lost opportunities in the prior two quarters had stalled in Negotiation or Proposal Sent for over 21 days before anyone noticed. A system that could identify a stall and recommend an action would have caught most of them.


The Solution

How We Structured the Engagement

We've implemented Salesforce Next Best Action across financial services, healthcare, and SaaS orgs — and the failure pattern is always the same: teams try to build NBA without first defining the decision logic that should drive it. We refused to write a single Flow rule until we'd mapped every advisor-to-client interaction pattern and gotten business sign-off on which signals should trigger which actions. That groundwork is what separates NBA deployments that advisors actually use from ones they ignore after week three.

The engagement ran across five structured phases — from data audit to live deployment with role-based training. We built 11 distinct NBA strategy rules covering engagements on both the Contact and Opportunity objects, with full Accept/Reject/Snooze mechanics, automated email triggering, rejection reason capture, and a 7-day snooze cycle.

Five Phases · 12-Week Delivery
Each phase was validated before advancing — no forced cutover, no overnight switch.
Phase 01 — Discovery & Workflow Audit Phase 02 — Data Mapping & Object Audit Phase 03 — NBA Strategy Build Phase 04 — Advisor Detail View Deployment Phase 05 — Training, Adoption & Handoff
Phase 01

Discovery — Mapping the Real Advisor Workflow

Salesforce Next Best Action runs on strategy rules — and bad strategy rules are worse than no rules at all. If the first actions an advisor sees are irrelevant, they'll dismiss the component and never look at it again. The first two weeks were entirely about understanding how this firm's top-performing advisors actually make contact decisions.

We ran structured listening sessions with 12 advisors across all four offices, and a separate session with the compliance lead and operations head. From those sessions, we built a decision logic map: 11 advisor actions, ranked by business priority, each with defined triggers. This document became the authoritative source for every NBA strategy rule in Phase 03.

Mapping the Real Advisor Workflow — discovery phase
Workflow mapping · Discovery Phase
🎙️
12 Advisor Listening Sessions
Structured interviews across 4 US offices, capturing real decision triggers not documented anywhere in the existing system.
🗂️
Decision Logic Map Delivered
11 prioritised advisor actions, each with defined trigger conditions, action types, and compliance check flags.
Business Sign-Off Before Build
Operations head, compliance lead, and 2 senior advisors signed off on the logic map before a single Flow rule was written.
Phase 02
Phase 02

Data Readiness & Salesforce Object Mapping

NBA recommendations are only as useful as the data feeding them. We ran a full audit of the client's Salesforce org: field population rates on Contact and Opportunity records, activity log completeness, ownership mapping between advisors and accounts, and the state of their AUM and engagement score fields — which turned out to be largely empty.

We mapped every NBA trigger field to the correct Salesforce object, confirmed the Activity Timeline was capturing data reliably, and identified three custom fields that needed to be built to support the strategy logic from Phase 01. We also audited the 14 email templates, retired six that were outdated, and restructured the remaining eight so they could be auto-opened by an Accept action in the NBA flow.

Data Readiness & Salesforce Object Mapping
Data Readiness & Salesforce Object Mapping
📊
Field Population Audit
Measured completeness rates on 22 fields across Contact and Opportunity — identified 7 fields below 60% fill rate that would break NBA trigger logic.
🔧
3 Custom Fields Built
Last Meaningful Engagement Date, AUM Tier, and Engagement Score fields added to Contact and Opportunity objects to support strategy rules.
📧
Email Template Restructure
8 usable templates restructured for NBA compatibility — now auto-load in Lightning email composer when advisor accepts an Email action type.
Phase 03
Phase 03

NBA Strategy Build — Flow Rules, Actions & Accept/Reject/Snooze Logic

We used Salesforce Flow to create 11 strategy rules, each mapped to the decision logic from Phase 01. Each rule evaluates a set of field conditions — last contact date, opportunity stage, AUM tier, days since last activity — and when triggered, surfaces a specific recommended action on the Advisor Detail View component. The actions were configured for both Contact records and Opportunity records, each with their own display priority and trigger logic.

The three-action mechanic — Accept, Reject, Snooze — required custom Flow builds for each path. On Accept for an Email action type, the flow automatically launches the Lightning email composer pre-loaded with the relevant template. The advisor sends, the activity logs to the Timeline, and the NBA action is marked complete. On Reject, the advisor selects a rejection reason from a controlled picklist — those reasons feed a report built for the operations team to monitor strategy rule performance weekly.

Accept, Reject, and Snooze.
Accept, Reject, and Snooze.
Accept
Accept
Reject
Reject
Snooze
Snooze
🧠
11 NBA Strategy Rules Built
Covering Contact and Opportunity objects — from "No contact in 30 days" nudges to "Opportunity stalled 14+ days in Proposal Sent" escalation actions.
📬
Auto Email Launch on Accept
Email action types automatically open the Lightning composer with the contextually correct template — advisor clicks send, activity auto-logs.
🔄
7-Day Snooze Cycle Configured
Snoozed actions re-surface after exactly 7 days; rejection reasons captured to a picklist that feeds weekly strategy performance reporting.
Phase 04
Phase 04

Advisor Detail View Deployment — Lightning UI & Component Configuration

The NBA component needed to feel like part of the Advisor Detail View — not a widget bolted on. We configured the Next Best Action Lightning component to sit prominently in the record layout, above the Activity Timeline on Contact records and in a dedicated column on Opportunity records. The placement decision came directly from the advisor listening sessions in Phase 01.

We ran two rounds of UAT with a pilot group of six advisors — three senior, three junior — before opening the deployment to the full team. UAT surfaced two issues, both resolved before the full rollout. Deployment ran office-by-office, giving the operations team time to monitor adoption at each stage.

Advisor Detail View with NBA Component
Advisor Detail View with NBA Component
📐
NBA Component Placed Above Timeline
Component positioned at the top of the record detail column on Contact, and in a dedicated right column on Opportunity — based on advisor feedback from UAT sessions.
🧪
2-Round UAT with Pilot Advisors
Six advisors tested the system over 10 business days; two bugs identified and resolved before full deployment.
🚀
Phased Rollout — Office by Office
Deployed to NYC and Boston in Week 10, Chicago and Atlanta in Week 11 — giving the operations team time to monitor adoption before final handoff.
Phase 05
Phase 05

Training, Adoption Monitoring & Ops Team Handoff

We ran structured role-based training sessions for advisors, team leads, and the operations team separately — each with a different focus. Advisors learned how to read and act on NBA recommendations, how to use the Snooze function intentionally, and what the Reject reasons mean and why capturing them matters. Team leads learned how to read the strategy performance dashboard to coach their teams. The ops admin learned how to modify strategy rule conditions without re-engaging a developer.

We stayed engaged for 30 days post-go-live with weekly check-in calls and a shared Slack channel for real-time questions. Usage data showed that by Day 14, over 70% of advisors were acting on at least one NBA recommendation per week. By Day 30, that number was 84%. The rejection reason data from the first 30 days also allowed us to retire two of the 11 strategy rules that were generating actions advisors consistently found irrelevant.

NBA Adoption Dashboard
NBA Adoption Dashboard
🎓
Role-Based Training — 3 Tracks
Advisor track (acting on recommendations), team lead track (coaching from dashboard data), ops admin track (maintaining and modifying strategy rules).
📊
84% Weekly Adoption by Day 30
Tracked via Salesforce usage reports — advisors acting on at least one NBA recommendation per week, measured across the full 180-person team.
🔄
Strategy Rules Refined Post-Go-Live
Two of 11 rules retired based on rejection reason data from the first 30 days — ops admin trained to continue this cycle without external support.

Impact & Outcomes

What Changed — In Numbers and In Practice

The number that stuck with the operations head wasn't the conversion lift — it was that junior advisors' performance had moved from 40% below the team average to within 12% of it in 90 days. Not because they'd suddenly become better advisors. Because they now had the same information system that top advisors had been running in their own heads for years.

68%
Reduction in advisor response lag — measured from trigger event to first advisor outreach action
62%
Lift in advisor-to-client conversion rate across the full advisor team in the first 90 days post go-live
90%
Of manual follow-up decisions now system-driven — advisors deciding how to act, not when or whether to act
3.2×
Increase in Salesforce email template send rate — advisors sending from Salesforce instead of personal Gmail accounts
Junior advisor performance closed to within 12% of team average in 90 days — purely through system-driven guidance, no additional coaching
Opportunity stall detection time dropped from 21+ days (manual review) to same-day — NBA surfaces the action the moment the stall condition is met
Compliance team confirmed zero advisor emails sent from personal accounts in the 30 days following NBA go-live — full switch to Salesforce-tracked outreach
84% of advisors acting on at least one NBA recommendation per week by Day 30 — measured via Salesforce usage reporting
Operations team fully self-sufficient on strategy rule maintenance within 6 weeks — no dependency on external developers for ongoing NBA management
Rejection reason data used to retire 2 underperforming strategy rules and refine 3 others — creating a governance cycle the firm now runs independently

"Before NBA, the difference between a senior advisor's performance and a junior advisor's wasn't skill — it was that senior advisors had a system in their head that told them when to call, what to say, and when to escalate. We've now put that system in Salesforce. And junior advisors are using it."

— Twopir Project Lead · US Asset Management · 2024

Frequently Asked Questions

Salesforce Next Best Action for Financial Services — Common Questions

Salesforce Next Best Action uses strategy rules built in Flow to surface contextual recommendations directly on the Advisor Detail View. Based on signals like last contact date, opportunity stage, email engagement, and asset value, the system recommends specific actions — email a prospectus, schedule a call, flag for manager review — and lets the advisor Accept, Reject with reason, or Snooze for 7 days. Each decision feeds back into the model to improve future recommendations. The key advantage over a static alert system is that NBA recommendations are prioritised and ranked — advisors see the single most important action first, not a list of 40 overdue tasks.
A properly scoped NBA implementation typically takes 10–14 weeks, depending on data readiness, existing Salesforce org complexity, and how many recommendation strategies need to be built. Our engagement for this asset management client ran 12 weeks across five phases: discovery, data mapping, strategy build, UI deployment, and training. The variable that kills most timelines isn't the build — it's the discovery phase. If you haven't defined your decision logic before development begins, you'll rebuild strategies mid-project, which adds 4–6 weeks.
Salesforce Next Best Action recommendations are only as good as the activity data feeding the strategy. You need clean Contact records with engagement history, Opportunity objects with accurate stage dates, email activity captured in the CRM (not just in personal inboxes), and ideally asset value or AUM data mapped to the advisor's book. Without these, NBA surfaces generic actions that advisors ignore within two weeks. In our experience, most orgs need 2–3 weeks of data remediation work before they're ready to build strategy rules — which is why we always start with a data audit, not a configuration sprint.
Yes. When an advisor accepts an NBA action of type Email, Salesforce automatically opens a pre-built email template in the Lightning composer — the advisor clicks send, and the activity is logged back to the Contact and Opportunity without any manual entry. Calendar integrations (Outlook, Google Calendar) can be layered in via Salesforce Inbox or standard Activity sync, so accepted meeting actions pre-populate invite details. One compliance benefit most firms don't anticipate: once advisors are sending from Salesforce instead of personal email, every outreach is automatically tracked, date-stamped, and available for audit review.
Yes. Twopir is headquartered in Pune, India, and over 60% of our active clients are US-based. We structure engagements with a 4-hour daily overlap window covering US EST mornings, which covers stand-ups, design reviews, and UAT sessions. Critical decision calls are always scheduled within business hours for the client's time zone. Clients consistently report that our delivery cadence feels no different from a local team — with faster turnaround on async tasks because our team is building while US advisors sleep. Response time on Slack or email is typically under 2 hours during the overlap window, and under 4 hours at any other time of day.

More From Twopir

Your Salesforce Has the Data.
Your Advisors Need the Signal.

We run a free CRM audit to assess your org's NBA readiness — data completeness, object mapping, Flow capacity, and where the quick wins are. You get findings in 5 business days, with a clear implementation scope if you choose to move forward.

Serving US · UK · Australia · UAE · Canada  ·  US EST · UK GMT · AEST coverage  ·  Response within 24 hours guaranteed