[{"data":1,"prerenderedAt":224},["ShallowReactive",2],{"/en/workflows/branch-signal-decision-field-guide":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":204,"tags":205,"integrations":209,"difficulty":211,"author":212,"verified":33,"featured":33,"date":213,"modified":213,"icon":7,"imageSrc":7,"path":214,"alternates":215,"seo":216},"e355d964-5275-4ac8-8a22-3edd465e1365","branch-signal-decision-field-guide","en",null,true,"Branch Signal Decision Field Guide","An interactive decision helper that turns messy branch metrics, conversations, and attribution into practical next steps—before polished noise creates confident wrong decisions.","## How it works\nThis workflow acts like a “meeting-safe” signal advisor: it answers the real questions people ask right before decisions get made—Which numbers can we trust? What’s probably dirty? When should we let automation run?—without turning it into an academic lecture.\n\nIt starts with a Knowledge Base step to ground responses in your team’s agreed definitions (what counts as a lead, how branches are compared, what attribution model is official). Then it routes users through a button-based menu into short, decision-shaped guidance and checks. Each answer loops back to the menu so leaders can pressure-test multiple angles quickly.\n\n## Key features\n- Knowledge Base–first responses to keep definitions consistent before routing into guidance.\n- Button menu for fast triage (trustworthy branch numbers, dirty signals, automation vs judgment, attribution comparisons, and signal culture).\n- “One-screen” reality checks designed to catch polished noise before it gets slide-deck authority.\n- Loops back to the menu after each answer so users can run multiple checks in one session.\n- Optional human handoff to an Analytics Ops / Data team when a decision is high-stakes or the signal is disputed.\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow.\n2. **Knowledge Base policy:** The workflow consults your Knowledge Base to align on definitions and avoid “same word, different metric” problems.\n3. **Decision menu:** The user chooses what they need:\n   - **Which branch numbers deserve trust**\n   - **How to spot dirty signal**\n   - **Automation vs human judgment**\n   - **Comparing branches, conversations, and attribution**\n   - **Building a signal culture (decisions, not slides)**\n   - **Talk to Analytics Ops**\n4. **Guidance response:** The workflow sends a focused checklist and practical advice for the selected path.\n5. **Repeat or hand off:** After most answers, the workflow returns to the menu. If the user selects **Talk to Analytics Ops**, it hands off to the configured department.\n\n## Setup requirements\n- **Calypso Knowledge Base:** Recommended (this workflow assumes you have at least basic metric definitions and reporting rules documented).\n- **Department routing:** If you want human handoff, ensure the **Analytics Ops** (or equivalent) department exists in Calypso and update the department ID/name in the fallback node.\n- **Credentials:** None required.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":170,"routingEnabled":8,"active":33},"wf-branch-signal-decision-field-guide","calypso-public-library","1.0.0",1,[18,34,40,52,83,93,101,106,112,118,124,129,135,141,147,153,163],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flowcfg","Workflow settings","flow-configs",[23,24],-120,40,{"name":9,"description":26,"tags":27,"triggerType":31},"Interactive helper to vet branch signals, catch dirty data, and decide when to trust 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","Start",[23,38],180,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node_kb","Knowledge base guardrails","knowledge-base-policy",[45,38],120,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"Use our documented definitions first (metrics, attribution, branch comparisons). If definitions are missing, ask clarifying questions before giving advice.",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_menu","Choose a decision check","interactive-message",[57,38],380,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Decision signals, not slide signals","Pick what you’re trying to decide. I’ll help you separate trustworthy branch numbers from polished noise—and catch dirty signal before it wins the meeting.","High-stakes? Choose “Talk to Analytics.”","",[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 human",{"id":75,"title":76},"compare_attribution","Compare & attribute",{"id":78,"title":79},"signal_culture","Signal culture",{"id":81,"title":82},"handoff_analytics_ops","Talk to Analytics",{"id":84,"name":85,"type":86,"typeVersion":16,"position":87,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_trust","If: trust branch numbers","if",[88,89],640,80,{"buttonId":66,"operator":91},"equals","routing",{"id":94,"name":95,"type":96,"typeVersion":16,"position":97,"parameters":99,"category":51,"deletable":8,"connectable":8},"node_text_trust","Trustworthy branch numbers checklist","text-message",[98,89],920,{"text":100},"Here’s what usually deserves trust (and what’s polished noise):\n\nDecision‑grade branch numbers usually have:\n1) A stable definition (same counting rules week to week).\n2) A clear unit of comparison (per‑day, per‑staffed hour, per‑footfall—pick one and stick to it).\n3) Coverage you can explain (who’s included/excluded and why).\n4) Lag awareness (what takes 7/14/30 days to show up).\n5) A known failure mode (what breaks it—POS outage, CRM dedupe changes, staffing gaps).\n\nPolished noise often looks like:\n- Big % lifts on tiny baselines.\n- “All branches” rollups hiding one branch’s data issue.\n- Metrics that improve when tracking breaks (mysteriously higher conversion with fewer sessions).\n\nPractical move: ask “What would have to be true for this number to be wrong?” If no one can answer, it’s not decision‑grade yet.",{"id":102,"name":103,"type":86,"typeVersion":16,"position":104,"parameters":105,"category":92,"deletable":8,"connectable":8},"node_if_dirty","If: spot dirty signal",[88,38],{"buttonId":69,"operator":91},{"id":107,"name":108,"type":96,"typeVersion":16,"position":109,"parameters":110,"category":51,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal tripwires",[98,38],{"text":111},"Dirty data rarely waves a flag. It usually wears a suit and carries a KPI.\n\nFast tripwires before the meeting goes off the rails:\n- Sudden step-change with no operational story (same staff, same hours, “miracle” lift).\n- A metric moves but its “shadow metrics” don’t (e.g., leads up, appointments flat; or revenue up, transactions flat).\n- One branch becomes an outlier exactly when tracking changed.\n- Missingness that’s non-random (new staff not logging notes; one channel not captured).\n- Attribution “credit” spikes while real capacity constraints stay constant.\n\nTwo questions that save teams:\n1) “Where could this be double-counted?”\n2) “What’s the easiest way this could be under-counted?”\n\nIf either answer is ‘we’re not sure,’ treat the number as directional—not decisive.",{"id":113,"name":114,"type":86,"typeVersion":16,"position":115,"parameters":117,"category":92,"deletable":8,"connectable":8},"node_if_automation","If: automation vs judgment",[88,116],280,{"buttonId":72,"operator":91},{"id":119,"name":120,"type":96,"typeVersion":16,"position":121,"parameters":122,"category":51,"deletable":8,"connectable":8},"node_text_automation","When to trust automation",[98,116],{"text":123},"Automation is great at doing the same thing reliably. It’s terrible at knowing when ‘same thing’ is no longer the right thing.\n\nTrust automation when:\n- The inputs are instrumented and stable (definitions don’t change quietly).\n- The cost of a wrong decision is low or reversible.\n- You have a guardrail metric (automation can’t “win” by breaking measurement).\n\nRequire human judgment when:\n- The decision is high-stakes (staffing, pricing, closures, major reallocations).\n- The data is sparse or newly collected.\n- The metric is easy to game (especially conversation notes and self-reported outcomes).\n- The environment changed (new campaign, new competitor, system migration).\n\nRule of thumb: automate the repeatable action; keep humans on exception handling and measurement integrity.",{"id":125,"name":126,"type":86,"typeVersion":16,"position":127,"parameters":128,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[88,57],{"buttonId":75,"operator":91},{"id":130,"name":131,"type":96,"typeVersion":16,"position":132,"parameters":133,"category":51,"deletable":8,"connectable":8},"node_text_compare","Comparisons & attribution pitfalls",[98,57],{"text":134},"Where teams misread comparisons (over and over):\n\n1) Comparing branches without normalizing\n- Use per‑staffed hour / per‑open day / per‑eligible customer.\n- Otherwise you’re mostly measuring scheduling and footfall.\n\n2) Treating conversation volume as intent\n- More conversations can mean more confusion, more failures, or a broken path—not more demand.\n\n3) Believing attribution is an objective truth\n- Attribution is a policy decision. Pick a model, document it, and stop “model shopping” after the results arrive.\n\n4) Mixing leading and lagging indicators\n- Don’t compare today’s conversation tags to this month’s revenue without acknowledging lag.\n\nPractical move: when two branches ‘tie’ on the headline KPI, compare **error bars**: data completeness, logging behavior, and coverage. The cleanest branch often beats the ‘best’ branch once you adjust for signal quality.",{"id":136,"name":137,"type":86,"typeVersion":16,"position":138,"parameters":140,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: build signal culture",[88,139],480,{"buttonId":78,"operator":91},{"id":142,"name":143,"type":96,"typeVersion":16,"position":144,"parameters":145,"category":51,"deletable":8,"connectable":8},"node_text_culture","Build a signal culture (decisions, not slides)",[98,139],{"text":146},"A healthy signal culture produces decisions quickly—and makes it hard for bad data to cosplay as certainty.\n\nHabits that work:\n- One owner per metric definition (changes are announced, not discovered).\n- A ‘decision log’: what we decided, what we used, what we ignored, and why.\n- Pre-mortems for key KPIs: “How could this number lie to us this week?”\n- Reward people who find measurement flaws (they’re saving you money and embarrassment).\n\nWitty but true: if the only time people ask about data quality is after a decision goes wrong, you don’t have metrics—you have storytelling aids.",{"id":148,"name":149,"type":86,"typeVersion":16,"position":150,"parameters":152,"category":92,"deletable":8,"connectable":8},"node_if_handoff","If: handoff to Analytics Ops",[88,151],580,{"buttonId":81,"operator":91},{"id":154,"name":155,"type":156,"typeVersion":16,"position":157,"parameters":158,"category":162,"deletable":8,"connectable":8},"node_fallback","Handoff: Analytics Ops","fallback",[98,151],{"handoffMessage":159,"departmentId":160,"departmentName":161},"Got it—looping in Analytics Ops for a human read. Please share: which branches, the timeframe, the exact metric(s), and what decision you’re trying to make.","analytics-ops","Analytics Ops","terminal",{"id":164,"name":165,"type":96,"typeVersion":16,"position":166,"parameters":168,"category":51,"deletable":8,"connectable":8},"node_text_nomatch","No selection guidance",[98,167],680,{"text":169},"Tap one of the buttons so I can route you to the right decision check. If this is urgent or high-stakes, choose “Talk to Analytics.”",[171,174,176,178,181,184,186,188,190,192,194,196,198,200,202],{"id":172,"source":35,"target":41,"sourceHandle":63,"targetHandle":63,"type":173},"conn_input_kb","edge",{"id":175,"source":41,"target":53,"sourceHandle":63,"targetHandle":63,"type":173},"conn_kb_menu",{"id":177,"source":53,"target":84,"sourceHandle":63,"targetHandle":63,"type":173},"conn_menu_if_trust",{"id":179,"source":84,"target":94,"sourceHandle":180,"targetHandle":63,"type":173},"conn_if_trust_true_text","true",{"id":182,"source":84,"target":102,"sourceHandle":183,"targetHandle":63,"type":173},"conn_if_trust_false_if_dirty","false",{"id":185,"source":102,"target":107,"sourceHandle":180,"targetHandle":63,"type":173},"conn_if_dirty_true_text",{"id":187,"source":102,"target":113,"sourceHandle":183,"targetHandle":63,"type":173},"conn_if_dirty_false_if_automation",{"id":189,"source":113,"target":119,"sourceHandle":180,"targetHandle":63,"type":173},"conn_if_automation_true_text",{"id":191,"source":113,"target":125,"sourceHandle":183,"targetHandle":63,"type":173},"conn_if_automation_false_if_compare",{"id":193,"source":125,"target":130,"sourceHandle":180,"targetHandle":63,"type":173},"conn_if_compare_true_text",{"id":195,"source":125,"target":136,"sourceHandle":183,"targetHandle":63,"type":173},"conn_if_compare_false_if_culture",{"id":197,"source":136,"target":142,"sourceHandle":180,"targetHandle":63,"type":173},"conn_if_culture_true_text",{"id":199,"source":136,"target":148,"sourceHandle":183,"targetHandle":63,"type":173},"conn_if_culture_false_if_handoff",{"id":201,"source":148,"target":154,"sourceHandle":180,"targetHandle":63,"type":173},"conn_if_handoff_true_fallback",{"id":203,"source":148,"target":164,"sourceHandle":183,"targetHandle":63,"type":173},"conn_if_handoff_false_nomatch","automation",[28,29,30,206,207,208],"dirty-data","attribution","automation-guardrails",[210],"Calypso Knowledge Base","intermediate","Calypso","2026-07-08T11:03:36.816Z","/en/workflows/branch-signal-decision-field-guide",{"en":214},{"title":9,"description":217,"ogDescription":218,"twitterDescription":219,"canonicalPath":214,"robots":220,"schemaType":221,"alternates":222},"Interactive workflow to vet branch metrics, spot dirty signals, and decide when to trust automation vs human judgment—before meetings go wrong.","A practical, button based advisor for trustworthy branch decisions: vet numbers, detect dirty signals, avoid attribution traps, and escalate to Analytics Ops when needed.","Turn messy branch signals into decision ready judgment: trust checks, dirty signal detection, automation guardrails, attribution pitfalls, and optional human handoff.","index,follow","HowTo",[223],{"hreflang":6,"href":214},1785947667529]