Branch Signal Coach: Trust vs Noise

This workflow turns “messy signal” conversations into decision-ready next steps. Instead of debating dashboards in a meeting, it gives leaders a practical set of checks to run before they trust a branch metric, compare branches, or automate a decision.

It’s designed for the real failure mode: bad data that looks clean. The flow uses a knowledge-base-first policy (so it can answer common questions consistently), then routes people through a short menu of decision-shaped prompts that surface what usually breaks first—definitions, timing, incentives, and attribution.

• Knowledge-base-first responses for consistent guidance on signal definitions and common pitfalls
• A decision-shaped menu that routes users to targeted “sanity checks” (trust, hygiene, automation, comparisons, culture)
• Clear escalation path to human help when the situation is ambiguous or politically sensitive
• A “back to menu” loop so teams can run multiple checks in one conversation

1. Trigger: The workflow starts when a user sends a message (Input).
2. Knowledge base policy: Calypso attempts to answer using your Knowledge Base first, with a practical “decision guardrails” tone.
3. Main menu: The user selects what they’re trying to decide (e.g., trust a number, spot dirty signal, compare branches).
4. Routing by choice: An IF chain matches the selected button and sends the corresponding guidance message.
5. Next steps menu: After the guidance, the user can either return to the main menu or request human help.
6. Handoff (optional): If requested (or if nothing matches), the workflow routes to fallback handoff messaging.

• Calypso Knowledge Base: Recommended (to make the knowledge-base step useful), but no credentials are required in this template.
• Calypso Inbox/chat entrypoint: Needed to receive the initial user message.
• Optional: Configure the fallback department if you want routing to a specific team; otherwise the default handoff message will be used.