Einstein Next Best Actions Considerations

Keep these considerations in mind when working with strategies and recommendations.

Einstein Next Best Action relies on flows, recommendations, strategies, and components, and has standard objects for reporting.

Flows

Flow requirements: All Recommendation objects must reference a flow. Without any flows, you can't show a recommendation.
Active flow requirements: Strategies only load recommendations with active flows.
REST API execution context: When you start a flow by using REST API, it runs in the context of the authenticated user. The running user's profile and permission sets determine the object permissions and field-level access of the flow. Create a profile and permission sets for users who run the flow.

Custom category fields: Consider adding a custom category field to the recommendation object and layout. A category field gives you more control when loading, sorting, and filtering recommendations, and more options when creating flows.
Recommendation labels: Create names, descriptions, acceptance labels, and rejection labels that are appropriate for your intended audience.
Duplicate names: Reusing a recommendation name creates a recommendation instead of overwriting the existing one. Duplicated names can cause strategies to show duplicate recommendations to customers.
Flow status visibility: All flows, both inactive and active, display in the Action dropdown list. After you save your recommendation, you can see if the flow is active.
Inactive flow references: You can create a recommendation that references an inactive flow, but no strategy loads it until you activate the flow.

Recommendation requirements: All strategies require at least one recommendation.
Loading recommendations: In Flow Builder, you can load and filter the records of a Recommendation object, or load and filter the records of any object and convert them into recommendations at the end of the strategy by using the Recommendation Assignment element.
Limit Repetitions element: Use the Limit Repetitions element in Flow Builder to hide a recommendation from all users after they respond more than a defined number of times within a defined number of days. For limit repetitions to work, recommendations must have a unique record ID.
Subflow support: Recommendation Strategy flows don't support calling subflows.

Custom report types: When you create strategies in Flow Builder, create custom report types by using the Recommendation Strategy Metrics and Recommendation Responses primary objects.
Unique record ID requirement: When you create reports from the Recommendation Reactions primary object, recommendations must have a unique record ID to show the recommendation source name and ID correctly for limit reoffers.

Rights of ALBERT EINSTEIN are used with permission of The Hebrew University of Jerusalem. Represented exclusively by Greenlight.