Branch Signal Decision Field Guide

This workflow acts like a “meeting-safe” signal advisor: it answers the real questions people ask right before decisions get made—Which numbers can we trust? What’s probably dirty? When should we let automation run?—without turning it into an academic lecture.

It starts with a Knowledge Base step to ground responses in your team’s agreed definitions (what counts as a lead, how branches are compared, what attribution model is official). Then it routes users through a button-based menu into short, decision-shaped guidance and checks. Each answer loops back to the menu so leaders can pressure-test multiple angles quickly.

• Knowledge Base–first responses to keep definitions consistent before routing into guidance.
• Button menu for fast triage (trustworthy branch numbers, dirty signals, automation vs judgment, attribution comparisons, and signal culture).
• “One-screen” reality checks designed to catch polished noise before it gets slide-deck authority.
• Loops back to the menu after each answer so users can run multiple checks in one session.
• Optional human handoff to an Analytics Ops / Data team when a decision is high-stakes or the signal is disputed.

1. Trigger: A user starts the workflow.
2. Knowledge Base policy: The workflow consults your Knowledge Base to align on definitions and avoid “same word, different metric” problems.
3. Decision menu: The user chooses what they need:
   • Which branch numbers deserve trust
   • How to spot dirty signal
   • Automation vs human judgment
   • Comparing branches, conversations, and attribution
   • Building a signal culture (decisions, not slides)
   • Talk to Analytics Ops
4. Guidance response: The workflow sends a focused checklist and practical advice for the selected path.
5. Repeat or hand off: After most answers, the workflow returns to the menu. If the user selects Talk to Analytics Ops, it hands off to the configured department.

• Calypso Knowledge Base: Recommended (this workflow assumes you have at least basic metric definitions and reporting rules documented).
• Department routing: If you want human handoff, ensure the Analytics Ops (or equivalent) department exists in Calypso and update the department ID/name in the fallback node.
• Credentials: None required.