Branch Signal Decision Compass

This workflow acts like a decision pre-flight check for branch-level reporting, conversation insights, and “looks-good” dashboards. It answers the questions teams usually ask five minutes before a confident meeting goes off the rails: Which numbers are real? What’s contaminated? When should we let automation decide?

It first tries to resolve questions using your Knowledge Base (so the guidance stays consistent with your internal definitions). If the KB can’t confidently answer, it routes the user into a short menu of decision-shaped checks—each designed to surface dirty signal early and push the conversation toward what’s trustworthy enough to act on.

• Uses a Knowledge Base-first policy to keep definitions and guardrails consistent.
• Offers a single menu of decision checks (trust, hygiene, automation vs. judgment, messy evidence, comparisons, culture).
• Delivers operator-ready prompts that help teams inspect signal quality before debating outcomes.
• Includes an escalation path to a human team when the situation is high-stakes or politically fragile.

1. User Input starts the workflow when someone asks for help interpreting branch signals or decision inputs.
2. Knowledge Assistant attempts to answer using your Knowledge Base and standard definitions.
3. If the KB can’t fully answer, Choose a decision check presents a set of buttons.
4. Based on the selection, the workflow sends one of the following responses:
   1. Which branch numbers deserve trust? — a checklist to separate stable metrics from polished noise.
   2. Spot dirty signal fast — a quick “contamination test” before the meeting locks onto a narrative.
   3. Automation vs. human judgment — rules of thumb for when to let systems decide and when humans must.
   4. Messy evidence to usable insight — how to summarize without sanding off inconvenient truth.
   5. Common misreads in comparisons — what teams repeatedly get wrong in branch, conversation, and attribution comparisons.
   6. Talk to a decision steward — hands off to a human owner when stakes are high or definitions are disputed.

• Calypso workflow builder access.
• A configured Calypso Knowledge Base is recommended (so the assistant can reuse your internal metric definitions and policies).
• No external app credentials are required for this workflow.