[{"data":1,"prerenderedAt":213},["ShallowReactive",2],{"/en/workflows/signal-hygiene-coach-for-confident-decisions":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":197,"tags":198,"integrations":199,"difficulty":201,"author":200,"verified":36,"featured":36,"date":202,"modified":202,"icon":7,"imageSrc":7,"path":203,"alternates":204,"seo":205},"ed508d5b-06cb-4e08-89ac-d83515636186","signal-hygiene-coach-for-confident-decisions","en",null,true,"Signal Hygiene Coach for Confident Decisions","A practical decision coach that helps teams separate trustworthy branch signals from polished noise, catch dirty data early, and choose when to automate vs. escalate to human judgment.","## How it works\nThis workflow turns messy branch numbers, conversation notes, and “everyone feels like…” updates into decision-ready checks—without pretending the data is cleaner than it is. It starts with a knowledge-base policy so Calypso can answer direct questions, then offers a menu of decision-shaped prompts that help operators pressure-test signals before a confident meeting drives a wrong call.\n\nIt’s designed for the moment right before commitment: selecting a branch playbook, reallocating budget, calling a performance issue, or declaring a campaign “worked.” The coaching is biased toward catching failure modes early (definition drift, selection bias, misread attribution) and knowing when automation is safe—and when it’s lying politely.\n\n## Key features\n- Knowledge-base-first behavior for quick Q&A, then guided routing into practical decision checks.\n- Button-based menu for common signal problems: trustworthiness, dirty signal detection, automation vs judgment, comparisons, and culture.\n- Repeatable “meeting-proof” prompts that reduce confident-but-wrong decisions.\n- Built-in escalation path to a human via a handoff node.\n- Loops back to the menu after each coaching response so operators can run multiple checks in one session.\n\n## Step-by-step\n1. **Trigger:** A user starts the conversation (incoming message).\n2. **Knowledge base policy:** Calypso attempts to answer directly from your knowledge base and keeps context available for follow-ups.\n3. **Decision menu:** The workflow presents a button menu: trust branch numbers, spot dirty signal, automation vs judgment, compare branches & attribution, build signal culture, or request a human handoff.\n4. **Routing:** Based on the selected button, the workflow routes into the matching check.\n5. **Coaching response:** A targeted message provides practical prompts and pitfalls to look for.\n6. **Continue or escalate:** After the coaching message, the workflow returns to the decision menu. If the user selects **Human handoff**, it routes to the fallback handoff.\n\n## Setup requirements\n- No credentials required.\n- (Optional but recommended) A populated Calypso knowledge base covering your branch metrics definitions, data sources, and reporting cadence so the knowledge-base policy can answer “what does this number mean here?” questions consistently.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":165,"routingEnabled":8,"active":36},"wf_signal_hygiene_coach_001","calypso-public-library","1.0.0",1,[18,37,43,55,86,95,101,107,112,118,124,132,138,144,150,156],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":35,"deletable":36,"connectable":36},"n0","Workflow settings","flow-configs",[23,24],120,80,{"name":9,"description":26,"tags":27,"triggerType":34},"Knowledge-base-first coaching menu that helps teams validate branch signals, detect dirty data, and decide when to automate vs escalate.",[28,29,30,31,32,33],"decision-making","signal-quality","branch-performance","data-hygiene","attribution","leadership","input","policy",false,{"id":38,"name":39,"type":34,"typeVersion":16,"position":40,"parameters":42,"category":34,"deletable":36,"connectable":8},"n1","Inbound message",[23,41],220,{},{"id":44,"name":45,"type":46,"typeVersion":16,"position":47,"parameters":49,"category":54,"deletable":8,"connectable":8},"n2","Knowledge base guidance","knowledge-base-policy",[48,41],360,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":50,"activationOpener":51,"personalization":53},"default",{"enabled":8,"instruction":52},"If the user asks a direct definition or process question (e.g., “What counts as an active lead?”), answer it from the knowledge base. Then help them choose a decision check from the menu to validate the signal before they act on it.",{"useContactName":8},"response",{"id":56,"name":57,"type":58,"typeVersion":16,"position":59,"parameters":61,"category":54,"deletable":8,"connectable":8},"n3","Decision checks menu","interactive-message",[60,41],620,{"messageType":62,"headerText":63,"bodyText":64,"footerText":65,"sectionTitle":66,"buttons":67,"ctaDisplayText":66,"ctaUrl":66},"button","Pick a decision check","Choose what you’re trying to trust right now. I’ll give you fast prompts to separate signal from polished noise—before the meeting gets confident.","Tip: Start with “Dirty signal”.","",[68,71,74,77,80,83],{"id":69,"title":70},"trust_numbers","Trust the numbers",{"id":72,"title":73},"dirty_signal","Dirty signal",{"id":75,"title":76},"automation_vs_judgment","Auto vs judgment",{"id":78,"title":79},"compare_branches","Compare branches",{"id":81,"title":82},"build_signal_culture","Signal culture",{"id":84,"title":85},"human_handoff","Human handoff",{"id":87,"name":88,"type":89,"typeVersion":16,"position":90,"parameters":92,"category":94,"deletable":8,"connectable":8},"n4","IF trust_numbers","if",[91,23],880,{"buttonId":69,"operator":93},"equals","routing",{"id":96,"name":97,"type":89,"typeVersion":16,"position":98,"parameters":100,"category":94,"deletable":8,"connectable":8},"n5","IF dirty_signal",[91,99],200,{"buttonId":72,"operator":93},{"id":102,"name":103,"type":89,"typeVersion":16,"position":104,"parameters":106,"category":94,"deletable":8,"connectable":8},"n6","IF automation_vs_judgment",[91,105],280,{"buttonId":75,"operator":93},{"id":108,"name":109,"type":89,"typeVersion":16,"position":110,"parameters":111,"category":94,"deletable":8,"connectable":8},"n7","IF compare_branches",[91,48],{"buttonId":78,"operator":93},{"id":113,"name":114,"type":89,"typeVersion":16,"position":115,"parameters":117,"category":94,"deletable":8,"connectable":8},"n8","IF build_signal_culture",[91,116],440,{"buttonId":81,"operator":93},{"id":119,"name":120,"type":89,"typeVersion":16,"position":121,"parameters":123,"category":94,"deletable":8,"connectable":8},"n9","IF human_handoff",[91,122],520,{"buttonId":84,"operator":93},{"id":125,"name":126,"type":127,"typeVersion":16,"position":128,"parameters":130,"category":54,"deletable":8,"connectable":8},"n10","Trustworthy numbers checklist","text-message",[129,23],1140,{"text":131},"Here’s how to tell which branch numbers deserve trust (and which are polished noise):\n\n1) **Definition stability:** Did the definition change this month? If yes, treat trends as *new series*, not improvement.\n2) **Denominator honesty:** Ask “out of what?” A great rate on a tiny base is a confidence trap.\n3) **Lag and revision:** If the number gets revised later, don’t use the first cut to make irreversible calls.\n4) **Operator effort sensitivity:** If the metric jumps when someone learns how it’s judged, it’s measuring incentives, not reality.\n5) **Cross-check:** Pick one “hard-to-fake” companion signal (e.g., verified outcomes vs self-reported activity).\n\nIf you tell me the metric name and what decision you’re making, I’ll help you pick the right cross-check.",{"id":133,"name":134,"type":127,"typeVersion":16,"position":135,"parameters":136,"category":54,"deletable":8,"connectable":8},"n11","Dirty signal quick scan",[129,99],{"text":137},"Dirty signal usually shows up as *neat stories with jagged plumbing*. Quick scan before the meeting:\n\n- **Too smooth:** Perfectly steady growth is often backfilled, batched, or filtered.\n- **Step-change with no cause:** If nothing operational changed, assume instrumentation changed.\n- **One branch is “special”:** Check for workflow differences (staffing, hours, routing rules) before praising or punishing.\n- **Missingness that flatters:** Ask what’s excluded (no-response calls, untracked channels, offline outcomes).\n- **Timestamp weirdness:** Spikes at midnight, end-of-week dumps, or identical durations = process artifact.\n\nRule of thumb: if the chart looks great, ask where the mess went.",{"id":139,"name":140,"type":127,"typeVersion":16,"position":141,"parameters":142,"category":54,"deletable":8,"connectable":8},"n12","Automation vs judgment guidance",[129,105],{"text":143},"When to trust automation vs when you still need human judgment:\n\n**Automate when:**\n- The decision is **reversible** (you can roll back cheaply).\n- Inputs are **well-defined** and audited (same meaning across branches).\n- Errors are **bounded** (a mistake costs minutes, not reputations).\n\n**Use human judgment when:**\n- The metric is a **proxy** (it’s standing in for something you actually care about).\n- Incentives are strong (people can “win the metric” without winning the business).\n- The situation is **novel** (new offer, new channel, new policy—models love the past).\n\nA good compromise: automate the *recommendation*, require a human to state the *why* in one sentence.",{"id":145,"name":146,"type":127,"typeVersion":16,"position":147,"parameters":148,"category":54,"deletable":8,"connectable":8},"n13","Branch comparison & attribution prompts",[129,48],{"text":149},"Comparing branches and attribution is where teams confidently misread things. Use these prompts:\n\n1) **Are we comparing like-with-like?** Different lead mix, hours, staffing tenure, or local constraints will masquerade as “performance.”\n2) **Selection bias check:** Did the “best” branch get easier cases or better routing? If yes, your comparison is mostly allocation.\n3) **Volume vs efficiency:** A branch can look efficient by doing fewer hard things. Separate throughput from conversion.\n4) **Attribution humility:** If two channels touch the same customer, last-touch certainty is often fiction.\n5) **Counterfactual question:** “What would have happened anyway?” If you can’t answer, say ‘uplift unknown’ rather than pretending.\n\nIf you share the comparison you’re making (branch A vs B on what metric?), I’ll suggest the minimum fairness adjustments.",{"id":151,"name":152,"type":127,"typeVersion":16,"position":153,"parameters":154,"category":54,"deletable":8,"connectable":8},"n14","Signal culture playbook",[129,116],{"text":155},"Want a signal culture that helps decisions happen (not just slides)? Build these habits:\n\n- **One owner per metric definition.** No owner = silent drift.\n- **Decision-first reporting:** Every chart must answer: “What will we do differently if this moves?”\n- **Red team the signal:** Someone is assigned to ask “How could this be wrong?” before leadership commits.\n- **Track the revisions:** If numbers get updated later, show the delta. It teaches appropriate confidence.\n- **Celebrate corrected calls:** If people get punished for changing their mind, you’ll get fake certainty forever.\n\nWitty but true: teams don’t drown in data—they drown in unchallenged confidence.",{"id":157,"name":85,"type":158,"typeVersion":16,"position":159,"parameters":160,"category":164,"deletable":8,"connectable":8},"n15","fallback",[129,122],{"handoffMessage":161,"departmentId":162,"departmentName":163},"Got it. I’m handing this to a human so you can sanity-check the signal before it turns into a confident decision. Share: (1) the decision at stake, (2) the key metric(s), (3) what changed, and (4) what would change your mind.","decision-support","Decision Support","terminal",[166,171,173,175,177,179,181,183,185,187,189,191,193,195],{"id":167,"source":38,"target":44,"sourceHandle":168,"targetHandle":169,"type":170},"c1","out","in","edge",{"id":172,"source":44,"target":56,"sourceHandle":168,"targetHandle":169,"type":170},"c2",{"id":174,"source":56,"target":87,"sourceHandle":168,"targetHandle":169,"type":170},"c3",{"id":176,"source":56,"target":96,"sourceHandle":168,"targetHandle":169,"type":170},"c4",{"id":178,"source":56,"target":102,"sourceHandle":168,"targetHandle":169,"type":170},"c5",{"id":180,"source":56,"target":108,"sourceHandle":168,"targetHandle":169,"type":170},"c6",{"id":182,"source":56,"target":113,"sourceHandle":168,"targetHandle":169,"type":170},"c7",{"id":184,"source":56,"target":119,"sourceHandle":168,"targetHandle":169,"type":170},"c8",{"id":186,"source":87,"target":125,"sourceHandle":168,"targetHandle":169,"type":170},"c9",{"id":188,"source":96,"target":133,"sourceHandle":168,"targetHandle":169,"type":170},"c10",{"id":190,"source":102,"target":139,"sourceHandle":168,"targetHandle":169,"type":170},"c11",{"id":192,"source":108,"target":145,"sourceHandle":168,"targetHandle":169,"type":170},"c12",{"id":194,"source":113,"target":151,"sourceHandle":168,"targetHandle":169,"type":170},"c13",{"id":196,"source":119,"target":157,"sourceHandle":168,"targetHandle":169,"type":170},"c14","automation",[28,29,30,31,32,33],[200],"Calypso","intermediate","2026-05-06T11:03:25.307Z","/en/workflows/signal-hygiene-coach-for-confident-decisions",{"en":203},{"title":9,"description":206,"ogDescription":207,"twitterDescription":208,"canonicalPath":203,"robots":209,"schemaType":210,"alternates":211},"Guide teams to trust the right branch signals, catch dirty data early, and choose when to automate vs use judgment—via a simple coaching flow.","A practical coaching workflow that pressure tests branch numbers, spots dirty signals before meetings, and clarifies when automation is safe vs when humans must decide.","Stop confident wrong decisions: pressure test branch signals, catch dirty data, and choose automation vs judgment with a guided coaching menu.","index,follow","HowTo",[212],{"hreflang":6,"href":203},1778614430632]