[{"data":1,"prerenderedAt":223},["ShallowReactive",2],{"/en/workflows/decisionready-signal-checks":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":205,"tags":206,"integrations":209,"difficulty":211,"author":210,"verified":32,"featured":32,"date":212,"modified":212,"icon":7,"imageSrc":7,"path":213,"alternates":214,"seo":215},"1e7f4bbe-b85e-4c34-adf5-847c5e7383fc","decisionready-signal-checks","en",null,true,"Decision‑Ready Signal Checks","Turn messy branch metrics, conversations, and attribution signals into decision-ready guidance. This workflow helps teams spot polished noise, dirty signal, and the moments where automation should step aside for human judgment.","## How it works\nThis workflow is a decision helper for the moment right before a team makes a confident mistake. It routes people through a few practical “signal checks” to decide which branch numbers are trustworthy, how to spot dirty signal hiding in clean dashboards, and when automation is safe versus when judgment is still required.\n\nIt starts with a short knowledge-base policy step (so answers stay consistent with your internal definitions), then offers a button menu. Each path returns a concise, meeting-ready checklist you can apply to branch metrics, conversation notes, and attribution claims—without “cleaning away” the inconvenient truth.\n\n## Key features\n- Knowledge-base aligned coaching before any routing, so definitions stay consistent\n- Button-based menu for decision-shaped questions (trust, dirty signal, automation vs judgment, comparisons, culture)\n- Practical checklists designed for branch-level metrics, conversations, and attribution\n- Clear escalation path to a human owner when the right move is “stop and verify”\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a new request comes in.\n2. **Knowledge base alignment:** The workflow applies your knowledge base policy to keep guidance consistent with internal definitions.\n3. **Choose a decision:** The user selects a button:\n   - *Which branch numbers deserve trust?*\n   - *How to spot dirty signal fast*\n   - *Automation vs human judgment*\n   - *Comparing branches & attribution pitfalls*\n   - *Build a signal culture (not a slide culture)*\n   - *Talk to a human*\n4. **Receive the checklist:** The workflow returns a targeted, meeting-ready set of checks for the chosen topic.\n5. **Escalate when needed:** If *Talk to a human* is chosen, the workflow hands off to your designated team/department.\n\n## Setup requirements\n- No external credentials required.\n- (Optional but recommended) Maintain definitions and measurement notes in your Calypso Knowledge Base so guidance matches your internal standards.\n- If you want human handoff to work smoothly, ensure the referenced department exists and is staffed during coverage hours.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":169,"routingEnabled":8,"active":32},"wf_decision_ready_signal_checks_v1","calypso-public-library","1.0.0",1,[18,33,39,51,81,91,99,105,111,116,122,128,134,140,146,152,162],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":24,"category":31,"deletable":32,"connectable":32},"node_flow_configs","Workflow settings","flow-configs",[23,23],80,{"name":9,"description":25,"tags":26,"triggerType":30},"Button-led signal checks for branch metrics, conversations, and attribution—designed to prevent confident wrong decisions.",[27,28,29],"signal-quality","branch-metrics","decision-making","input","policy",false,{"id":34,"name":35,"type":30,"typeVersion":16,"position":36,"parameters":38,"category":30,"deletable":32,"connectable":8},"node_input","Inbound request",[23,37],200,{},{"id":40,"name":41,"type":42,"typeVersion":16,"position":43,"parameters":45,"category":50,"deletable":8,"connectable":8},"node_kb_policy","Knowledge base policy","knowledge-base-policy",[44,37],320,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":46,"activationOpener":47,"personalization":49},"default",{"enabled":8,"instruction":48},"Use the knowledge base definitions for branch metrics, attribution, and conversation tagging. If a term is ambiguous, ask a clarifying question before recommending action.",{"useContactName":32},"response",{"id":52,"name":53,"type":54,"typeVersion":16,"position":55,"parameters":57,"category":50,"deletable":8,"connectable":8},"node_menu","Choose your signal check","interactive-message",[56,37],580,{"messageType":58,"headerText":9,"bodyText":59,"footerText":60,"sectionTitle":61,"buttons":62,"ctaDisplayText":61,"ctaUrl":61},"button","Pick the question you’re trying to answer. You’ll get a short checklist you can use in a meeting—before the room falls in love with a bad number.","Tip: High stakes + fuzzy signal? Escalate early.","",[63,66,69,72,75,78],{"id":64,"title":65},"btn_trust_numbers","Trust numbers",{"id":67,"title":68},"btn_dirty_signal","Spot dirty signal",{"id":70,"title":71},"btn_automation_vs_judgment","Auto vs judgment",{"id":73,"title":74},"btn_compare_branches","Compare branches",{"id":76,"title":77},"btn_signal_culture","Build signal culture",{"id":79,"title":80},"btn_talk_to_human","Talk to a human",{"id":82,"name":83,"type":84,"typeVersion":16,"position":85,"parameters":88,"category":90,"deletable":8,"connectable":8},"node_if_trust","If: trust numbers","if",[86,87],820,120,{"buttonId":64,"operator":89},"equals","routing",{"id":92,"name":93,"type":94,"typeVersion":16,"position":95,"parameters":97,"category":50,"deletable":8,"connectable":8},"node_msg_trust","Checklist: numbers you can trust","text-message",[96,87],1080,{"text":98},"Here’s how to tell “decision-worthy” branch numbers from polished noise:\n\n1) **Definition check (boring but lethal):** Is everyone using the same definition (visit, lead, booked, funded)? If not, stop.\n2) **Denominator sanity:** Are we comparing rates with similar volume? Tiny denominators produce heroic stories.\n3) **Lag & backfill:** Does the metric revise after the meeting? If yes, label it “prelim” and avoid irreversible decisions.\n4) **Instrumentation stability:** Any recent changes to tracking, forms, call routing, or staff behavior? Breaks mimic growth.\n5) **Incentive pressure:** If someone’s bonus depends on it, assume gaming exists until disproven.\n6) **Cross-signal agreement:** A trustworthy number usually agrees with at least one independent signal (cash, ops load, complaints, churn).\n\nIf you can’t pass 1–3 quickly, treat the metric as a *hint*, not a verdict.",{"id":100,"name":101,"type":84,"typeVersion":16,"position":102,"parameters":104,"category":90,"deletable":8,"connectable":8},"node_if_dirty","If: dirty signal",[86,103],220,{"buttonId":67,"operator":89},{"id":106,"name":107,"type":94,"typeVersion":16,"position":108,"parameters":109,"category":50,"deletable":8,"connectable":8},"node_msg_dirty","Checklist: spot dirty signal",[96,103],{"text":110},"Fast ways to catch dirty signal **before** a confident meeting:\n\n- **Too-smooth trend test:** Real operations are lumpy. Perfectly smooth lines often mean aggregation artifacts or selective reporting.\n- **Edge-case sniff:** Ask: “What gets excluded?” Returns, duplicates, transfers, partials, reopened cases—often where the truth lives.\n- **One-field dependency:** If the story depends on one tag (source, disposition, campaign), assume it’s inconsistently used.\n- **Sudden step change:** Great news overnight is usually a tracking change, staffing change, routing change, or definition change.\n- **Conversation mismatch:** If the floor says ‘it’s quieter’ but the dashboard says ‘record demand,’ don’t average them—investigate.\n\nPractical move: pick **3 records** at random and trace end-to-end. Dirty signal rarely survives contact with real examples.",{"id":112,"name":113,"type":84,"typeVersion":16,"position":114,"parameters":115,"category":90,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[86,44],{"buttonId":70,"operator":89},{"id":117,"name":118,"type":94,"typeVersion":16,"position":119,"parameters":120,"category":50,"deletable":8,"connectable":8},"node_msg_auto","Guide: when to trust automation",[96,44],{"text":121},"When to trust automation (and when to keep a human in the loop):\n\n**Trust automation when:**\n- The decision is **reversible** (you can roll back without drama).\n- The metric is **well-defined, stable, and audited** (same meaning across branches and time).\n- The cost of a miss is **small** and bounded.\n- You have **feedback** (you’ll quickly see if it was wrong).\n\n**Require human judgment when:**\n- The decision is **one-way** (pricing changes, staffing cuts, territory shifts).\n- Data can be **gamed** or is heavily incentive-driven.\n- You’re relying on **attribution** to explain causality.\n- The story depends on **exceptions, edge cases, or qualitative context**.\n\nRule of thumb: automate the *routine*, but escalate the *regretful*.",{"id":123,"name":124,"type":84,"typeVersion":16,"position":125,"parameters":127,"category":90,"deletable":8,"connectable":8},"node_if_compare","If: compare branches",[86,126],420,{"buttonId":73,"operator":89},{"id":129,"name":130,"type":94,"typeVersion":16,"position":131,"parameters":132,"category":50,"deletable":8,"connectable":8},"node_msg_compare","Checklist: compare branches & attribution",[96,126],{"text":133},"Comparing branches is where good teams accidentally lie to themselves. Use this:\n\n1) **Normalize for opportunity:** Footfall, installed base, local seasonality, staffing hours. Raw totals are a popularity contest.\n2) **Check mix shift:** A branch can ‘improve’ simply by handling different customer types.\n3) **Watch selection bias:** The best branches often get the best leads (or cherry-pick). That’s not skill; that’s routing.\n4) **Attribution humility:** If multiple touches exist, don’t crown one channel because it’s easy to track.\n5) **Look for trade-offs:** Higher conversion with worse retention or higher refunds is not a win—it's a delayed problem.\n\nGood comparison question: “If we swapped inputs (leads, hours, mix), would the ranking change?” If yes, the ‘winner’ is mostly context.",{"id":135,"name":136,"type":84,"typeVersion":16,"position":137,"parameters":139,"category":90,"deletable":8,"connectable":8},"node_if_culture","If: signal culture",[86,138],520,{"buttonId":76,"operator":89},{"id":141,"name":142,"type":94,"typeVersion":16,"position":143,"parameters":144,"category":50,"deletable":8,"connectable":8},"node_msg_culture","Playbook: build a signal culture",[96,138],{"text":145},"A signal culture that helps decisions happen (not just slides):\n\n- **One metric, one owner, one definition.** If nobody owns it, it will drift.\n- **Decision labels:** Every dashboard metric should answer: *monitor / investigate / decide*. Most should be “monitor.”\n- **Pre-mortems for big calls:** Ask “How could this be wrong?” before you ask “How fast can we scale it?”\n- **Example-first habit:** Require 2–3 real records/conversations alongside aggregate numbers.\n- **Celebrate detection, not just success:** Reward the person who finds the tracking bug before it becomes a strategy.\n\nWitty but true: the fastest way to ruin signal culture is to punish people for discovering reality.",{"id":147,"name":148,"type":84,"typeVersion":16,"position":149,"parameters":151,"category":90,"deletable":8,"connectable":8},"node_if_human","If: talk to a human",[86,150],620,{"buttonId":79,"operator":89},{"id":153,"name":154,"type":155,"typeVersion":16,"position":156,"parameters":157,"category":161,"deletable":8,"connectable":8},"node_fallback","Handoff to human support","fallback",[96,150],{"handoffMessage":158,"departmentId":159,"departmentName":160},"Got it—this sounds like it needs a quick human verification. Please share: (1) the branch(es), (2) the metric in question, (3) the timeframe, and (4) what decision you’re about to make. I’m handing this to the team now.","dept_data_insights","Data & Insights","terminal",{"id":163,"name":164,"type":94,"typeVersion":16,"position":165,"parameters":167,"category":50,"deletable":8,"connectable":8},"node_msg_default","Default: reselect option",[96,166],720,{"text":168},"I didn’t catch a selection. Please tap one of the buttons above so I can route you to the right signal check.",[170,175,177,179,182,185,187,189,191,193,195,197,199,201,203],{"id":171,"source":34,"target":40,"sourceHandle":172,"targetHandle":173,"type":174},"conn_input_to_kb","out","in","smoothstep",{"id":176,"source":40,"target":52,"sourceHandle":172,"targetHandle":173,"type":174},"conn_kb_to_menu",{"id":178,"source":52,"target":82,"sourceHandle":172,"targetHandle":173,"type":174},"conn_menu_to_if_trust",{"id":180,"source":82,"target":92,"sourceHandle":181,"targetHandle":173,"type":174},"conn_if_trust_true","true",{"id":183,"source":82,"target":100,"sourceHandle":184,"targetHandle":173,"type":174},"conn_if_trust_false","false",{"id":186,"source":100,"target":106,"sourceHandle":181,"targetHandle":173,"type":174},"conn_if_dirty_true",{"id":188,"source":100,"target":112,"sourceHandle":184,"targetHandle":173,"type":174},"conn_if_dirty_false",{"id":190,"source":112,"target":117,"sourceHandle":181,"targetHandle":173,"type":174},"conn_if_auto_true",{"id":192,"source":112,"target":123,"sourceHandle":184,"targetHandle":173,"type":174},"conn_if_auto_false",{"id":194,"source":123,"target":129,"sourceHandle":181,"targetHandle":173,"type":174},"conn_if_compare_true",{"id":196,"source":123,"target":135,"sourceHandle":184,"targetHandle":173,"type":174},"conn_if_compare_false",{"id":198,"source":135,"target":141,"sourceHandle":181,"targetHandle":173,"type":174},"conn_if_culture_true",{"id":200,"source":135,"target":147,"sourceHandle":184,"targetHandle":173,"type":174},"conn_if_culture_false",{"id":202,"source":147,"target":153,"sourceHandle":181,"targetHandle":173,"type":174},"conn_if_human_true",{"id":204,"source":147,"target":163,"sourceHandle":184,"targetHandle":173,"type":174},"conn_if_human_false","automation",[27,28,29,207,208],"data-hygiene","attribution",[210],"Calypso","intermediate","2026-07-23T11:03:54.581Z","/en/workflows/decisionready-signal-checks",{"en":213},{"title":9,"description":216,"ogDescription":217,"twitterDescription":218,"canonicalPath":213,"robots":219,"schemaType":220,"alternates":221},"Help teams trust the right branch signals, spot dirty data early, and know when to use automation vs human judgment—before decisions go wrong.","A practical workflow to sanity check branch numbers, detect dirty signal, and avoid confident wrong decisions. Includes automation vs judgment guardrails.","Turn messy metrics and conversations into decision ready insight. Spot polished noise, catch dirty signal early, and escalate when judgment is needed.","index,follow","HowTo",[222],{"hreflang":6,"href":213},1785947666267]