This guide highlights the main differences between Journeys and Workflows.
| Journeys | Workflows | |
| Data Health | Only NWB and FWB | Enhanced with logical nodes and routing, the system now supports separate nodes for Notes and Objects |
| Reminders | Same content sent repeatedly | Smarter, activity-based reminders with contextual follow-ups |
| Responses | Static (Entity Attributes only) | Context-aware, dynamic responses, and LLM-powered sentiment analysis for better decision-making |
| Guardrails | One customer impact others | Isolation between customer usage |
| FUP | No Credit - Limit boundary | Credit - Limit for all possible events |
| Priority Brackets | Static priority irrespective of events | On demand priority assignment |
HERO Usecase
The following serves as a framework for systematic targeting, ensuring efficient and data-driven engagement.
1. Whom to Target
Identifying the right audience for targeted engagement:
- Cohort Definition: A well-defined group of individuals with similar characteristics and common objectives.
- Qualification Criteria: Establish rules to determine when a user qualifies for targeting.
- Triggering Mechanism: Define conditions that activate the next step in engagement.
2. How to Target
Executing personalized and strategic communication:
- Personalized Content: Group users with similar records and send tailored messages.
- Follow-Up Actions: If users do not respond, initiate follow-up actions based on previous communication history.
3. When to Target
Timing strategies to maximize engagement effectiveness:
- User Inactivity: Reach out when users are not taking any specific action.
- Time Intervals: Space out communication to avoid overwhelming users and ensure better engagement.
4. Process Workflow
- Writeback: Store and update user engagement data.
- Analyze and Reiterate: Continuously review performance and optimize targeting strategies.
Graphical representation of a HERO usecase:
Examples of a HERO usecase: