Branch Signal Decision Guardrails

This workflow turns “we have numbers” into “we have decision‑worthy evidence.” It starts with a knowledge-base answer (so you’re not reinventing guidance every conversation), then offers a few sharp, decision-shaped routes: sanity-checking a metric, comparing branches without fooling yourself, and deciding where automation is safe vs. where human judgment is still doing the real work.

It’s built for the moment right before decisions harden: the pre-meeting, the weekly review, the “why is Branch 12 down?” thread. The goal is not perfect data—it’s catching polished noise early, keeping messy truth intact, and getting to a call you can defend.

• Knowledge base policy up front to deliver consistent, reusable guidance before routing
• Interactive menu that routes leaders into common decision situations (sanity check, branch comparison, automation vs judgment)
• Practical “red flag” checklists that help spot dirty signal before it derails a meeting
• Clear guardrails on which branch numbers are usually trustworthy vs. cosmetically clean
• Optional human handoff path when the situation needs investigation or authority

1. Trigger: A user starts the conversation in Calypso (e.g., WhatsApp chat entry point).
2. Knowledge base guidance: Calypso applies the Knowledge Base Policy to answer naturally in plain language, using your existing signal/metric guidance.
3. Choose the decision situation: The workflow sends an interactive menu with four options:
   1. Run a signal sanity check
   2. Compare branches safely
   3. Automation vs. human judgment
   4. Talk to a person
4. Route based on selection:
   • If Run a signal sanity check → user receives a fast checklist to detect “clean-looking, wrong” signals.
   • If Compare branches safely → user receives a practical comparison framework (what usually gets misread first).
   • If Automation vs. human judgment → user receives rules of thumb for when automation is safe, and when leaders must stay in the loop.
   • If Talk to a person → the workflow hands off to routing with a clear handoff message.

• Calypso Knowledge Base: Add or confirm articles that cover branch metric definitions, common failure modes (attribution, conversation tagging, outages), and decision guidelines. No external credentials required.
• Channel support for interactive messages: Use a Calypso channel that supports interactive buttons (e.g., WhatsApp).
• Optional routing: If you want the “Talk to a person” path to go somewhere specific, ensure a routing department exists and update the department fields in the fallback node (otherwise it can remain a general handoff).