[{"data":1,"prerenderedAt":234},["ShallowReactive",2],{"/en/workflows/branch-signal-decision-coach":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":213,"tags":214,"integrations":218,"difficulty":221,"author":222,"verified":33,"featured":33,"date":223,"modified":223,"icon":7,"imageSrc":7,"path":224,"alternates":225,"seo":226},"4e2a36cb-82ac-4771-b2a9-b87b44a84f91","branch-signal-decision-coach","en",null,true,"Branch Signal Decision Coach","Turn messy branch numbers, conversations, and events into decision-ready guidance. This workflow uses a knowledge base first, then routes operators through practical “trust tests” so teams stop confusing polished noise for truth.","## How it works\nThis workflow helps operators and branch leaders pressure-test the signals behind a decision before they confidently walk into the wrong meeting. It starts by answering with your Knowledge Base (so the easy questions are handled fast), then offers a menu of decision-shaped topics that translate messy evidence into clear next actions.\n\nIt’s built for the real world where bad data often looks “clean” until it gets compared across branches, attributed to the wrong cause, or automated into a dashboard that nobody challenges. The workflow pushes the user toward practical checks: what to trust, what to distrust, what to measure next, and when to stop pretending the numbers are self-explanatory.\n\n## Key features\n- Knowledge Base first: answers known questions immediately, then routes to guided decision coaching when needed.\n- Interactive menu of decision-shaped paths (trust branch numbers, spot dirty signals, attribution/branch comparisons, automation vs judgment, and more).\n- Practical, non-academic guidance written for operators who need usable checks—not theory.\n- Optional human handoff path when the situation needs judgment, context, or escalation.\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow via the **Input** node.\n2. **Knowledge Base pass:** **Knowledge Base Policy** attempts to answer using your maintained content. If it can’t confidently answer, it falls through to routing.\n3. **Choose a decision path:** The user receives an **Interactive Message** with buttons to pick what they’re deciding (e.g., which branch numbers to trust, how to spot dirty signal, automation vs human judgment).\n4. **Route by selection:** A matching **If** node checks the exact button id and routes to the relevant coaching message.\n5. **Get the playbook:** A **Text Message** delivers a concise, decision-ready checklist and common failure modes for that topic.\n6. **Escalate when needed:** If the user chooses **Talk to a person**, the workflow routes to **Fallback** for human support.\n\n## Setup requirements\n- Calypso Knowledge Base: recommended (this workflow is designed to use it first). No additional credentials are required beyond your Calypso workspace access.\n- Calypso Inbox/channel connected to receive and send interactive and text messages (e.g., your Calypso chat surface).",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":179,"routingEnabled":8,"active":33},"wf_branch_signal_decision_coach_v1","calypso-public-library","1.0.0",1,[18,34,40,52,86,96,104,110,116,122,128,134,140,146,152,157,163,169],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_configs","Flow settings","flow-configs",[23,24],-240,80,{"name":9,"description":26,"tags":27,"triggerType":31},"KB-first decision coaching for branch signals: trust tests, dirty-signal spotting, attribution traps, and automation vs judgment.",[28,29,30],"signal-quality","decision-systems","branch-metrics","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":39,"category":31,"deletable":33,"connectable":8},"node_input","Start",[38,24],-40,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node_kb_policy","Knowledge Base first","knowledge-base-policy",[45,24],200,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"Use the Knowledge Base to answer if you can. If the question is ambiguous, high-stakes, or about interpreting branch signals, route to the decision menu instead of guessing.",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_menu","Choose what you’re deciding","interactive-message",[57,24],460,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Decision coaching for branch signals","Pick the path that matches what you need. If you’re about to defend numbers in a meeting, start with trust checks—polished noise is persuasive right up until it’s wrong.","Tip: Assume measurement changed before reality.","",[65,68,71,74,77,80,83],{"id":66,"title":67},"TRUST_BRANCH_NUMBERS","Trust numbers",{"id":69,"title":70},"SPOT_DIRTY_SIGNAL","Spot dirty data",{"id":72,"title":73},"AUTOMATION_VS_JUDGMENT","Auto vs judgment",{"id":75,"title":76},"MESSY_EVIDENCE_INSIGHT","Messy to insight",{"id":78,"title":79},"COMPARE_BRANCHES_ATTRIBUTION","Compare branches",{"id":81,"title":82},"BUILD_SIGNAL_CULTURE","Signal culture",{"id":84,"title":85},"TALK_TO_PERSON","Talk to a person",{"id":87,"name":88,"type":89,"typeVersion":16,"position":90,"parameters":93,"category":95,"deletable":8,"connectable":8},"node_if_trust","If: Which numbers to trust","if",[91,92],740,-140,{"buttonId":66,"operator":94},"equals","routing",{"id":97,"name":98,"type":99,"typeVersion":16,"position":100,"parameters":102,"category":51,"deletable":8,"connectable":8},"node_text_trust","Trust checks for branch numbers","text-message",[101,92],1010,{"text":103},"Here’s the fast way to decide whether a branch number deserves trust—or just looks impressive on a slide:\n\n1) Definition check (the silent killer)\n- What exactly is counted? What is excluded?\n- Has the definition changed in the last 60–90 days?\n\n2) Capture check (is it consistently recorded?)\n- Is the number based on optional fields, manual notes, or “best effort” tagging? Treat it as directional.\n- If one branch captures more diligently, it will look worse/better for the wrong reasons.\n\n3) Denominator check (the most common trap)\n- Ask: “Out of what?” Volume swings can fake performance swings.\n- Prefer rates with stable denominators and explicit eligibility rules.\n\n4) Lag & revision check\n- Does the metric settle over time (late postings, reclassifications)? If yes, avoid week-to-week heroics.\n\n5) Incentive check\n- If people are judged on it, they will game it—even politely.\n\nIf you want, tell me the metric name and what decision it’s driving (staffing, budget, coaching, product changes), and I’ll point out the top 2 failure modes to test first.",{"id":105,"name":106,"type":89,"typeVersion":16,"position":107,"parameters":109,"category":95,"deletable":8,"connectable":8},"node_if_dirty","If: Spot dirty signal fast",[91,108],-20,{"buttonId":69,"operator":94},{"id":111,"name":112,"type":99,"typeVersion":16,"position":113,"parameters":114,"category":51,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal early-warning checklist",[101,108],{"text":115},"Dirty data rarely announces itself. It shows up as confidence that’s out of proportion to evidence. Quick tells before the meeting goes off the rails:\n\n- Spikes that align with process changes (new form, new script, new manager, new incentive).\n- Perfect smoothness: real operations are lumpy. A flat line can mean “stuck pipeline,” not stability.\n- Missingness that isn’t random (e.g., certain shifts, roles, or busy days don’t get logged).\n- Category drift: teams rename or re-label to sound consistent; the trend stays “clean” while meaning changes.\n- One branch looks ‘better’ because it’s better at recording the outcome, not achieving it.\n\nTwo practical moves:\n1) Ask for 10 raw examples (calls, notes, events) behind the number.\n2) Recompute the metric using only high-confidence records. If the conclusion flips, the original signal is fragile.\n\nShare the metric + the time window and I’ll suggest the quickest falsification test.",{"id":117,"name":118,"type":89,"typeVersion":16,"position":119,"parameters":121,"category":95,"deletable":8,"connectable":8},"node_if_auto","If: Automation vs judgment",[91,120],100,{"buttonId":72,"operator":94},{"id":123,"name":124,"type":99,"typeVersion":16,"position":125,"parameters":126,"category":51,"deletable":8,"connectable":8},"node_text_auto","When to trust automation (and when not to)",[101,120],{"text":127},"Automation is great at repetition, not responsibility. Use this rule of thumb:\n\nTrust automation when:\n- The definition is stable and audited (everyone agrees what “success” means).\n- The cost of being wrong is low to moderate.\n- The signal is hard to game (or gaming is detectable).\n- You can monitor drift (you’ll notice if the process changes).\n\nRequire human judgment when:\n- The decision is high-stakes (people, pricing, compliance, reputation).\n- The signal is proxy-heavy (attribution, sentiment tagging, ‘intent’ labels).\n- Branches operate differently (different customer mix, staffing, hours, local constraints).\n- There’s a plausible “measurement changed” story.\n\nPractical compromise:\n- Automate the *alert*, not the *conclusion*.\n- Put humans on the exceptions: surprises, outliers, sudden inflections, and anything that triggers incentives.\n\nIf you describe the decision you’re automating, I’ll tell you what to keep automated and what must stay reviewed.",{"id":129,"name":130,"type":89,"typeVersion":16,"position":131,"parameters":133,"category":95,"deletable":8,"connectable":8},"node_if_messy","If: Messy evidence → insight",[91,132],220,{"buttonId":75,"operator":94},{"id":135,"name":136,"type":99,"typeVersion":16,"position":137,"parameters":138,"category":51,"deletable":8,"connectable":8},"node_text_messy","Use messy evidence without ‘cleaning away’ the truth",[101,132],{"text":139},"Cleaning isn’t neutral. If you over-clean, you delete the very weirdness that explains what’s happening.\n\nA practical approach:\n\n1) Separate “messy” from “unreliable”\n- Messy can be real (edge cases, unusual customer journeys).\n- Unreliable means the same thing isn’t recorded the same way.\n\n2) Keep a ‘raw reality’ slice\n- Always retain a view that includes the ugly: notes, exceptions, reversals, reopens.\n- Use it to sanity-check neat dashboards.\n\n3) Promote evidence in tiers\n- Tier 1: system-recorded events with clear definitions.\n- Tier 2: structured fields with moderate compliance.\n- Tier 3: free-text notes and manual tags (use for hypotheses, not conclusions).\n\n4) Don’t average away the story\n- If branches differ, ask which segments differ (new vs existing, product types, time-of-day).\n\nIf you tell me what evidence you have (events, conversations, outcomes) I can suggest a tiering that preserves truth without letting chaos run the show.",{"id":141,"name":142,"type":89,"typeVersion":16,"position":143,"parameters":145,"category":95,"deletable":8,"connectable":8},"node_if_compare","If: Compare branches & attribution",[91,144],340,{"buttonId":78,"operator":94},{"id":147,"name":148,"type":99,"typeVersion":16,"position":149,"parameters":150,"category":51,"deletable":8,"connectable":8},"node_text_compare","What teams misread in branch comparisons & attribution",[101,144],{"text":151},"Branch comparisons fail for predictable reasons—usually before anyone opens a spreadsheet.\n\nWhat gets misread first:\n\n- Different mix, same process: customer mix changes the outcome. Your ‘best branch’ might just have easier cases.\n- Different process, same definition: one branch follows the script; another improvises. The metric looks comparable, but the behavior isn’t.\n- Attribution that rewards the last touch: the ‘winner’ channel gets credit; the real driver stays hidden.\n- Volume illusions: a small branch swings wildly; a big branch looks ‘stable’ while problems hide inside.\n- Survivorship bias: you only see completed journeys; the dropouts are the point.\n\nDecision-safe comparison checklist:\n1) Match on eligibility (who could have counted).\n2) Compare rates + volumes together.\n3) Break out key segments (top 2–3 that explain most variance).\n4) Treat attribution as a hypothesis generator, not a verdict.\n\nIf you share what you’re comparing (branches, channels, or conversation outcomes), I’ll suggest the minimum segmentation that prevents a confident wrong call.",{"id":153,"name":154,"type":89,"typeVersion":16,"position":155,"parameters":156,"category":95,"deletable":8,"connectable":8},"node_if_culture","If: Build a signal culture",[91,57],{"buttonId":81,"operator":94},{"id":158,"name":159,"type":99,"typeVersion":16,"position":160,"parameters":161,"category":51,"deletable":8,"connectable":8},"node_text_culture","Build a signal culture that produces decisions (not slides)",[101,57],{"text":162},"A healthy signal culture isn’t ‘more metrics.’ It’s fewer arguments that start with “I don’t trust the numbers.”\n\nWhat works in practice:\n\n- Name the decision first. Then choose signals. Metrics without a decision are just busy.\n- Publish definitions like you publish policies. If a metric can’t be defined in one paragraph, it’s not ready.\n- Make ‘challenge the signal’ a role, not a personality trait.\n- Keep a short list of “known-bad signals” (optional fields, free-text tags, vanity counts) and label them clearly.\n- Reward truth-telling: when a team finds a measurement issue, treat it as progress, not failure.\n\nSimple operating rhythm:\n- Weekly: 10-minute signal review (what changed, what might be measurement).\n- Monthly: definition audit (did anything drift?).\n\nIf you tell me your top 3 decisions this quarter, I’ll recommend a small set of signals worth institutionalizing—and what to stop tracking.",{"id":164,"name":165,"type":89,"typeVersion":16,"position":166,"parameters":168,"category":95,"deletable":8,"connectable":8},"node_if_handoff","If: Talk to a person",[91,167],580,{"buttonId":84,"operator":94},{"id":170,"name":171,"type":172,"typeVersion":16,"position":173,"parameters":174,"category":178,"deletable":8,"connectable":8},"node_fallback","Human support","fallback",[101,167],{"handoffMessage":175,"departmentId":176,"departmentName":177},"Got it — this one benefits from context and judgment. I’m handing you to a teammate. If you can, share: the decision, the metric(s), the time window, and what changed recently.","ops-analytics","Ops Analytics","terminal",[180,183,185,187,189,191,193,195,197,199,201,203,205,207,209,211],{"id":181,"source":35,"target":41,"sourceHandle":47,"targetHandle":47,"type":182},"conn_input_to_kb","edge",{"id":184,"source":41,"target":53,"sourceHandle":47,"targetHandle":47,"type":182},"conn_kb_to_menu",{"id":186,"source":53,"target":87,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_trust",{"id":188,"source":53,"target":105,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_dirty",{"id":190,"source":53,"target":117,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_auto",{"id":192,"source":53,"target":129,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_messy",{"id":194,"source":53,"target":141,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_compare",{"id":196,"source":53,"target":153,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_culture",{"id":198,"source":53,"target":164,"sourceHandle":47,"targetHandle":47,"type":182},"conn_menu_to_if_handoff",{"id":200,"source":87,"target":97,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_trust_to_text",{"id":202,"source":105,"target":111,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_dirty_to_text",{"id":204,"source":117,"target":123,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_auto_to_text",{"id":206,"source":129,"target":135,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_messy_to_text",{"id":208,"source":141,"target":147,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_compare_to_text",{"id":210,"source":153,"target":158,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_culture_to_text",{"id":212,"source":164,"target":170,"sourceHandle":47,"targetHandle":47,"type":182},"conn_if_handoff_to_fallback","automation",[28,29,30,215,216,217],"attribution","leadership","data-hygiene",[219,220],"Calypso Knowledge Base","Calypso Inbox","intermediate","Calypso","2026-05-22T11:03:29.396Z","/en/workflows/branch-signal-decision-coach",{"en":224},{"title":9,"description":227,"ogDescription":228,"twitterDescription":229,"canonicalPath":224,"robots":230,"schemaType":231,"alternates":232},"Guide teams to trust the right branch signals, spot dirty data early, and balance automation with judgment before decisions go wrong.","A practical decision coach for branch metrics and messy signals—spot dirty data, avoid attribution traps, and know when to trust automation vs human judgment.","Turn messy branch signals into decision ready guidance: trust checks, dirty signal spotting, attribution pitfalls, and when to escalate to human judgment.","index,follow","HowTo",[233],{"hreflang":6,"href":224},1780761213490]