Signal Sanity Check for Branch Decisions

This workflow turns “messy but convincing” branch numbers, conversations, and local events into decision-ready judgment. It starts by applying your Knowledge Base guidance (your definitions, your caveats, your rules of thumb), then asks the operator what kind of signal problem they’re dealing with.

From there, it routes the conversation into short, decision-shaped checklists: what to trust, what to distrust, what usually breaks first, and when to stop pretending automation is a substitute for thinking. If the situation is high-stakes or ambiguous, the user can hand off to a human.

• Uses a Knowledge Base policy first, so answers follow your team’s definitions and “gotchas”
• Interactive menu routes to decision-specific playbooks (branch metrics, dirty signals, attribution, culture)
• Quick “confidence killers” checklist to catch clean-looking dirty data before meetings
• Clear boundary-setting on when automation is safe vs. when human judgment should step in
• One-tap handoff path to a human team for complex or high-risk decisions

1. Start (Input): The workflow begins when a user opens the conversation.
2. Signal guidance (KB): The assistant follows your Knowledge Base policy for signal definitions, measurement caveats, and local context.
3. Choose a signal task (List): The user picks what they need help with (e.g., branch numbers, dirty signal, automation vs. judgment).
4. Routing chain (IF nodes): The workflow checks the selected button ID and routes to the matching playbook.
5. Deliver the playbook (Text): The user receives a concise checklist and practical coaching, then gets sent back to the main menu to pick another task.
6. Handoff (Fallback): If the user chooses “Bring in a human,” the workflow routes them to the Analytics department with a clear handoff message.

• Calypso Inbox enabled on at least one channel (e.g., Web chat) to run the conversation.
• A populated Knowledge Base with your definitions for branch metrics, attribution rules, known data quality issues, and decision thresholds.
• No external credentials are required for this workflow as built.