Numbers Under Pressure: Branch Signal Checks

This workflow turns “messy evidence” (branch numbers, conversation notes, attribution reports, and operational anecdotes) into decision-ready guidance without pretending the data is cleaner than it is. It starts by answering the user’s question from your Knowledge Base, then routes them into a focused set of decision-shaped prompts.

It’s designed for the moment right before a confident meeting goes off the rails: when dashboards look tidy, the story feels obvious, and the fastest path to a wrong call is “everyone nods.” The workflow nudges people toward practical checks, sensible thresholds, and the right kind of uncertainty.

• Uses a Knowledge Base-first policy so known standards and definitions are applied before ad‑hoc opinions.
• Presents a button-based menu that maps to real decision moments (trusting branch numbers, dirty-signal detection, automation vs judgment, attribution comparisons, and signal culture).
• Routes users through simple, explainable logic (one selection → one targeted playbook).
• Includes a human handoff fallback when the question is ambiguous, political, or high-stakes.

1. Trigger: A user starts the workflow (message or chat entry).
2. Knowledge Base response: The workflow answers using your Knowledge Base where possible and keeps context sticky for the session.
3. Decision menu: The user chooses what they need help with:
   1. Which branch numbers deserve trust
   2. How to spot dirty signal fast
   3. Automation vs human judgment
   4. Comparing branches & attribution
   5. Build a signal culture (less slides, more decisions)
4. Targeted guidance: Based on the selected option, the workflow returns a concise playbook with checks, common failure modes, and “what I’d do next.”
5. Fallback to a team: If no option matches (or the interaction is unclear), the workflow routes the conversation to a human team with a clear handoff message.

• Calypso Knowledge Base: Add or validate articles for metric definitions, data freshness expectations, attribution rules, and branch reporting standards.
• Routing department: Create or select a department (e.g., “Analytics & Ops”) to receive fallbacks.
• Credentials: None required beyond your normal Calypso access and Knowledge Base publishing permissions.