Best Practices for Using Recommendations
Effective strategies for leveraging recommendations to enhance user support.
Table of Contents
Recommendations in Pear Suite are simple yet powerful text-based guidance tools that appear within a member’s profile. They are designed to help care teams remain consistent and thoughtful by suggesting specific next steps based on the data collected during member interactions.
Recommendations as actionable cues
Recommendations are intended to be used as a cue, not a command. They serve as a helpful checklist or reminder note that appears only when a specific need is identified. Because these cues are triggered by previous member responses, they often highlight critical information regarding eligibility, program requirements, or urgent needs. It is essential to read the recommendation description carefully, as it contains the full guidance, including follow-up steps, lists of community partners, or ideas for additional support.
Acting on and dismissing recommendations
When a recommendation appears, it signifies that a member has shared something significant in a previous activity that requires manual review or action. Once the care team has addressed the recommendation or determined that it no longer applies, it should be dismissed from the profile. Dismissing completed or irrelevant recommendations ensures the member's profile remains organized and only displays active, high-priority guidance for the staff.
Best practices for admins and workflow builders
For those configuring the platform, recommendations should be built to be as actionable as possible while remaining flexible. Effective recommendations utilize short, clear titles that are easy for staff to scan during a visit. Builders should avoid overloading users with too many recommendations for low-impact answers, instead focusing on meaningful follow-up opportunities. It is important to remember that a recommendation itself is not an action, but a note that supports and informs the actions taken by the care team. Keeping the underlying logic clean and avoiding over-stacked conditions ensures that the right guidance appears at the right time.