Dirty Signal Checklist for Branch Decisions

This workflow turns “Is this number real?” into a quick, repeatable decision path. It starts with a knowledge-base layer (so common definitions and policies are answered consistently), then offers a menu of decision-shaped checklists to triage branch metrics, conversations, and attribution before a confident meeting drives a wrong call.

Use it when branch dashboards look clean but feel off. The goal isn’t to over-clean the evidence—it’s to catch the early signs of dirty signal (silent exclusions, reporting drift, incentive gaming) and to decide whether you should trust automation, pause for judgment, or escalate for a deeper review.

• Knowledge-base first, so teams get consistent definitions and guardrails before routing.
• Button-based menu that routes users into practical checklists (trust tests, dirty-signal spotting, attribution pitfalls).
• “Decision-ready” prompts designed for leaders: what to verify, what usually breaks first, and what to do next.
• Clear escalation path to a human team when the signal is too messy for self-serve.

1. Trigger: A user starts the chat workflow.
2. Knowledge base policy: Calypso applies your signal/metric definitions and internal guidance before presenting options.
3. Menu: The user chooses what they’re trying to decide (trust a branch number, spot dirty signal, automation vs judgment, compare branches, or build signal culture).
4. Checklist response: The workflow sends a targeted, plain-English checklist with the fastest “trust tests” and common failure modes for that situation.
5. Escalation (if needed): If none of the menu options match, the workflow routes to a human fallback for help.

• Calypso Chat enabled for your workspace.
• Knowledge Base content covering: metric definitions, branch reporting rules, attribution rules, and escalation owners.
• No additional credentials are required for this workflow.