Every activity in Pear Suite is driven by one or more flows, which serve as the structured roadmap of questions and logic encountered during a member interaction. By modifying a flow, organizations can refine their data collection, update language for clarity, and automate care coordination through advanced logic triggers.

Understanding flows as activity roadmaps

A flow is the primary vehicle for capturing member data during a visit. Whether configured as a single-page assessment or a question-by-question script, the flow defines exactly what information is collected. Editing these templates allows administrators to ensure that the care team is always asking the most relevant questions and following the latest program protocols.

Customizing flow structure and logic

The flow editor provides a comprehensive environment for tailoring member interactions. Within this space, users can perform the following:

• Content Management: Add, remove, or reorder questions to streamline the conversation.
• Response Types: Modify how data is captured, such as transitioning a field from a short text input to a multiple-choice selection.
• Branching Logic: Create conditional paths where specific questions only appear based on previous answers (e.g., "If Yes, show follow-up question").
• Answer Actions: Set up powerful automations that trigger instantly based on responses, such as automatically generating a care goal or scheduling a follow-up visit.

Impact of updates and best practices

It is important to note that any changes saved to a flow template will apply to all future activities scheduled using that template. These updates will not retroactively alter activities that are already completed or currently in progress, ensuring the integrity of historical documentation. When deciding whether to update an existing flow or create a new version entirely, consult with your Customer Success Manager to ensure your data reporting remains consistent across different program cycles.