Decision Signals Coach: Trust Checks & Next Moves

This workflow helps leaders and operators turn “looks fine” signals into “safe to decide” signals. It starts with a knowledge-base-first assistant (so you can keep the guidance consistent), then routes people into decision-shaped paths like Which branch numbers deserve trust, How to spot dirty signal before a meeting, and When automation is safe vs when humans must step in.

The point isn’t to clean everything into a fake certainty. It’s to surface the few checks that catch the usual failures early—before the confident wrong decision, the heroic dashboard screenshot, and the awkward “so… why did this branch ‘win’?” follow-up.

• Uses a knowledge-base policy first so your house rules on signal trust are applied consistently.
• Presents a button menu that routes users into the most common decision situations (branch numbers, dirty signal, automation, attribution, culture).
• Delivers actionable, non-academic checklists as short text messages—built for real meetings and real data.
• Includes an optional handoff to Analytics for cases that require human review.

1. Input starts the workflow when a user enters the experience.
2. Knowledge Base Policy activates: the assistant answers from your knowledge base when possible and stays grounded in your documented standards.
3. The workflow sends an interactive button menu asking what the user is trying to decide.
4. Based on the button selected, an IF route delivers one of the following guidance messages:
   1. Branch numbers: what to trust (quick credibility tests, “too smooth” patterns, denominator traps).
   2. Spot dirty signal before the meeting (stale timestamps, mixed definitions, sudden tracking changes, survivorship).
   3. Automation vs human judgment (where automation is reliable, where it quietly fails, and what requires review).
   4. Comparing branches & attribution (selection bias, seasonality, mix shifts, channel overlap).
   5. Build a signal culture (make decisions happen, reduce slide-theater, set ownership).
5. If the user requests it (or none of the buttons match), the workflow hands off to Analytics with a clear message.

• A Calypso workspace with this workflow imported.
• (Recommended) A populated Calypso Knowledge Base containing your definitions (e.g., “active customer,” “lead,” “qualified conversation”), metric owners, and known tracking caveats.
• (Optional) A Calypso routing destination/department named Analytics to receive handoffs.
• No external credentials are required by this workflow as built.