[{"data":1,"prerenderedAt":309},["ShallowReactive",2],{"/en/workflows/signal-decision-field-guide":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":289,"tags":290,"integrations":293,"difficulty":296,"author":297,"verified":34,"featured":34,"date":298,"modified":298,"icon":7,"imageSrc":7,"path":299,"alternates":300,"seo":301},"5da9c7ce-4628-4838-b11e-3fae6b4bafea","signal-decision-field-guide","en",null,true,"Signal Decision Field Guide","A practical decision coach that helps operators sanity-check branch metrics, spot dirty signals early, and choose when to trust automation versus human judgment—before a confident meeting makes a confident mistake.","## How it works\nThis workflow acts like an on-demand “signal advisor” inside your messaging channel. It uses your knowledge base first (if you’ve documented internal definitions and metrics), then routes people through a short menu of decision-shaped checks—so they can quickly figure out what to trust, what to verify, and what’s probably polished noise.\n\nIt’s designed for the real world where bad data looks normal until the moment it wins an argument. Each path gives crisp guardrails (what to check, what usually breaks first, and what to do next) and offers a fast handoff to a human when the situation needs judgment.\n\n## Key features\n- Knowledge-base-first responses, then routing into a practical decision menu\n- Interactive menu covers branch numbers, dirty signals, automation vs. judgment, messy evidence, comparisons, and culture\n- “Another check?” follow-up to keep the conversation moving without starting over\n- Optional human handoff for cases that shouldn’t be automated\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow (message entry point).\n2. **Knowledge base policy:** Calypso attempts to answer using your knowledge base; if it can’t, the workflow continues into the guided menu.\n3. **Decision menu:** The user chooses a topic (e.g., *Which numbers deserve trust?*).\n4. **Routing:** The workflow matches the selected button and sends a focused, operator-friendly checklist.\n5. **Next action:** The user can either go back to the menu for another check or request a human handoff.\n6. **Handoff (optional):** If selected, the workflow sends a handoff message and routes to the designated team.\n\n## Setup requirements\n- No credentials required.\n- (Optional) Populate your Calypso knowledge base with your internal metric definitions, branch reporting rules, and attribution conventions to make the first step more useful.\n- Configure your Calypso messaging entry point on **WhatsApp** or **Web chat** (whichever channels you use).",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":228,"routingEnabled":8,"active":34},"wf_signal_decision_field_guide_v1","calypso-public-library","1.0.0",1,[18,35,41,53,87,97,105,111,117,122,128,134,140,146,152,157,163,169,175,192,198,205,211,221],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":33,"deletable":34,"connectable":34},"fc1","Workflow settings","flow-configs",[23,24],-120,40,{"name":9,"description":26,"tags":27,"triggerType":32},"Knowledge-base-first decision coaching for branch signals, dirty data detection, automation vs judgment, comparisons, and signal culture.",[28,29,30,31],"signal-quality","decision-making","branch-metrics","data-hygiene","input","policy",false,{"id":36,"name":37,"type":32,"typeVersion":16,"position":38,"parameters":40,"category":32,"deletable":34,"connectable":8},"in1","Entry point",[23,39],200,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"kb1","Knowledge base first","knowledge-base-policy",[46,39],120,{"enabled":8,"fallbackToRouting":8,"sticky":34,"stickyMode":48,"activationOpener":49,"personalization":51},"default",{"enabled":8,"instruction":50},"Answer from the knowledge base if it clearly applies (definitions, metric rules, attribution conventions). If the request is ambiguous or needs judgment, continue to the menu and keep it practical—no academic jargon.",{"useContactName":34},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"im1","Choose a decision check","interactive-message",[58,39],380,{"messageType":60,"headerText":9,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":86,"ctaUrl":86},"list","Pick what you’re deciding. I’ll give you fast checks to separate decision-grade signal from polished noise.","If it can’t take 2 questions, it’s décor.","Decision checks",[65,68,71,74,77,80,83],{"id":66,"title":67},"trust_branch_numbers","Trustworthy numbers",{"id":69,"title":70},"spot_dirty_signal","Spot dirty signal",{"id":72,"title":73},"automation_vs_judgment","Automation or human?",{"id":75,"title":76},"messy_evidence","Messy → insight",{"id":78,"title":79},"compare_branches_attr","Compare branches",{"id":81,"title":82},"build_signal_culture","Signal culture",{"id":84,"title":85},"talk_to_human","Talk to a human","",{"id":88,"name":89,"type":90,"typeVersion":16,"position":91,"parameters":94,"category":96,"deletable":8,"connectable":8},"if1","If: trust branch numbers","if",[92,93],660,80,{"buttonId":66,"operator":95},"equals","routing",{"id":98,"name":99,"type":100,"typeVersion":16,"position":101,"parameters":103,"category":52,"deletable":8,"connectable":8},"tx1","Trust tests for branch numbers","text-message",[102,93],940,{"text":104},"**Branch numbers that deserve trust usually have three things:**\n1) **A definition with teeth** (what’s included/excluded, and where it’s measured).\n2) **A stable collection path** (same system, same timing, no “helpful” manual edits).\n3) **A known failure mode** (you can name how it breaks, and you watch for it).\n\n**Quick reality checks:**\n- Ask: *“What would make this number wrong by 20%?”* If nobody can answer, it’s fragile.\n- Look for **sudden smoothness** (perfectly tidy trends are often human-made).\n- Compare to a **stubborn reference** (cash, inventory, staffing hours, ticket volume). If the story only works in one dataset, be suspicious.\n\n**Rule of thumb:** If a metric can’t be audited in under an hour, it’s not decision-grade for weekly branch calls.",{"id":106,"name":107,"type":90,"typeVersion":16,"position":108,"parameters":110,"category":96,"deletable":8,"connectable":8},"if2","If: spot dirty signal",[92,109],140,{"buttonId":69,"operator":95},{"id":112,"name":113,"type":100,"typeVersion":16,"position":114,"parameters":115,"category":52,"deletable":8,"connectable":8},"tx2","Dirty signal early warnings",[102,109],{"text":116},"**Dirty signal doesn’t look like garbage. It looks like confidence.** Here are the early warnings before a meeting goes off the rails:\n\n**Red flags that show up first:**\n- **Timing weirdness:** big swings that start exactly when reporting changed, incentives changed, or a new dashboard launched.\n- **Category drift:** the same label quietly starts meaning something else (e.g., “new customer” becomes “new-to-CRM”).\n- **One-branch miracles:** a single branch “solves” the business overnight with no operational explanation.\n- **Convenient missingness:** the hardest-to-measure segments disappear right when scrutiny rises.\n\n**Two questions that save you:**\n1) *“What did we stop counting?”*\n2) *“What could someone do to improve this number without improving reality?”*\n\nIf those questions cause discomfort, good. That’s the signal working.",{"id":118,"name":119,"type":90,"typeVersion":16,"position":120,"parameters":121,"category":96,"deletable":8,"connectable":8},"if3","If: automation vs judgment",[92,39],{"buttonId":72,"operator":95},{"id":123,"name":124,"type":100,"typeVersion":16,"position":125,"parameters":126,"category":52,"deletable":8,"connectable":8},"tx3","When to trust automation",[102,39],{"text":127},"**Trust automation when:**\n- The decision is **reversible** (you can undo damage cheaply).\n- The inputs are **instrumented**, not “reported” (captured by systems, not argued into existence).\n- The environment is **stable** (rules haven’t changed this month).\n\n**Demand human judgment when:**\n- The metric is **gameable** (people can win the number while losing the mission).\n- The decision is **one-way** (pricing, staffing cuts, branch closures).\n- The data is **thin or newly defined** (fresh KPI + big consequences = classic failure).\n\n**Practical pattern:** Automate the *default*, and create a clear “manual review” lane for edge cases. If you can’t describe the edge cases, you haven’t earned automation yet.",{"id":129,"name":130,"type":90,"typeVersion":16,"position":131,"parameters":133,"category":96,"deletable":8,"connectable":8},"if4","If: messy evidence",[92,132],260,{"buttonId":75,"operator":95},{"id":135,"name":136,"type":100,"typeVersion":16,"position":137,"parameters":138,"category":52,"deletable":8,"connectable":8},"tx4","Messy evidence to insight",[102,132],{"text":139},"**Don’t “clean” away the truth. Contain the mess instead.**\n\n**Use this sequence:**\n1) **Triage**: split inputs into *reliable*, *useful-but-sketchy*, and *story-only*.\n2) **Name the bias**: what would this method systematically miss (or overcount)?\n3) **Keep contradictions visible**: conflicting signals are information—don’t average them into silence.\n4) **Anchor on decisions**: ask *“What would we do differently if this were true?”* If nothing changes, stop polishing.\n\n**Best practice:** Keep a short “notes on weirdness” alongside the metric. Future-you will thank you when the number ‘mysteriously’ shifts.",{"id":141,"name":142,"type":90,"typeVersion":16,"position":143,"parameters":145,"category":96,"deletable":8,"connectable":8},"if5","If: compare branches & attribution",[92,144],320,{"buttonId":78,"operator":95},{"id":147,"name":148,"type":100,"typeVersion":16,"position":149,"parameters":150,"category":52,"deletable":8,"connectable":8},"tx5","Branch comparisons & attribution traps",[102,144],{"text":151},"**Branch comparisons fail for boring reasons—then become confident for expensive reasons.**\n\n**Common traps:**\n- **Mix-shift:** Branch A “improves” because its customer mix changed, not its execution.\n- **Lead/lag confusion:** one branch books revenue now; another records it later. Looks like performance. It’s bookkeeping.\n- **Selective visibility:** branches with better tooling look better because they’re measured better.\n- **Attribution inflation:** the same outcome gets credited multiple times across channels or teams.\n\n**Make comparisons fair fast:**\n- Compare **rate + volume** (percentages alone hide tiny denominators).\n- Normalize for **exposure** (traffic, staffing hours, call volume).\n- Require one **operational mechanism**: *“What did the branch do differently on Tuesday?”* If you can’t answer, it may be noise.",{"id":153,"name":154,"type":90,"typeVersion":16,"position":155,"parameters":156,"category":96,"deletable":8,"connectable":8},"if6","If: build signal culture",[92,58],{"buttonId":81,"operator":95},{"id":158,"name":159,"type":100,"typeVersion":16,"position":160,"parameters":161,"category":52,"deletable":8,"connectable":8},"tx6","Build a signal culture",[102,58],{"text":162},"**A healthy signal culture makes decisions happen—slides are a side effect.**\n\n**Small habits that work:**\n- **One owner per metric** (not one committee). Owners define it, monitor drift, and publish known issues.\n- **Pre-mortem questions in every review:** *“How could this be wrong?”* and *“How could this be gamed?”*\n- **Decision logs:** write down the metric, the call you made, and what you expected. Accountability beats debate.\n- **Celebrate honest bad news:** it’s cheaper than fake good news.\n\n**Wit-sized truth:** If your dashboard can’t survive a curious intern with a spreadsheet, it’s not governance—it’s theater.",{"id":164,"name":165,"type":90,"typeVersion":16,"position":166,"parameters":168,"category":96,"deletable":8,"connectable":8},"if7","If: talk to a human",[92,167],440,{"buttonId":84,"operator":95},{"id":170,"name":171,"type":100,"typeVersion":16,"position":172,"parameters":173,"category":52,"deletable":8,"connectable":8},"tx7","Handoff note",[102,167],{"text":174},"You’re right to escalate. Some calls need judgment, context, and a real back-and-forth. I can route this to a human reviewer next.",{"id":176,"name":177,"type":56,"typeVersion":16,"position":178,"parameters":181,"category":52,"deletable":8,"connectable":8},"im2","What next?",[179,180],1220,220,{"messageType":182,"headerText":183,"bodyText":184,"footerText":86,"sectionTitle":86,"buttons":185,"ctaDisplayText":86,"ctaUrl":86},"button","Next step","Want another check, or do you want a human to look at the situation?",[186,189],{"id":187,"title":188},"back_to_menu","Another check",{"id":190,"title":191},"handoff_human","Human review",{"id":193,"name":194,"type":90,"typeVersion":16,"position":195,"parameters":197,"category":96,"deletable":8,"connectable":8},"if8","If: another check",[196,39],1500,{"buttonId":187,"operator":95},{"id":199,"name":200,"type":100,"typeVersion":16,"position":201,"parameters":203,"category":52,"deletable":8,"connectable":8},"tx9","How to run another check",[202,39],1780,{"text":204},"To run another check, start a new message and type **menu** (or reopen the guide from your entry point). Keeps the advice clean and avoids half-states.",{"id":206,"name":207,"type":90,"typeVersion":16,"position":208,"parameters":210,"category":96,"deletable":8,"connectable":8},"if9","If: handoff human",[196,209],280,{"buttonId":190,"operator":95},{"id":212,"name":213,"type":214,"typeVersion":16,"position":215,"parameters":216,"category":220,"deletable":8,"connectable":8},"fb1","Handoff to Insights Ops","fallback",[202,209],{"handoffMessage":217,"departmentId":218,"departmentName":219},"Got it. I’m routing this to the Insights Ops team for a human review. Please share: (1) the branch(es), (2) the metric or question, (3) the time window, and (4) what decision is on the line.","insights-ops","Insights Ops","terminal",{"id":222,"name":223,"type":100,"typeVersion":16,"position":224,"parameters":226,"category":52,"deletable":8,"connectable":8},"tx8","Unrecognized choice",[202,225],360,{"text":227},"I didn’t catch that selection. If you still want a human review, choose **Human review**. Otherwise start a new message and type **menu**.",[229,231,233,235,238,241,243,245,247,249,251,253,255,257,259,261,263,265,267,269,271,273,275,277,279,281,283,285,287],{"id":230,"source":36,"target":42,"sourceHandle":48,"targetHandle":48,"type":48},"c1",{"id":232,"source":42,"target":54,"sourceHandle":48,"targetHandle":48,"type":48},"c2",{"id":234,"source":54,"target":88,"sourceHandle":48,"targetHandle":48,"type":48},"c3",{"id":236,"source":88,"target":98,"sourceHandle":237,"targetHandle":48,"type":48},"c4","true",{"id":239,"source":88,"target":106,"sourceHandle":240,"targetHandle":48,"type":48},"c5","false",{"id":242,"source":106,"target":112,"sourceHandle":237,"targetHandle":48,"type":48},"c6",{"id":244,"source":106,"target":118,"sourceHandle":240,"targetHandle":48,"type":48},"c7",{"id":246,"source":118,"target":123,"sourceHandle":237,"targetHandle":48,"type":48},"c8",{"id":248,"source":118,"target":129,"sourceHandle":240,"targetHandle":48,"type":48},"c9",{"id":250,"source":129,"target":135,"sourceHandle":237,"targetHandle":48,"type":48},"c10",{"id":252,"source":129,"target":141,"sourceHandle":240,"targetHandle":48,"type":48},"c11",{"id":254,"source":141,"target":147,"sourceHandle":237,"targetHandle":48,"type":48},"c12",{"id":256,"source":141,"target":153,"sourceHandle":240,"targetHandle":48,"type":48},"c13",{"id":258,"source":153,"target":158,"sourceHandle":237,"targetHandle":48,"type":48},"c14",{"id":260,"source":153,"target":164,"sourceHandle":240,"targetHandle":48,"type":48},"c15",{"id":262,"source":164,"target":170,"sourceHandle":237,"targetHandle":48,"type":48},"c16",{"id":264,"source":164,"target":176,"sourceHandle":240,"targetHandle":48,"type":48},"c17",{"id":266,"source":98,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c18",{"id":268,"source":112,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c19",{"id":270,"source":123,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c20",{"id":272,"source":135,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c21",{"id":274,"source":147,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c22",{"id":276,"source":158,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c23",{"id":278,"source":170,"target":176,"sourceHandle":48,"targetHandle":48,"type":48},"c24",{"id":280,"source":176,"target":193,"sourceHandle":48,"targetHandle":48,"type":48},"c25",{"id":282,"source":193,"target":199,"sourceHandle":237,"targetHandle":48,"type":48},"c26",{"id":284,"source":193,"target":206,"sourceHandle":240,"targetHandle":48,"type":48},"c27",{"id":286,"source":206,"target":212,"sourceHandle":237,"targetHandle":48,"type":48},"c28",{"id":288,"source":206,"target":222,"sourceHandle":240,"targetHandle":48,"type":48},"c29","automation",[28,29,30,31,291,292],"attribution","ops-coaching",[294,295],"WhatsApp","Web chat","intermediate","Calypso","2026-06-20T11:04:00.882Z","/en/workflows/signal-decision-field-guide",{"en":299},{"title":9,"description":302,"ogDescription":303,"twitterDescription":304,"canonicalPath":299,"robots":305,"schemaType":306,"alternates":307},"Route messy branch signals into decision ready checks: trust tests, dirty signal spotting, automation vs judgment, and fast human handoff.","A practical workflow to sanity check branch metrics, spot dirty signals early, and decide when automation is safe vs when humans must weigh in.","Turn messy signals into decision ready checks: what to trust, what to verify, and when to escalate to human judgment—before meetings go off the rails.","index,follow","HowTo",[308],{"hreflang":6,"href":299},1785947669062]