Branch Signal Decision Litmus Test

This workflow helps operators and leaders pressure-test branch numbers, conversations, and “looks-good-on-a-slide” metrics before they harden into confident wrong decisions. It starts with a knowledge assistant (so common definitions and policies are consistent), then routes the user into a decision-shaped checklist based on what they’re trying to decide.

Think of it as a practical litmus test: you pick the situation (trusting branch numbers, spotting dirty signal, automation vs judgment, comparing branches, or building a signal culture) and the workflow replies with crisp guardrails and what usually breaks first.

• Knowledge-base-first guidance to keep definitions and KPI rules consistent
• Button-based routing into common decision moments (not generic “analytics advice”)
• Built-in “dirty signal” sniff test to catch polished noise early
• Practical guardrails for when to trust automation vs when to demand human review
• Optional handoff path to an Analytics/Ops team for high-stakes or ambiguous cases

1. User Input kicks off the flow from any inbound conversation.
2. Knowledge Assistant answers straightforward questions from your Knowledge Base and falls through to routing when the user needs a structured decision check.
3. Choose your decision check prompts the user to pick what they’re trying to validate.
4. Based on the button tapped, the workflow sends a targeted response:
   1. Which numbers deserve trust? → a short set of reliability checks for branch KPIs (what to trust, what to treat as noise).
   2. Spot dirty signal fast → red flags that predict a confident meeting going off the rails.
   3. Automation vs human judgment → rules of thumb for when automation is safe and when it’s dangerously persuasive.
   4. Compare branches fairly → common misreads in branch comparisons, conversations, and attribution.
   5. Build a signal culture → habits that make decisions happen (instead of slide production).
   6. Talk to a human → hands off to Analytics with a clear expectation-setting message.

• Calypso Knowledge Base populated with your branch KPI definitions, metric owners, known data caveats (e.g., backfills), and attribution rules.
• No additional credentials are required for this workflow as written.