Next Best Action dependencies on visits, email, and Planner settings
Key Takeaway
Next Best Action depends on other Life Sciences setup. Visits need Visit Management, emails need Emails and Templates, and weekly recommendations follow the work week in Planner settings. A visit created from a recommendation is linked to it only when the TerrAccRcmActStatusUpdateHandle trigger handler is turned on.
Life Sciences Next Best Action shows field reps recommended actions in the Next Best Action component. A rep can act on a recommendation by creating a visit or sending an email directly from the component. Because the component depends on other Life Sciences features, setting it up means configuring those features. You also need the trigger handlers behind the component and the right user access.
What the Next Best Action component shows
The Next Best Action component shows records from the Territory Account Recommended Action object, where recommended actions are stored. The component shares recommendations by territory and tracks completed actions.
You supply the recommendations in one of two ways. You can create Territory Account Recommended Action records manually. You can also integrate your own recommendation model to create the records automatically.
A record in the object doesn't always appear. Only accessible and active recommendation records appear in the component. A record stays hidden if it's inactive or if the user can't access it.