Branch Signal Triage Coach

This workflow turns “we have a bunch of numbers and opinions” into a practical decision path. It first anchors the conversation in your knowledge base (your local definitions, metrics, and guardrails), then offers a menu of decision-shaped topics: trustworthiness of branch metrics, dirty signal detection, automation vs. judgment, messy evidence handling, cross-branch comparisons/attribution, and building a signal culture.

It’s designed for the moment right before a confident meeting goes off the rails: the data looks tidy, the story is polished, and the risk is hidden in what wasn’t measured, what was over-counted, or what got cleaned until it lied.

• Starts with a knowledge-base-guided coach so advice matches your organization’s metric definitions and norms.
• Provides a button-based menu of the most common “decision failure modes” (trust, hygiene, automation, attribution).
• Routes users to clear, non-academic playbooks for each decision type.
• Includes a human handoff path when the situation is ambiguous, political, or high-stakes.
• Keeps the workflow operator-friendly: easy to expand with more buttons or deeper KB articles.

1. Start (Input): A user opens the workflow.
2. Decision Coach KB (Knowledge Base Policy): The assistant answers using your knowledge base first, so “branch conversion” or “attributed revenue” means what you mean.
3. Choose what you need (Interactive Buttons): The user selects the decision they’re trying to make.
4. Routing (IF nodes): The workflow checks which button was clicked and routes accordingly.
5. Outcome (Text Message): The user gets a practical checklist/playbook tailored to the selected decision.
6. Escalation (Fallback): If the user asks for a human (or the selection doesn’t match), the workflow hands off to the configured department.

• Calypso Conversations enabled in your workspace.
• Optional (recommended): A lightweight knowledge base with your metric definitions (e.g., “branch conversion,” “qualified conversation,” “attribution window,” “do-not-use metrics”).
• No external credentials required for this workflow as written.