[{"data":1,"prerenderedAt":206},["ShallowReactive",2],{"/en/workflows/branch-signal-decision-field-manual":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":186,"tags":187,"integrations":191,"difficulty":193,"author":194,"verified":33,"featured":33,"date":195,"modified":195,"icon":7,"imageSrc":7,"path":196,"alternates":197,"seo":198},"2fc1fa1d-1fc4-44ac-b680-44e78035d0a0","branch-signal-decision-field-manual","en",null,true,"Branch Signal Decision Field Manual","A guided decision workflow that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and choose when automation should (and shouldn’t) drive decisions.","## How it works\nThis workflow turns “we have numbers” into “we can trust this decision.” It starts by offering a quick, practical signal check (via your knowledge base), then routes people into decision-shaped guidance: which branch metrics deserve trust, how to detect dirty signal before the meeting gets confident, and when human judgment should override automated conclusions.\n\nIt’s designed for operators and leaders who don’t need more dashboards—they need fewer wrong calls. The tone is intentionally plainspoken: most bad data looks impressively normal right up until it wins an argument.\n\n## Key features\n- Uses a **Knowledge Base Policy** first, so common “what does this metric mean?” questions get answered before opinions form.\n- Presents a **menu of decision scenarios** (trust, hygiene, automation vs judgment, comparison, culture) via an interactive button message.\n- Routes with **explicit button-based branching** so guidance stays focused and repeatable.\n- Provides **field-tested checks** for denominator problems, definition drift, mix shifts, and attribution traps.\n- Includes a **fallback handoff** for cases that need human review (analytics/ops) instead of more automated certainty.\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow (Input).\n2. **Answer basics first:** The Knowledge Base Policy responds to straightforward questions and primes the conversation for consistent definitions.\n3. **Choose the decision scenario:** The user selects one of five buttons (Interactive Message).\n4. **Route to the right playbook:** Conditional checks (If nodes) detect the selected button and deliver targeted guidance (Text Message).\n5. **Escalate when needed:** If no option matches (or the situation is ambiguous), the workflow routes to a human handoff (Fallback).\n\n## Setup requirements\n- A Calypso Inbox/channel where interactive messages are supported.\n- (Recommended) A populated Calypso Knowledge Base with your branch metric definitions and calculation notes.\n- No external credentials are required for this workflow.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":155,"routingEnabled":8,"active":33},"wf-branch-signal-decision-field-manual","calypso-public-library","1.0.0",1,[18,34,40,52,80,90,98,103,109,115,121,126,132,138,144],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_configs","Workflow settings","flow-configs",[23,24],-120,40,{"name":9,"description":26,"tags":27,"triggerType":31},"Decision-focused guidance to separate trustworthy branch signals from polished noise, spot dirty data early, and choose when automation vs judgment should lead.",[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_policy","Knowledge base: metric definitions first","knowledge-base-policy",[45,38],140,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"Before we debate the number: what exactly is being counted, over what time window, and for which branches?",{"useContactName":33},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_menu","Pick a decision scenario","interactive-message",[57,38],420,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Signal decisions, minus the nonsense","Choose what you’re trying to decide. I’ll give you a quick field guide—practical checks, common traps, and when to escalate to a human.","Tip: If it fails a definition check, it’s a mood.","",[65,68,71,74,77],{"id":66,"title":67},"trust_branch_numbers","Trust numbers",{"id":69,"title":70},"spot_dirty_signal","Dirty signal",{"id":72,"title":73},"automation_vs_judgment","Auto vs judgment",{"id":75,"title":76},"compare_branches_attr","Compare branches",{"id":78,"title":79},"build_signal_culture","Signal culture",{"id":81,"name":82,"type":83,"typeVersion":16,"position":84,"parameters":87,"category":89,"deletable":8,"connectable":8},"node_if_trust","If: Which numbers to trust","if",[85,86],700,60,{"buttonId":66,"operator":88},"equals","routing",{"id":91,"name":92,"type":93,"typeVersion":16,"position":94,"parameters":96,"category":51,"deletable":8,"connectable":8},"node_text_trust","Trust checks for branch numbers","text-message",[95,86],980,{"text":97},"Here’s how to tell “decision-grade” branch numbers from polished noise:\n\n1) **Denominator sanity**: If the denominator changes (eligible customers, open hours, staffing), your rate is lying politely. Ask: *What could change this rate without changing reality?*\n\n2) **Definition drift**: Metrics rot when definitions evolve quietly. If the team can’t state the definition in one sentence, don’t ship decisions on it.\n\n3) **Collection incentives**: Any metric tied to praise, bonus, or “we’ll look good in QBR” invites creative reporting. Treat sudden smoothness as a smell.\n\n4) **Lag + backfills**: If late-arriving events exist (refunds, reversals, call outcomes), today’s number may be a preview, not the truth.\n\nIf you want one rule: **trust numbers that are hard to game and easy to explain.**",{"id":99,"name":100,"type":83,"typeVersion":16,"position":101,"parameters":102,"category":89,"deletable":8,"connectable":8},"node_if_dirty","If: Spot dirty signal fast",[85,38],{"buttonId":69,"operator":88},{"id":104,"name":105,"type":93,"typeVersion":16,"position":106,"parameters":107,"category":51,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal detectors",[95,38],{"text":108},"Dirty signal usually looks *reasonable*—that’s why it wins meetings. Quick detectors:\n\n- **Sudden step-changes** with no operational story: likely tracking, mapping, or process change.\n- **Too-clean stability** across messy operations: often aggregation hiding breakage.\n- **Segment gaps**: one branch, channel, or device type quietly missing.\n- **Small-n confidence**: a top branch on 12 events is a vibe, not a finding.\n- **Duplicate inflation**: retries, callbacks, reopened tickets—counts rise while reality doesn’t.\n\nMeeting-saving move: ask, “**What would we see if this were broken?**” If nobody can answer, assume it’s broken until proven otherwise.",{"id":110,"name":111,"type":83,"typeVersion":16,"position":112,"parameters":114,"category":89,"deletable":8,"connectable":8},"node_if_auto","If: Automation vs judgment",[85,113],300,{"buttonId":72,"operator":88},{"id":116,"name":117,"type":93,"typeVersion":16,"position":118,"parameters":119,"category":51,"deletable":8,"connectable":8},"node_text_auto","When to trust automation",[95,113],{"text":120},"Automation is great at **consistency**, not **wisdom**. Use it when:\n\n- The decision is **high-frequency, low-stakes** (routing, thresholds, routine follow-ups).\n- The inputs are **well-defined and stable** (same meaning over time).\n- You have **guardrails** (alerts for missing data, drift, and outliers).\n\nLean on human judgment when:\n\n- Stakes are high or irreversible (closing a branch program, changing comp, public commitments).\n- The world just changed (policy updates, competitor moves, staffing shifts).\n- The metric is a proxy (CSAT, “engagement”) and incentives are in play.\n\nPractical rule: **Automate the boring parts of being careful. Don’t automate the part where you decide what careful means.**",{"id":122,"name":123,"type":83,"typeVersion":16,"position":124,"parameters":125,"category":89,"deletable":8,"connectable":8},"node_if_compare","If: Compare branches & attribution",[85,57],{"buttonId":75,"operator":88},{"id":127,"name":128,"type":93,"typeVersion":16,"position":129,"parameters":130,"category":51,"deletable":8,"connectable":8},"node_text_compare","Branch comparison traps",[95,57],{"text":131},"Most branch comparisons fail for predictable reasons:\n\n1) **Mix shift**: Branch A didn’t “improve”—it got easier customers. Compare like-with-like (same segments, same windows).\n\n2) **Opportunity access**: If one branch gets more leads, better hours, or different product mix, raw performance is unfair.\n\n3) **Attribution overlap**: Conversations, callbacks, and multi-touch journeys will over-credit the last visible touch. If two channels can claim the same win, you don’t have attribution—you have diplomacy.\n\n4) **Survivorship + selection**: The branch with fewer recorded issues may just be recording less.\n\nHelpful move: ask, **“What would we conclude if we swapped the populations?”** If the answer changes, you’re measuring mix, not performance.",{"id":133,"name":134,"type":83,"typeVersion":16,"position":135,"parameters":137,"category":89,"deletable":8,"connectable":8},"node_if_culture","If: Build a signal culture",[85,136],540,{"buttonId":78,"operator":88},{"id":139,"name":140,"type":93,"typeVersion":16,"position":141,"parameters":142,"category":51,"deletable":8,"connectable":8},"node_text_culture","Signal culture that produces decisions",[95,136],{"text":143},"A healthy signal culture isn’t more dashboards—it’s fewer surprises.\n\n- **Decision logs**: Write down what you decided, what signals you used, and what would change your mind.\n- **Metric definitions that can’t wiggle**: One sentence, owner named, updated deliberately.\n- **Red flags are celebrated**: People who find breakage get thanked, not blamed.\n- **Pre-mortems before big calls**: “If this decision is wrong, what signal misled us?”\n\nWitty but true: **Slides don’t create alignment—shared definitions do.**",{"id":145,"name":146,"type":147,"typeVersion":16,"position":148,"parameters":150,"category":154,"deletable":8,"connectable":8},"node_fallback","Escalate to analytics review","fallback",[95,149],660,{"handoffMessage":151,"departmentId":152,"departmentName":153},"This looks like one of those cases where the numbers behave *just* well enough to be dangerous. I’m routing this to the analytics team for a human review of definitions, missing segments, and data drift.","dept-analytics-ops","Analytics Ops","terminal",[156,160,162,164,167,170,172,174,176,178,180,182,184],{"id":157,"source":35,"target":41,"sourceHandle":158,"targetHandle":159,"type":47},"conn_input_to_kb","out","in",{"id":161,"source":41,"target":53,"sourceHandle":158,"targetHandle":159,"type":47},"conn_kb_to_menu",{"id":163,"source":53,"target":81,"sourceHandle":158,"targetHandle":159,"type":47},"conn_menu_to_if_trust",{"id":165,"source":81,"target":91,"sourceHandle":166,"targetHandle":159,"type":47},"conn_if_trust_true_to_text","true",{"id":168,"source":81,"target":99,"sourceHandle":169,"targetHandle":159,"type":47},"conn_if_trust_false_to_if_dirty","false",{"id":171,"source":99,"target":104,"sourceHandle":166,"targetHandle":159,"type":47},"conn_if_dirty_true_to_text",{"id":173,"source":99,"target":110,"sourceHandle":169,"targetHandle":159,"type":47},"conn_if_dirty_false_to_if_auto",{"id":175,"source":110,"target":116,"sourceHandle":166,"targetHandle":159,"type":47},"conn_if_auto_true_to_text",{"id":177,"source":110,"target":122,"sourceHandle":169,"targetHandle":159,"type":47},"conn_if_auto_false_to_if_compare",{"id":179,"source":122,"target":127,"sourceHandle":166,"targetHandle":159,"type":47},"conn_if_compare_true_to_text",{"id":181,"source":122,"target":133,"sourceHandle":169,"targetHandle":159,"type":47},"conn_if_compare_false_to_if_culture",{"id":183,"source":133,"target":139,"sourceHandle":166,"targetHandle":159,"type":47},"conn_if_culture_true_to_text",{"id":185,"source":133,"target":145,"sourceHandle":169,"targetHandle":159,"type":47},"conn_if_culture_false_to_fallback","automation",[28,29,30,188,189,190],"data-hygiene","attribution","triage",[192],"Calypso Inbox","intermediate","Calypso","2026-06-28T11:03:07.210Z","/en/workflows/branch-signal-decision-field-manual",{"en":196},{"title":9,"description":199,"ogDescription":200,"twitterDescription":201,"canonicalPath":196,"robots":202,"schemaType":203,"alternates":204},"Guide teams to trust the right branch metrics, spot dirty signals early, and decide when automation vs judgment should lead.","A practical workflow to separate trustworthy branch signals from polished noise—spot dirty data, avoid attribution traps, and route tricky cases to humans.","Turn messy branch signals into decision ready guidance: trust checks, dirty signal detection, automation vs judgment, and clean escalation when needed.","index,follow","HowTo",[205],{"hreflang":6,"href":196},1785947667730]