[{"data":1,"prerenderedAt":234},["ShallowReactive",2],{"/en/workflows/signal-to-decision-field-guide":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":212,"tags":213,"integrations":217,"difficulty":220,"author":221,"verified":32,"featured":32,"date":222,"modified":222,"icon":7,"imageSrc":7,"path":223,"alternates":224,"seo":225},"9a2fac61-c117-4f75-88bd-49effd706335","signal-to-decision-field-guide","en",null,true,"Signal-to-Decision Field Guide","A practical coaching flow that helps teams separate trustworthy branch signals from polished noise—before decisions get locked in.","## How it works\nThis workflow is a guided “signal check” assistant for leaders and operators who have to make branch-level decisions from messy inputs: dashboards, conversations, local events, and attribution reports that look clean right up until they’re wrong.\n\nIt starts by pulling helpful context from your Knowledge Base, then asks the user what kind of decision they’re facing. Each path gives a short, decision-shaped checklist: what to trust, what to doubt, and what usually breaks first—so your next meeting is about reality, not confident slides.\n\n## Key features\n- Uses your Calypso Knowledge Base first, then routes users into focused decision checklists.\n- Interactive menu with six practical “signal situations” (trust, dirtiness, automation vs judgment, messy evidence, comparisons, culture).\n- Each checklist ends by sending the user back to the menu for quick follow-up checks.\n- Built-in fallback to route to a human team when the situation needs judgment or escalation.\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a user opens the flow (Input).\n2. **Knowledge grounding:** The **Knowledge Base Policy** applies your stored guidance (definitions, metrics conventions, branch reporting rules) to keep advice consistent.\n3. **Choose a situation:** The user receives an **interactive list** to pick what they need help with (e.g., “Which branch numbers deserve trust?”).\n4. **Route to the right checklist:** A sequence of **IF** nodes matches the selected button id and routes accordingly.\n5. **Deliver the checklist:** A **text message** provides a practical, decision-ready checklist for that situation.\n6. **Loop for more:** After the checklist, the flow returns to the main menu so the user can run another check.\n7. **Escalate when needed:** If the selection can’t be matched, the flow uses **Fallback** to hand off to **Analytics Operations**.\n\n## Setup requirements\n- **Calypso Knowledge Base:** Recommended (this workflow is designed to use it). No additional credentials are required.\n- **WhatsApp channel in Calypso:** Required to send interactive list messages and text responses.\n- **Operational readiness:** If you keep the handoff enabled, ensure the **Analytics Operations** department exists to receive escalations.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":177,"routingEnabled":8,"active":32},"wf_signal_to_decision_field_guide","calypso-public-library","1.0.0",1,[18,33,40,52,84,93,102,108,115,121,127,133,140,146,153,159,166],{"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},"Guided signal checks for branch decisions: trust vs noise, dirty signal spotting, automation vs judgment, comparisons, attribution, and culture.",[27,28,29],"signal-quality","decision-systems","branch-performance","input","policy",false,{"id":34,"name":35,"type":30,"typeVersion":16,"position":36,"parameters":39,"category":30,"deletable":32,"connectable":8},"node_input","Start",[37,38],240,200,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node_kb_policy","Knowledge base guidance","knowledge-base-policy",[45,38],460,{"enabled":8,"fallbackToRouting":8,"sticky":32,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"You’re about to make a decision from signals that look neat on a dashboard. I’ll help you sanity-check what’s real, what’s noisy, and what to verify before the meeting gets confident.",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_menu","Pick a signal check","interactive-message",[57,38],700,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":83,"ctaUrl":83},"list","Signal-to-decision checks","Choose what you’re trying to decide. I’ll give a practical checklist—no academic fog, no fake certainty.","Tip: 'Always up' may mean logging changed, not reality.","Choose a topic",[65,68,71,74,77,80],{"id":66,"title":67},"trust_branch_numbers","Trust branch numbers",{"id":69,"title":70},"spot_dirty_signal","Spot dirty signals",{"id":72,"title":73},"automation_vs_judgment","Automation vs humans",{"id":75,"title":76},"messy_evidence_to_insight","Messy to insight",{"id":78,"title":79},"compare_branches_attribution","Branches & attribution",{"id":81,"title":82},"signal_culture","Build signal culture","",{"id":85,"name":86,"type":87,"typeVersion":16,"position":88,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_trust","If: Trust branch numbers","if",[89,38],940,{"buttonId":66,"operator":91},"equals","routing",{"id":94,"name":95,"type":96,"typeVersion":16,"position":97,"parameters":100,"category":51,"deletable":8,"connectable":8},"node_text_trust","Checklist: Trustworthy numbers","text-message",[98,99],1180,120,{"text":101},"Trust the *branch number* only after these quick checks:\n\n1) **Definition stability:** Did the metric definition change in the last 4–8 weeks (filters, eligibility, “active” rules)? If yes, treat the jump as “measurement change” until proven otherwise.\n2) **Denominator sanity:** Is the denominator moving (opened hours, staffing, lead volume, footfall)? A stable rate can hide a collapsing base.\n3) **Coverage:** What % of real activity is captured? Missing channels often look like “improvement.”\n4) **Lag & backfill:** Is it real-time, next-day, or backfilled? If it backfills, don’t celebrate Tuesday until Friday.\n5) **Cross-check:** One independent check (e.g., operational logs vs dashboard) beats five correlated charts.\n\nIf you can’t state the definition and data coverage in one sentence, you’re not holding a number—you’re holding a story.",{"id":103,"name":104,"type":87,"typeVersion":16,"position":105,"parameters":107,"category":92,"deletable":8,"connectable":8},"node_if_dirty","If: Spot dirty signal",[89,106],340,{"buttonId":69,"operator":91},{"id":109,"name":110,"type":96,"typeVersion":16,"position":111,"parameters":113,"category":51,"deletable":8,"connectable":8},"node_text_dirty","Checklist: Dirty signal detectors",[98,112],300,{"text":114},"Dirty signal usually shows up as *plausible* numbers with suspicious behavior. Look for:\n\n- **Step-changes at midnight / Mondays / month-end:** Often a pipeline job, policy change, or threshold—not customer behavior.\n- **Perfectly smooth curves:** Real branches are lumpy. Too-smooth often means aggregation, imputation, or filtered exceptions.\n- **One-branch miracles:** If one branch “fixed performance” without any operational change, check tagging, routing, or logging first.\n- **Missingness with manners:** Nulls that appear only on weekends, only for one channel, or only after a release.\n- **Attribution that always agrees with the narrative:** The best lie is a consistent one.\n\nMeeting-saving move: ask “What would we expect to see if this is *wrong*?” Then look for that pattern before you decide.",{"id":116,"name":117,"type":87,"typeVersion":16,"position":118,"parameters":120,"category":92,"deletable":8,"connectable":8},"node_if_auto","If: Automation vs judgment",[89,119],480,{"buttonId":72,"operator":91},{"id":122,"name":123,"type":96,"typeVersion":16,"position":124,"parameters":125,"category":51,"deletable":8,"connectable":8},"node_text_auto","Checklist: When to trust automation",[98,119],{"text":126},"Trust automation when:\n- The decision is **reversible** (you can undo it cheaply).\n- The inputs are **well-instrumented** (coverage is known; missingness is monitored).\n- The metric has **clear failure alarms** (you’ll know quickly when it’s wrong).\n- The outcome is **local** (one branch/process), not a company-wide bet.\n\nUse human judgment when:\n- The data can be gamed or Goodharted (people respond to measurement).\n- The signal depends on context (weather, staffing shocks, local events).\n- The consequence is irreversible (pricing, closures, policy changes).\n\nRule of thumb: automate the *boring repeatables*; keep humans for *exceptions and trade-offs*—the things that make you unpopular for 10 minutes but right for 12 months.",{"id":128,"name":129,"type":87,"typeVersion":16,"position":130,"parameters":132,"category":92,"deletable":8,"connectable":8},"node_if_messy","If: Messy evidence to insight",[89,131],620,{"buttonId":75,"operator":91},{"id":134,"name":135,"type":96,"typeVersion":16,"position":136,"parameters":138,"category":51,"deletable":8,"connectable":8},"node_text_messy","Checklist: Don’t clean away the truth",[98,137],660,{"text":139},"How to turn messy evidence into usable insight *without polishing it into fiction*:\n\n1) **Separate ‘messy’ from ‘wrong’:** Outliers can be errors—or the only real signal you’ve got.\n2) **Keep raw + interpreted side-by-side:** If you can’t show the raw trace, your conclusion is a vibe.\n3) **Name the missingness:** Who/what isn’t captured (channel, shift, device, segment)? Missingness is a finding.\n4) **Use ‘triangulation’ not ‘averaging’:** Two imperfect sources that fail differently are more valuable than one “clean” source.\n5) **Write a decision note:** “We believe X because A+B; we’d change our mind if we saw C.”\n\nCleaning that deletes the uncomfortable parts doesn’t reduce noise—it deletes learning.",{"id":141,"name":142,"type":87,"typeVersion":16,"position":143,"parameters":145,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: Compare branches & attribution",[89,144],760,{"buttonId":78,"operator":91},{"id":147,"name":148,"type":96,"typeVersion":16,"position":149,"parameters":151,"category":51,"deletable":8,"connectable":8},"node_text_compare","Checklist: Comparisons & attribution traps",[98,150],840,{"text":152},"What teams repeatedly misread when comparing branches, conversations, and attribution:\n\n- **Different baselines:** Branches differ in demand, staffing, and constraints. Compare *changes* (before/after) more than raw levels.\n- **Selection effects:** The “best” branch might just get easier customers or cleaner leads.\n- **Channel mix:** A branch with more walk-ins vs more online will ‘win’ different metrics.\n- **Attribution inflation:** If you credit every touch, everyone looks like a hero. Decide what ‘credit’ is for: budgeting, learning, or accountability.\n- **Conversation ≠ outcome:** A high contact rate can mean great service—or broken self-serve.\n\nGood comparison question: “If we swapped the leads and staffing between Branch A and B, would the ranking stay the same?” If not, you’re ranking context, not performance.",{"id":154,"name":155,"type":87,"typeVersion":16,"position":156,"parameters":158,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: Build signal culture",[89,157],900,{"buttonId":81,"operator":91},{"id":160,"name":161,"type":96,"typeVersion":16,"position":162,"parameters":164,"category":51,"deletable":8,"connectable":8},"node_text_culture","Checklist: Signal culture that decides",[98,163],1020,{"text":165},"Build a signal culture that helps decisions happen (not just decks):\n\n- **One owner per metric:** Not to ‘control the story’—to own definitions, coverage, and known failure modes.\n- **Decision-first reporting:** Every chart answers: “What would we do differently if this moved?” If nothing, it’s trivia.\n- **Pre-mortems for metrics:** Write how the metric could lie (instrumentation change, gaming, missingness) before it does.\n- **Escalation is a feature:** Make it normal to say “We don’t know yet,” then assign the next check.\n- **Reward good questions:** Teams that fear looking dumb will produce gorgeous noise.\n\nWit meets truth: the slide that ‘tells the story’ is often the slide that ends the investigation.",{"id":167,"name":168,"type":169,"typeVersion":16,"position":170,"parameters":172,"category":176,"deletable":8,"connectable":8},"node_fallback","Escalate to Analytics Operations","fallback",[98,171],210,{"handoffMessage":173,"departmentId":174,"departmentName":175},"I can’t confidently route that selection. I’m handing this to Analytics Operations so you don’t make a confident wrong decision on a mystery signal.","dept_analytics_ops","Analytics Operations","terminal",[178,182,184,186,189,192,194,196,198,200,202,204,206,208,210],{"id":179,"source":34,"target":41,"sourceHandle":180,"targetHandle":180,"type":181},"conn_input_to_kb","main","smoothstep",{"id":183,"source":41,"target":53,"sourceHandle":180,"targetHandle":180,"type":181},"conn_kb_to_menu",{"id":185,"source":53,"target":85,"sourceHandle":180,"targetHandle":180,"type":181},"conn_menu_to_if_trust",{"id":187,"source":85,"target":94,"sourceHandle":188,"targetHandle":180,"type":181},"conn_if_trust_true_to_text","true",{"id":190,"source":85,"target":103,"sourceHandle":191,"targetHandle":180,"type":181},"conn_if_trust_false_to_if_dirty","false",{"id":193,"source":103,"target":109,"sourceHandle":188,"targetHandle":180,"type":181},"conn_if_dirty_true_to_text",{"id":195,"source":103,"target":116,"sourceHandle":191,"targetHandle":180,"type":181},"conn_if_dirty_false_to_if_auto",{"id":197,"source":116,"target":122,"sourceHandle":188,"targetHandle":180,"type":181},"conn_if_auto_true_to_text",{"id":199,"source":116,"target":128,"sourceHandle":191,"targetHandle":180,"type":181},"conn_if_auto_false_to_if_messy",{"id":201,"source":128,"target":134,"sourceHandle":188,"targetHandle":180,"type":181},"conn_if_messy_true_to_text",{"id":203,"source":128,"target":141,"sourceHandle":191,"targetHandle":180,"type":181},"conn_if_messy_false_to_if_compare",{"id":205,"source":141,"target":147,"sourceHandle":188,"targetHandle":180,"type":181},"conn_if_compare_true_to_text",{"id":207,"source":141,"target":154,"sourceHandle":191,"targetHandle":180,"type":181},"conn_if_compare_false_to_if_culture",{"id":209,"source":154,"target":160,"sourceHandle":188,"targetHandle":180,"type":181},"conn_if_culture_true_to_text",{"id":211,"source":154,"target":167,"sourceHandle":191,"targetHandle":180,"type":181},"conn_if_culture_false_to_fallback","automation",[27,28,29,214,215,216],"attribution","data-hygiene","leadership-ops",[218,219],"WhatsApp","Calypso Knowledge Base","intermediate","Calypso","2026-04-17T11:04:27.309Z","/en/workflows/signal-to-decision-field-guide",{"en":223},{"title":226,"description":227,"ogDescription":228,"twitterDescription":229,"canonicalPath":223,"robots":230,"schemaType":231,"alternates":232},"Signal to Decision Field Guide","Turn messy branch signals into decision ready checks. Spot polished noise, dirty data, and when automation needs human judgment.","A practical workflow for leaders: trust the right branch numbers, catch dirty signals early, and choose when to rely on automation vs judgment.","Stop confident wrong decisions. Use this signal to decision guide to spot noise, validate branch metrics, and know when humans must step in.","index,follow","HowTo",[233],{"hreflang":6,"href":223},1776877119303]