How It Works
Each On Login Popup automation is scoped to one or more source groups, which determines which customers it applies to. Within each automation, staff configure one or more cases. Each case has its own set of criteria and a corresponding action — the prompt to display within the online banking interface. When a customer logs in, the platform evaluates each active automation against them. If the customer is in the automation’s source group, the cases are checked from top to bottom. The first case whose criteria all match is used — the associated prompt is displayed to the customer. No further cases in that automation are evaluated once a match is found. If no case matches, no prompt is shown and the customer proceeds to their dashboard as normal.Cases
Cases allow a single automation to handle multiple scenarios with a single configuration. Rather than creating a separate automation for every combination of conditions, staff define ordered cases that each represent a distinct situation. Cases are evaluated in priority order — Case 1 is checked first, then Case 2, and so on. This matters when conditions can overlap: the most specific or highest-priority scenario should be placed first so it takes precedence when multiple cases would otherwise match. Each case includes:- Criteria — one or more conditions the customer must meet for this case to match. Multiple criteria within a case must all be true.
- Action — the prompt to display when this case matches.
