Signal & Research Decision Coach

This workflow acts like a calm, experienced advisor sitting in the meeting with you—before the team confidently drives off a cliff with “clean-looking” numbers. It uses your Knowledge Base first (for your internal definitions and policies), then offers a short menu of decision-shaped prompts to quickly diagnose whether a branch metric, conversation trend, or attribution story deserves trust.

Operators use it to triage messy evidence without “sanitizing away” the truth: you’ll get practical checks for dirty signal, comparisons that usually mislead, and guidance on when automation can be trusted—and when it needs a human in the loop.

• Knowledge Base-first responses for your internal metric definitions, thresholds, and branch policies
• Button-based menu that routes to the exact decision situation (trust, hygiene, automation, comparisons, culture)
• Fast “dirty signal” checks designed to catch problems before the confident meeting
• Clear guidance on when to accept automated outputs vs when to require human review
• One-tap handoff path for cases that should go to a human analyst

1. Input (Trigger): A teammate asks a question or requests a sanity check on a branch number, conversation trend, or attribution claim.
2. Knowledge Base Policy: If the question maps to known internal definitions (e.g., “What counts as a qualified conversation?”), the workflow answers from your Knowledge Base. If not, it continues to guided routing.
3. Interactive Menu: The user selects what they need:
   1. Which branch numbers deserve trust?
   2. Spot dirty signal before the meeting
   3. Automation vs human judgment
   4. Messy evidence → usable insight
   5. Comparing branches & attribution pitfalls
   6. Build a signal culture (less slides, more decisions)
   7. Talk to a human analyst
4. Decision Guidance (Routed Text): The workflow returns a concise playbook tailored to the selected situation.
5. Human Handoff (Optional): If the user chooses the analyst option, the workflow sends a handoff message and routes to the specified department.

• Calypso Knowledge Base: Recommended. Add (or confirm) entries for metric definitions, branch comparison rules, attribution rules, and escalation policies.
• Credentials: None required for this workflow as configured.
• Optional routing: Configure the target department for analyst handoff (name/id) if you want the “Talk to a human analyst” path to route correctly.