Recommendations are created as records on the standard Recommendation object, usually from the Recommendations app or tab in Setup. Build the record first, then point a strategy at it and place the component on a page so users can see it.
- Open the Recommendations app
Use the App Launcher to open the Recommendations app or tab. This is the standard object that backs Einstein Next Best Action. Click New to start a record.
- Write the card text
Fill in the Name for internal use and the Description that the user reads. Keep the description short and action oriented so the suggestion is obvious at a glance.
- Set the accept and reject labels
Enter an Acceptance Label for the accept button and a Rejection Label for the dismiss button. Use verbs the user understands, such as Book Now and Not Now.
- Attach the action flow
In the Action field, reference the screen flow or autolaunched flow that should run when the user accepts. Optionally add an image and save the record.
- Wire it into a strategy and page
Add the recommendation to a strategy so it can be filtered and ranked, then place the Einstein Next Best Action component on a record or app page bound to that strategy.
Internal label used to find and reference the recommendation; not shown on the card.
The sentence the user reads on the card; this is the actual offer or ask.
Text on the accept button, for example Apply Discount or Schedule Visit.
Text on the dismiss button, for example No Thanks or Not Now.
Reference to the screen flow or autolaunched flow that runs when the user accepts.
- Only screen flows and autolaunched flows can be assigned to a recommendation; record-triggered and scheduled flows cannot.
- A recommendation never appears on its own. It must be returned by a strategy that the placed component is bound to.
- The Description is the only persuasion the user sees, so vague wording quietly tanks your acceptance rate.
- The object exists from API version 45.0, so older orgs or integrations on earlier API versions will not see it.