Trustworthy Branch Signals Navigator

This workflow runs as a guided chat that turns “we have numbers” into “we have decision‑ready evidence.” It helps teams pressure‑test branch metrics, conversation signals, and attribution stories before they harden into confident (and wrong) decisions.

Users pick a decision-shaped topic from a menu. The workflow returns practical checks, common failure modes, and crisp next steps—then offers to loop back for another topic or hand off to a human when the situation is genuinely messy.

• A single menu that routes users to the most common decision traps: branch metric trust, dirty signal detection, automation vs. judgment, and comparisons/attribution.
• Built-in knowledge base policy for consistent tone and reusable guidance before routing.
• “One more thing?” loop that encourages good decision hygiene without forcing a long session.
• Clear human handoff path for cases where automation should not pretend to be certainty.

1. Start: The workflow begins when a user messages the workflow entry point.
2. Signal knowledge & tone: A knowledge base policy applies consistent guidance style and allows knowledge-backed responses when available.
3. Pick a decision to sharpen: The user chooses what they’re trying to decide (e.g., which branch numbers to trust, how to spot dirty signal, or how to compare branches and attribution).
4. Decision routing: The workflow routes based on the selected button:
   1. Which branch numbers deserve trust? → returns a practical trust checklist and what “polished noise” looks like.
   2. How to spot dirty signal early → returns fast tests to catch data contamination before the meeting.
   3. When to trust automation vs. human judgment → returns guardrails for when automation is helpful and when it’s a liability.
   4. Comparing branches & attribution → returns the common misreads and safer comparison patterns.
   5. Build a signal culture (decisions > slides) → returns lightweight habits that make evidence usable.
   6. Talk to a human → routes to a human team.
5. Anything else?: After any guidance, the user can go back to the main menu or request a human handoff.

• No credentials are required.
• Configure your Analytics Ops (or equivalent) handoff destination in Calypso so the fallback route reaches the right team.