These steps follow the Strategy Builder route. The Flow Builder route replaces steps two through four with a flow of type Recommendation Strategy.
- Create the Recommendation records first
Nothing renders until the menu exists. Each needs a name, the description a user actually reads, and an Action Reference pointing at what runs on accept.
- Open Strategy Builder and start a strategy
From Setup, enter Next Best Action in the Quick Find box, select Next Best Action, then click New Strategy. Choose an API name you can live with, since the component references it.
- Load, then narrow immediately
Add a load element to pull candidates, and put your cheapest, most selective filter directly after it. Everything downstream runs against whatever survives.
- Branch for audiences, then rank and suppress repeats
Use an if element to send segments down separate paths, then sort on the field that expresses priority. Add a Limit Reoffers element so an ignored card stops arriving every morning.
- Add the component and point it at the strategy
In Lightning App Builder, drag the Einstein Next Best Action component onto the record page, select your strategy, and tell it which builder produced it.
- Test against a record that should not match
Preview with one record that qualifies and one that clearly does not. Confirm the second returns nothing rather than everything, because an over-broad filter is the failure that ships quietly.
Flow Builder with the Recommendation Strategy flow type for new work, Strategy Builder when model-based scoring is involved.
The standard Recommendation object, or a custom object where a package defines its own recommendation records.
A Lightning record page for internal users, or an Experience Builder site page for customers and partners.
A static priority field for rule-based strategies, or a model-written score for predictive ones.
- An empty component is the default failure mode. When a filter drops every candidate there is no error, so everyone assumes the feature was never switched on.
- A callout buried in an invocable action runs inside page load, so a slow external system becomes a slow record page.
- A saved strategy is not automatically the live one. Confirm the component points at the version you just edited before calling the change shipped.