Signal Triage for Trustworthy Decisions

This workflow acts like a practical “decision pre-flight check” for branch-level numbers, conversation signals, and attribution claims. It first tries to answer using your Knowledge Base, then guides the requester through a short menu of decision-shaped paths (audit a metric, detect dirty signal, compare branches, etc.).

Instead of chasing perfect cleanliness, it focuses on the failure modes that look fine right up until a meeting goes off the rails: shifting definitions, selective visibility, attribution mirages, and automation used as a substitute for judgment.

• Knowledge Base-first responses to handle common questions quickly, with routing available when the KB can’t help.
• A decision-focused menu that funnels messy asks into five practical “what should I trust?” paths.
• Clear, operator-friendly checklists that highlight where polished noise usually hides.
• Structured escalation to a Decision Support team after the user gets a first-pass reality check.

1. Trigger: A new inbound conversation starts the workflow.
2. Knowledge Base attempt: The assistant answers from your KB when possible (definitions, policies, metric owners, FAQ).
3. Orientation message: The assistant sets expectations: this is a quick trust-check, not an academic lecture.
4. User chooses a path: A menu lets the user pick what they’re trying to decide (audit a number, spot dirty signal, automation vs judgment, compare branches, or build signal culture).
5. Checklist response: The workflow sends a tailored set of checks for the selected path.
6. Handoff: The conversation routes to Decision Support for follow-up with the user’s context and the checklist they received.

• Calypso Inbox enabled for inbound conversations.
• A populated Knowledge Base (recommended: metric definitions, data owners, branch event taxonomy, attribution rules, and known caveats).
• A configured Decision Support department in Calypso routing (no external credentials required).