[{"data":1,"prerenderedAt":225},["ShallowReactive",2],{"/en/workflows/decisionready-signal-checkpoints":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":206,"tags":207,"integrations":210,"difficulty":212,"author":213,"verified":33,"featured":33,"date":214,"modified":214,"icon":7,"imageSrc":7,"path":215,"alternates":216,"seo":217},"ff19ba36-b7cb-4fe9-908c-acbc88d3563e","decisionready-signal-checkpoints","en",null,true,"Decision‑Ready Signal Checkpoints","A guided triage flow that helps teams separate trustworthy branch signals from polished noise, catch dirty data early, and decide when to use automation vs human judgment.","## How it works\nThis workflow is a practical “signal triage” assistant for teams who make decisions from branch numbers, conversations, and attribution. It routes people to short, decision-shaped checklists that reveal what’s likely trustworthy, what’s probably polished noise, and what to verify before a confident meeting drives the org into a confident wrong turn.\n\nIt starts with a knowledge-backed policy to answer questions consistently, then offers a menu of common decision situations (branch numbers, dirty signal, automation vs judgment, comparisons, and culture). Each path ends with an actionable checklist you can apply immediately.\n\n## Key features\n- Knowledge-base-first responses to keep signal guidance consistent before routing\n- Menu-based routing for fast triage (no long forms; just pick the decision situation)\n- Practical checklists focused on what breaks first: definitions, coverage, timing, incentives, and outliers\n- Dedicated path for “automation vs judgment” to prevent silent over-trust in dashboards\n- Human handoff option when the situation is sensitive or high-stakes\n\n## Step-by-step\n1. **Start**: The workflow begins when a message arrives.\n2. **Knowledge base guardrails**: The assistant prioritizes approved knowledge for signal design and decision guidance.\n3. **Pick your situation**: A list menu asks what you’re trying to decide (branch numbers, dirty signal, automation vs judgment, comparisons, culture, or handoff).\n4. **Branch numbers — trust vs noise**: If selected, the workflow sends a checklist for determining whether a branch metric deserves trust.\n5. **Dirty signal — spot it early**: If selected, the workflow sends quick tests to catch contamination before it derails a meeting.\n6. **Automation vs judgment**: If selected, the workflow sends rules-of-thumb for when to trust automation and when to require human review.\n7. **Compare branches & attribution**: If selected, the workflow sends a comparison/attribution sanity checklist to avoid repeated misreads.\n8. **Build signal culture**: If selected, the workflow sends a short playbook for building a culture where signals drive decisions (not slide decks).\n9. **Talk to a person**: If selected—or if nothing matches—the workflow routes to a human handoff message.\n\n## Setup requirements\n- **Calypso**: A workspace with this workflow installed.\n- **WhatsApp channel**: Connected in Calypso to use interactive list messages.\n- **Knowledge base**: Add/enable your internal articles on branch metrics, attribution, and signal definitions (no additional credentials required beyond Calypso access).",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":171,"routingEnabled":8,"active":33},"wf_decision_ready_signal_checkpoints_v1","calypso-public-library","1.0.0",1,[18,34,40,51,83,93,101,107,113,119,125,131,137,143,149,155,165],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_cfg","Flow settings","flow-configs",[23,24],-260,-220,{"name":9,"description":26,"tags":27,"triggerType":31},"Guided triage to separate trustworthy branch signals from polished noise, spot dirty signal early, and choose automation vs human judgment.",[28,29,30],"signal-quality","branch-metrics","decision-making","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":39,"category":31,"deletable":33,"connectable":8},"node_input","Incoming message",[23,38],0,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":45,"category":50,"deletable":8,"connectable":8},"node_kb_policy","Knowledge base guardrails","knowledge-base-policy",[38,38],{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":46,"activationOpener":47,"personalization":49},"default",{"enabled":8,"instruction":48},"Prioritize practical, non-academic guidance. Focus on: what to trust, what to verify, what usually breaks first, and how to avoid confident wrong decisions.",{"useContactName":33},"response",{"id":52,"name":53,"type":54,"typeVersion":16,"position":55,"parameters":57,"category":50,"deletable":8,"connectable":8},"node_menu","Choose your decision situation","interactive-message",[56,38],260,{"messageType":58,"headerText":59,"bodyText":60,"footerText":61,"sectionTitle":62,"buttons":63,"ctaDisplayText":82,"ctaUrl":82},"list","Signal triage","What are you trying to decide right now? Pick the closest match and I’ll give you a short checklist that prevents “looks fine” data from winning the meeting.","Tip: If it’s high-stakes, choose the handoff option.","Decision situations",[64,67,70,73,76,79],{"id":65,"title":66},"branch_numbers","Trust branch numbers",{"id":68,"title":69},"dirty_signal","Spot dirty signal fast",{"id":71,"title":72},"automation_vs_judgment","Automation vs judgment",{"id":74,"title":75},"compare_branches","Branches & attribution",{"id":77,"title":78},"signal_culture","Build signal culture",{"id":80,"title":81},"handoff","Talk to a person","",{"id":84,"name":85,"type":86,"typeVersion":16,"position":87,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_branch_numbers","If: branch numbers","if",[88,89],520,-180,{"buttonId":65,"operator":91},"equals","routing",{"id":94,"name":95,"type":96,"typeVersion":16,"position":97,"parameters":99,"category":50,"deletable":8,"connectable":8},"node_text_branch_numbers","Checklist: trust vs noise","text-message",[98,89],780,{"text":100},"Branch numbers you can trust tend to be boring in the right ways. Here’s the quick trust test:\n\n1) Definition: Can two people compute the metric and get the same answer? If not, it’s a vibe, not a signal.\n2) Coverage: What % of branches/events are missing? “Only the clean ones report” creates heroic dashboards.\n3) Timing: Any backfills or posting delays? If last week keeps changing, don’t treat it like a final score.\n4) Incentives: Who benefits if the number looks good? If comp, rankings, or reputation are involved, assume gaming until proven otherwise.\n5) Denominator sanity: Are we comparing rates with tiny counts? A 50% jump on 4 → 6 is not a strategy.\n6) Outlier drill-down: One branch can fake a trend. Always ask: “Does the median agree with the mean?”\n\nIf the metric fails any of these, keep it—just downgrade it from ‘decision’ to ‘directional.’",{"id":102,"name":103,"type":86,"typeVersion":16,"position":104,"parameters":106,"category":92,"deletable":8,"connectable":8},"node_if_dirty_signal","If: dirty signal",[88,105],-60,{"buttonId":68,"operator":91},{"id":108,"name":109,"type":96,"typeVersion":16,"position":110,"parameters":111,"category":50,"deletable":8,"connectable":8},"node_text_dirty_signal","Checklist: dirty signal tells",[98,105],{"text":112},"Dirty signal usually shows up as “everything looks plausible.” Use these tripwires before the meeting locks in a narrative:\n\n- Sudden step-change: Ask “What changed in the world or the logging?” If nobody can name one, suspect instrumentation.\n- Too-perfect consistency: Real operations are messy. Perfectly smooth lines often mean aggressive filtering.\n- Spiky around deadlines: End-of-month heroics often indicate batch posting, backfills, or manual edits.\n- Mismatched sources: If branch traffic rises but conversations/orders don’t, you may be counting different realities.\n- Missingness with a pattern: If certain branch types are always absent, you’re measuring compliance, not performance.\n\nRule: Don’t ‘clean away’ inconvenient cases until you’ve explained them. Anomalies are often the story, not the error.",{"id":114,"name":115,"type":86,"typeVersion":16,"position":116,"parameters":118,"category":92,"deletable":8,"connectable":8},"node_if_automation","If: automation vs judgment",[88,117],60,{"buttonId":71,"operator":91},{"id":120,"name":121,"type":96,"typeVersion":16,"position":122,"parameters":123,"category":50,"deletable":8,"connectable":8},"node_text_automation","Guide: when to trust automation",[98,117],{"text":124},"When to trust automation (and when to insist on humans):\n\nTrust automation when:\n- The definition is stable and audited (same input → same output).\n- Errors are low-cost and reversible.\n- There’s a clear alert threshold and an owner who responds.\n\nRequire human judgment when:\n- The metric can be gamed (rankings, targets, comps).\n- The decision is irreversible or reputationally expensive.\n- Context matters (local events, staffing, branch constraints) and the model can’t ‘see’ it.\n\nPractical rule: Automate detection and summaries; keep decisions human when incentives, edge cases, or one-way doors appear.",{"id":126,"name":127,"type":86,"typeVersion":16,"position":128,"parameters":130,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[88,129],180,{"buttonId":74,"operator":91},{"id":132,"name":133,"type":96,"typeVersion":16,"position":134,"parameters":135,"category":50,"deletable":8,"connectable":8},"node_text_compare","Checklist: comparisons & attribution",[98,129],{"text":136},"Branch comparisons and attribution are where smart teams repeatedly misread reality. Use this sanity checklist:\n\n1) Like-for-like: Are we comparing similar branch types (traffic, hours, staffing, maturity)? If not, you’re measuring the mix.\n2) Exposure: Did both branches have equal opportunity (campaign reach, inventory, local disruptions)?\n3) Small numbers: Rank-ordering tiny volumes creates fake winners.\n4) Attribution drift: If the rules changed (new channel tagging, new CRM fields), trends aren’t trends.\n5) Conversation bias: The loudest branch often generates the most notes—not necessarily the most truth.\n\nDecision tip: Ask “What would we conclude if we removed the top 1 branch and the bottom 1 branch?” If the story flips, your signal is fragile.",{"id":138,"name":139,"type":86,"typeVersion":16,"position":140,"parameters":142,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: signal culture",[88,141],300,{"buttonId":77,"operator":91},{"id":144,"name":145,"type":96,"typeVersion":16,"position":146,"parameters":147,"category":50,"deletable":8,"connectable":8},"node_text_culture","Playbook: build signal culture",[98,141],{"text":148},"A signal culture that helps decisions happen (not just slides) looks like this:\n\n- One metric, one owner, one definition. If ownership is shared, accountability is imaginary.\n- “Decision first” dashboards: every chart answers a specific decision question, or it doesn’t exist.\n- Default to ranges and confidence, not false precision. Exact numbers are often the least honest part.\n- Pre-mortems for metrics: “How could this number be wrong while looking right?” Write the answers down.\n- Reward truth-telling: branches shouldn’t be punished for reporting messy reality.\n\nWit-with-teeth rule: If a metric’s main job is to impress leadership, it will. That’s the problem.",{"id":150,"name":151,"type":86,"typeVersion":16,"position":152,"parameters":154,"category":92,"deletable":8,"connectable":8},"node_if_handoff","If: talk to a person",[88,153],420,{"buttonId":80,"operator":91},{"id":156,"name":157,"type":158,"typeVersion":16,"position":159,"parameters":160,"category":164,"deletable":8,"connectable":8},"node_fallback_handoff","Human handoff","fallback",[98,153],{"handoffMessage":161,"departmentId":162,"departmentName":163},"Got it—looping in a human. Share the branch, timeframe, and the decision you’re about to make (not just the metric), and we’ll help you stress-test the signal.","dept_support","Support","terminal",{"id":166,"name":167,"type":158,"typeVersion":16,"position":168,"parameters":169,"category":164,"deletable":8,"connectable":8},"node_fallback_default","Default handoff (no match)",[98,88],{"handoffMessage":170,"departmentId":162,"departmentName":163},"I may be missing context. I’m looping in a human—tell us what decision you’re making, what signals you’re using, and what looks ‘too clean’ to be true.",[172,176,178,180,183,186,188,190,192,194,196,198,200,202,204],{"id":173,"source":35,"target":41,"sourceHandle":174,"targetHandle":174,"type":175},"conn_input_to_kb","main","edge",{"id":177,"source":41,"target":52,"sourceHandle":174,"targetHandle":174,"type":175},"conn_kb_to_menu",{"id":179,"source":52,"target":84,"sourceHandle":174,"targetHandle":174,"type":175},"conn_menu_to_if1",{"id":181,"source":84,"target":94,"sourceHandle":182,"targetHandle":174,"type":175},"conn_if1_true_to_text1","true",{"id":184,"source":84,"target":102,"sourceHandle":185,"targetHandle":174,"type":175},"conn_if1_false_to_if2","false",{"id":187,"source":102,"target":108,"sourceHandle":182,"targetHandle":174,"type":175},"conn_if2_true_to_text2",{"id":189,"source":102,"target":114,"sourceHandle":185,"targetHandle":174,"type":175},"conn_if2_false_to_if3",{"id":191,"source":114,"target":120,"sourceHandle":182,"targetHandle":174,"type":175},"conn_if3_true_to_text3",{"id":193,"source":114,"target":126,"sourceHandle":185,"targetHandle":174,"type":175},"conn_if3_false_to_if4",{"id":195,"source":126,"target":132,"sourceHandle":182,"targetHandle":174,"type":175},"conn_if4_true_to_text4",{"id":197,"source":126,"target":138,"sourceHandle":185,"targetHandle":174,"type":175},"conn_if4_false_to_if5",{"id":199,"source":138,"target":144,"sourceHandle":182,"targetHandle":174,"type":175},"conn_if5_true_to_text5",{"id":201,"source":138,"target":150,"sourceHandle":185,"targetHandle":174,"type":175},"conn_if5_false_to_if6",{"id":203,"source":150,"target":156,"sourceHandle":182,"targetHandle":174,"type":175},"conn_if6_true_to_fallback",{"id":205,"source":150,"target":166,"sourceHandle":185,"targetHandle":174,"type":175},"conn_if6_false_to_default_fallback","automation",[28,29,30,208,209],"data-hygiene","attribution",[211],"WhatsApp","intermediate","Calypso","2026-08-04T11:04:36.733Z","/en/workflows/decisionready-signal-checkpoints",{"en":215},{"title":9,"description":218,"ogDescription":219,"twitterDescription":220,"canonicalPath":215,"robots":221,"schemaType":222,"alternates":223},"Route teams to practical checklists that separate trustworthy branch signals from noise, catch dirty data early, and guide automation vs judgment.","A guided signal triage flow: spot dirty metrics, avoid attribution traps, and decide when automation is safe—before confident meetings go off the rails.","Turn messy branch signals into decision ready checkpoints: trust tests, dirty data tells, attribution sanity checks, and when humans must override automation.","index,follow","HowTo",[224],{"hreflang":6,"href":215},1785947665961]