[{"data":1,"prerenderedAt":343},["ShallowReactive",2],{"/en/workflows/decision-signal-compass-trust-noise-next-steps":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":325,"tags":326,"integrations":327,"difficulty":330,"author":331,"verified":35,"featured":35,"date":332,"modified":332,"icon":7,"imageSrc":7,"path":333,"alternates":334,"seo":335},"11728f2e-2e68-44ab-b5af-26eaf35b8167","decision-signal-compass-trust-noise-next-steps","en",null,true,"Decision Signal Compass: Trust, Noise, Next Steps","A guided chat workflow that helps teams sanity-check branch numbers, spot polished noise, and decide when to trust automation vs human judgment.","## How it works\nThis workflow turns “we have some numbers and a meeting in 20 minutes” into a calmer, decision-ready checklist. It guides a user through the most common failure modes in branch metrics, conversations, and attribution—where the data looks clean right up until someone makes a confident wrong call.\n\nIt starts with a Knowledge Base-first policy (so your team can reuse your house definitions and guardrails), then routes users through short, decision-shaped prompts: which numbers deserve trust, how to spot dirty signal early, when to trust automation, how to compare branches without lying to yourself, and how to build a signal culture that produces decisions—not slides.\n\n## Key features\n- Knowledge Base-first responses, then structured routing for consistent “sanity check” coaching\n- A decision-shaped menu covering trust, dirty signal detection, automation vs judgment, comparisons, and culture\n- Practical checklists designed to surface hidden confounds before a meeting goes off the rails\n- “Run another check” loop to keep teams moving without restarting the conversation\n- One-tap handoff to a human when the situation needs context, judgment, or escalation\n\n## Step-by-step\n1. **Trigger:** A user opens the workflow (Input).\n2. **Knowledge Base policy applies:** The workflow prioritizes your Knowledge Base guidance, then continues into routing if needed.\n3. **User chooses a check:** An interactive list offers:\n   - Which numbers deserve trust (vs polished noise)\n   - Spot dirty signal before the meeting\n   - Trust automation vs keep a human in the loop\n   - Compare branches, conversations, and attribution\n   - Build a signal culture that enables decisions\n   - Talk to a human\n4. **Workflow delivers the selected checklist:** A short, practical message provides the specific checks and common misreads for that choice.\n5. **Next move:** The user can either **Run another check** (returns to the main menu) or **Talk to a human** (handoff).\n\n## Setup requirements\n- **Calypso Knowledge Base (recommended):** Add or link articles that define your branch metrics, attribution rules, reporting cadence, and known data gaps. No additional credentials are required inside this workflow.\n- **Calypso Inbox routing:** If you use handoff, ensure a team can receive escalations via the configured fallback route.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":252,"routingEnabled":8,"active":35},"wf-decision-signal-compass-v1","calypso-public-library","1.0.1",1,[18,36,42,54,86,95,101,107,113,119,125,134,148,154,161,171,175,182,192,196,202,212,216,223,232,236,244],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":34,"deletable":35,"connectable":35},"cfg-1","Workflow settings","flow-configs",[23,24],80,60,{"name":9,"description":26,"tags":27,"triggerType":33},"Guided checks for signal trust, dirty data, automation vs judgment, and safe comparisons across branches and conversations.",[28,29,30,31,32],"signal-quality","decision-making","branch-metrics","attribution","triage","input","policy",false,{"id":37,"name":38,"type":33,"typeVersion":16,"position":39,"parameters":41,"category":33,"deletable":35,"connectable":8},"in-1","Start",[23,40],180,{},{"id":43,"name":44,"type":45,"typeVersion":16,"position":46,"parameters":48,"category":53,"deletable":8,"connectable":8},"kb-1","Knowledge Base first","knowledge-base-policy",[47,40],280,{"enabled":8,"fallbackToRouting":8,"sticky":35,"stickyMode":49,"activationOpener":50,"personalization":52},"default",{"enabled":8,"instruction":51},"I can help you pressure-test branch signals and avoid polished noise. Pick the check that matches the decision you’re about to make.",{"useContactName":35},"response",{"id":55,"name":56,"type":57,"typeVersion":16,"position":58,"parameters":60,"category":53,"deletable":8,"connectable":8},"im-menu","Choose a signal check","interactive-message",[59,40],520,{"messageType":61,"headerText":62,"bodyText":63,"footerText":64,"sectionTitle":65,"buttons":66,"ctaDisplayText":85,"ctaUrl":85},"list","Decision Signal Compass","Pick the check you need. Built for real decisions—when the data looks fine until it suddenly isn’t.","Tip: Run “Dirty signal” before meetings.","Signal checks",[67,70,73,76,79,82],{"id":68,"title":69},"trust_numbers","Trust the numbers",{"id":71,"title":72},"dirty_signal","Spot dirty signal",{"id":74,"title":75},"automation_vs_humans","Automation vs humans",{"id":77,"title":78},"compare_branches","Compare branches",{"id":80,"title":81},"signal_culture","Signal culture",{"id":83,"title":84},"handoff","Talk to a human","",{"id":87,"name":88,"type":89,"typeVersion":16,"position":90,"parameters":92,"category":94,"deletable":8,"connectable":8},"if-trust","Route: trust_numbers","if",[91,40],760,{"buttonId":68,"operator":93},"equals","routing",{"id":96,"name":97,"type":89,"typeVersion":16,"position":98,"parameters":100,"category":94,"deletable":8,"connectable":8},"if-dirty","Route: dirty_signal",[91,99],300,{"buttonId":71,"operator":93},{"id":102,"name":103,"type":89,"typeVersion":16,"position":104,"parameters":106,"category":94,"deletable":8,"connectable":8},"if-auto","Route: automation_vs_humans",[91,105],420,{"buttonId":74,"operator":93},{"id":108,"name":109,"type":89,"typeVersion":16,"position":110,"parameters":112,"category":94,"deletable":8,"connectable":8},"if-compare","Route: compare_branches",[91,111],540,{"buttonId":77,"operator":93},{"id":114,"name":115,"type":89,"typeVersion":16,"position":116,"parameters":118,"category":94,"deletable":8,"connectable":8},"if-culture","Route: signal_culture",[91,117],660,{"buttonId":80,"operator":93},{"id":120,"name":121,"type":89,"typeVersion":16,"position":122,"parameters":124,"category":94,"deletable":8,"connectable":8},"if-handoff","Route: handoff",[91,123],780,{"buttonId":83,"operator":93},{"id":126,"name":127,"type":128,"typeVersion":16,"position":129,"parameters":132,"category":53,"deletable":8,"connectable":8},"txt-trust","Trust check: numbers","text-message",[130,131],1020,120,{"text":133},"Which branch numbers deserve trust (and which are polished noise):\n\n1) Decision-grade numbers have a *known capture process*. If nobody can explain how the number is created end-to-end, it’s a vibe with decimals.\n2) Prefer *counts with clear denominators* over rates without context. A conversion rate without volume is a confidence trap.\n3) Watch for “quiet backfills”: data that improves when you stop looking. If last week’s numbers keep changing, treat them as draft.\n4) Check sensitivity: would one policy change, staffing shift, or tracking tweak move this metric? If yes, demand a note next to the chart.\n5) Trust numbers that come with *boundaries*: what it includes/excludes, known gaps, and the simplest way it can be wrong.\n\nIf you can’t write a one-sentence definition + one-sentence failure mode, don’t let it steer a big decision.",{"id":135,"name":136,"type":57,"typeVersion":16,"position":137,"parameters":139,"category":53,"deletable":8,"connectable":8},"im-next-1","Next move (trust numbers)",[130,138],200,{"messageType":140,"headerText":141,"bodyText":142,"footerText":85,"sectionTitle":85,"buttons":143,"ctaDisplayText":85,"ctaUrl":85},"button","Next move","Want to pressure-test another angle, or do you need a human to weigh in?",[144,147],{"id":145,"title":146},"back_to_menu","Run another check",{"id":83,"title":84},{"id":149,"name":150,"type":89,"typeVersion":16,"position":151,"parameters":153,"category":94,"deletable":8,"connectable":8},"if-back-1","Run another check?",[152,138],1240,{"buttonId":145,"operator":93},{"id":155,"name":156,"type":128,"typeVersion":16,"position":157,"parameters":159,"category":53,"deletable":8,"connectable":8},"txt-dirty","Dirty signal: fast detection",[130,158],260,{"text":160},"How to spot dirty signal *before* a confident meeting goes off the rails:\n\n1) Look for impossible smoothness: perfectly stable lines in a messy world often mean “we stopped measuring part of the world.”\n2) Ask “what changed?” in plain language: staffing, hours, incentives, script changes, routing, tags, tracking, system migrations.\n3) Compare the metric to its nearest neighbor. If leads are up but conversations are flat (or vice versa), something’s leaking.\n4) Inspect one layer down: 5–10 real examples (calls, chats, forms, tickets). Dirty signal hides in edge cases.\n5) Check timing: spikes that align with month-end, campaigns, or reporting deadlines are often process artifacts.\n\nRule of thumb: if you can’t name the top two ways this metric can be wrong, the meeting will do it for you—publicly.",{"id":162,"name":163,"type":57,"typeVersion":16,"position":164,"parameters":166,"category":53,"deletable":8,"connectable":8},"im-next-2","Next move (dirty signal)",[130,165],340,{"messageType":140,"headerText":141,"bodyText":167,"footerText":85,"sectionTitle":85,"buttons":168,"ctaDisplayText":85,"ctaUrl":85},"Keep going, or hand this to someone who can pull examples and confirm what changed?",[169,170],{"id":145,"title":146},{"id":83,"title":84},{"id":172,"name":150,"type":89,"typeVersion":16,"position":173,"parameters":174,"category":94,"deletable":8,"connectable":8},"if-back-2",[152,165],{"buttonId":145,"operator":93},{"id":176,"name":177,"type":128,"typeVersion":16,"position":178,"parameters":180,"category":53,"deletable":8,"connectable":8},"txt-auto","Automation vs judgment",[130,179],400,{"text":181},"When to trust automation—and when you still need human judgment:\n\nTrust automation when:\n- The input data is stable, definitions don’t change weekly, and exceptions are rare.\n- The cost of being wrong is small and reversible (tactical optimizations, not reputation bets).\n- There’s a clear feedback loop (you’ll know quickly if it worked).\n\nDemand human judgment when:\n- A policy, incentive, or process recently changed (automation will “learn” the wrong lesson fast).\n- The metric can be gamed (tagging, disposition codes, attribution rules).\n- The decision is one-way door (pricing, staffing model, branch closures, compliance).\n\nGood leaders don’t distrust automation—they distrust *silent assumptions*. Make the assumptions audible.",{"id":183,"name":184,"type":57,"typeVersion":16,"position":185,"parameters":187,"category":53,"deletable":8,"connectable":8},"im-next-3","Next move (automation)",[130,186],480,{"messageType":140,"headerText":141,"bodyText":188,"footerText":85,"sectionTitle":85,"buttons":189,"ctaDisplayText":85,"ctaUrl":85},"Want to run another check, or escalate for a judgment call?",[190,191],{"id":145,"title":146},{"id":83,"title":84},{"id":193,"name":150,"type":89,"typeVersion":16,"position":194,"parameters":195,"category":94,"deletable":8,"connectable":8},"if-back-3",[152,186],{"buttonId":145,"operator":93},{"id":197,"name":198,"type":128,"typeVersion":16,"position":199,"parameters":200,"category":53,"deletable":8,"connectable":8},"txt-compare","Compare branches safely",[130,111],{"text":201},"What teams repeatedly misread when comparing branches, conversations, and attribution:\n\n1) Different denominators pretending to be the same. Two branches can have the same conversion rate while one is living on 10 leads and the other on 1,000.\n2) Mix shifts: Branch A has more complex cases, different hours, different routing, different seniority. That’s not “performance,” it’s composition.\n3) Tagging discipline: one branch labels everything, another labels nothing. Guess which looks “cleaner.”\n4) Attribution drift: if the rules changed (or the channel mix changed), month-over-month comparisons become a story about rules.\n5) Conversation counts ≠ quality: more conversations can mean better engagement… or broken routing.\n\nA fair comparison starts with: same definitions, same window, and one sanity sample of real records from each branch.",{"id":203,"name":204,"type":57,"typeVersion":16,"position":205,"parameters":207,"category":53,"deletable":8,"connectable":8},"im-next-4","Next move (comparisons)",[130,206],620,{"messageType":140,"headerText":141,"bodyText":208,"footerText":85,"sectionTitle":85,"buttons":209,"ctaDisplayText":85,"ctaUrl":85},"Run another check, or hand off to someone who can validate definitions and samples?",[210,211],{"id":145,"title":146},{"id":83,"title":84},{"id":213,"name":150,"type":89,"typeVersion":16,"position":214,"parameters":215,"category":94,"deletable":8,"connectable":8},"if-back-4",[152,206],{"buttonId":145,"operator":93},{"id":217,"name":218,"type":128,"typeVersion":16,"position":219,"parameters":221,"category":53,"deletable":8,"connectable":8},"txt-culture","Build a signal culture",[130,220],680,{"text":222},"How to build a signal culture that helps decisions happen (not just slides):\n\n1) Standardize definitions *only where it matters*. Over-standardizing creates performative compliance and worse truth.\n2) Require a “failure mode” line on every metric: “This can be wrong when…” It turns debate into diagnosis.\n3) Promote receipts, not rhetoric: 5 real examples beat 50 polished charts when something feels off.\n4) Make reversibility explicit: label decisions as one-way or two-way doors. It changes what evidence you need.\n5) Reward early bad news: teams hide dirty signal when you punish messengers.\n\nCulture isn’t posters. It’s what happens when someone says, “These numbers look great,” and the room replies, “Great—what could fool us?”",{"id":224,"name":225,"type":57,"typeVersion":16,"position":226,"parameters":227,"category":53,"deletable":8,"connectable":8},"im-next-5","Next move (culture)",[130,91],{"messageType":140,"headerText":141,"bodyText":228,"footerText":85,"sectionTitle":85,"buttons":229,"ctaDisplayText":85,"ctaUrl":85},"Want another checklist, or do you need help turning this into a team habit?",[230,231],{"id":145,"title":146},{"id":83,"title":84},{"id":233,"name":150,"type":89,"typeVersion":16,"position":234,"parameters":235,"category":94,"deletable":8,"connectable":8},"if-back-5",[152,91],{"buttonId":145,"operator":93},{"id":237,"name":238,"type":128,"typeVersion":16,"position":239,"parameters":242,"category":53,"deletable":8,"connectable":8},"txt-restart","Restart instructions",[240,241],1480,360,{"text":243},"To run another check, restart this workflow to reopen the Signal Checks menu.\n\nIf you’re heading into a meeting, start with **Spot dirty signal**—it catches the sneaky stuff before the room gets confident.",{"id":245,"name":246,"type":247,"typeVersion":16,"position":248,"parameters":249,"category":251,"deletable":8,"connectable":8},"fb-1","Handoff to human","fallback",[240,59],{"handoffMessage":250,"departmentId":85,"departmentName":85},"Got it. I’m looping in a human to help validate the signal and avoid the classic “clean chart, wrong decision” problem. Share: (1) the decision you’re making, (2) the metric(s), (3) time window, and (4) what recently changed.","terminal",[253,255,257,259,262,265,267,269,271,273,275,277,279,281,283,285,287,289,291,293,295,297,299,301,303,305,307,309,311,313,315,317,319,321,323],{"id":254,"source":37,"target":43,"sourceHandle":85,"targetHandle":85,"type":49},"c-in-kb",{"id":256,"source":43,"target":55,"sourceHandle":85,"targetHandle":85,"type":49},"c-kb-menu",{"id":258,"source":55,"target":87,"sourceHandle":85,"targetHandle":85,"type":49},"c-menu-iftrust",{"id":260,"source":87,"target":126,"sourceHandle":261,"targetHandle":85,"type":49},"c-iftrust-true","true",{"id":263,"source":87,"target":96,"sourceHandle":264,"targetHandle":85,"type":49},"c-iftrust-false","false",{"id":266,"source":96,"target":155,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifdirty-true",{"id":268,"source":96,"target":102,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifdirty-false",{"id":270,"source":102,"target":176,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifauto-true",{"id":272,"source":102,"target":108,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifauto-false",{"id":274,"source":108,"target":197,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifcompare-true",{"id":276,"source":108,"target":114,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifcompare-false",{"id":278,"source":114,"target":217,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifculture-true",{"id":280,"source":114,"target":120,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifculture-false",{"id":282,"source":120,"target":245,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifhandoff-true",{"id":284,"source":120,"target":245,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifhandoff-false",{"id":286,"source":126,"target":135,"sourceHandle":85,"targetHandle":85,"type":49},"c-trust-next",{"id":288,"source":135,"target":149,"sourceHandle":85,"targetHandle":85,"type":49},"c-next1-ifback",{"id":290,"source":149,"target":237,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifback1-true",{"id":292,"source":149,"target":245,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifback1-false",{"id":294,"source":155,"target":162,"sourceHandle":85,"targetHandle":85,"type":49},"c-dirty-next",{"id":296,"source":162,"target":172,"sourceHandle":85,"targetHandle":85,"type":49},"c-next2-ifback",{"id":298,"source":172,"target":237,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifback2-true",{"id":300,"source":172,"target":245,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifback2-false",{"id":302,"source":176,"target":183,"sourceHandle":85,"targetHandle":85,"type":49},"c-auto-next",{"id":304,"source":183,"target":193,"sourceHandle":85,"targetHandle":85,"type":49},"c-next3-ifback",{"id":306,"source":193,"target":237,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifback3-true",{"id":308,"source":193,"target":245,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifback3-false",{"id":310,"source":197,"target":203,"sourceHandle":85,"targetHandle":85,"type":49},"c-compare-next",{"id":312,"source":203,"target":213,"sourceHandle":85,"targetHandle":85,"type":49},"c-next4-ifback",{"id":314,"source":213,"target":237,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifback4-true",{"id":316,"source":213,"target":245,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifback4-false",{"id":318,"source":217,"target":224,"sourceHandle":85,"targetHandle":85,"type":49},"c-culture-next",{"id":320,"source":224,"target":233,"sourceHandle":85,"targetHandle":85,"type":49},"c-next5-ifback",{"id":322,"source":233,"target":237,"sourceHandle":261,"targetHandle":85,"type":49},"c-ifback5-true",{"id":324,"source":233,"target":245,"sourceHandle":264,"targetHandle":85,"type":49},"c-ifback5-false","automation",[28,29,30,31,32],[328,329],"Calypso Inbox","Calypso Knowledge Base","intermediate","Calypso","2026-04-08T11:06:03.388Z","/en/workflows/decision-signal-compass-trust-noise-next-steps",{"en":333},{"title":9,"description":336,"ogDescription":337,"twitterDescription":338,"canonicalPath":333,"robots":339,"schemaType":340,"alternates":341},"Guide teams to trust the right branch signals, spot dirty data early, and choose automation vs human judgment—via a structured chat flow.","A practical chat workflow to sanity check branch metrics, catch polished noise, and make better decisions before the confident meeting.","Stop confident wrong decisions: use this chat flow to test signal quality, compare branches safely, and know when humans must step in.","index,follow","HowTo",[342],{"hreflang":6,"href":333},1776877119338]