[{"data":1,"prerenderedAt":224},["ShallowReactive",2],{"/en/workflows/branch-signal-decision-sensemaker":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},"4d8d2708-acbc-4937-8463-78bebc52bec7","branch-signal-decision-sensemaker","en",null,true,"Branch Signal Decision Sensemaker","A guided menu that turns messy branch numbers, conversations, and events into decision-ready checks—so teams stop mistaking polished noise for truth.","## How it works\nThis workflow acts like a practical “signal bouncer” for branch decisions. A teammate picks what they’re trying to decide (trust a metric, compare branches, judge attribution, etc.), and the flow serves a tight set of reality checks designed to catch the kinds of bad data that looks perfect—right up until the meeting ends with a confident wrong decision.\n\nIt uses a Knowledge Base step first (so common questions can be answered consistently), then routes the user into short, decision-shaped guidance they can apply immediately—without forcing a data-cleaning fantasy that scrubs away the truth.\n\n## Key features\n- Knowledge Base first, then routing: answers what it can, escalates to guided decision checks when it can’t.\n- Button-based menu that keeps the conversation crisp (no essay prompts, no “thought leadership”).\n- Practical “trust tests” for branch metrics, attribution, and cross-branch comparisons.\n- A built-in path to hand off to a human team when stakes are high or signals are messy.\n- Loop-back design: users can run multiple checks in one session without restarting.\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow (in your connected Calypso messaging channel).\n2. **Knowledge Base assist:** The workflow attempts to answer using your Knowledge Base policy.\n3. **Decision menu:** The user chooses what they need:\n   - **Which numbers deserve trust**\n   - **Spot dirty signal before the meeting**\n   - **Automation vs. human judgment**\n   - **Comparing branches & attribution pitfalls**\n   - **Building a signal culture (decisions, not slides)**\n   - **Talk to the Insights Team**\n4. **Guidance is delivered:** The workflow sends a focused playbook for the selected option.\n5. **Run another check (optional):** After each guidance message, the workflow returns to the menu.\n6. **Human handoff (optional):** If selected, the workflow hands the conversation to your Insights Team.\n\n## Setup requirements\n- A Calypso inbox with **WhatsApp** connected (or another channel that supports interactive buttons in your Calypso environment).\n- An enabled **Knowledge Base** in Calypso (recommended for consistent definitions and metric FAQs).\n- No additional credentials are required for this template beyond your existing Calypso channel setup.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":169,"routingEnabled":8,"active":33},"wf_branch_signal_decision_sensemaker","calypso-public-library","1.0.1",1,[18,34,40,52,83,92,97,103,109,115,120,128,134,140,146,152,159],{"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,80,{"name":9,"description":26,"tags":27,"triggerType":31},"Guided decision checks for branch signal reliability, dirty data detection, and when to trust automation vs. 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],220,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node_kb_policy","Knowledge Base assist","knowledge-base-policy",[45,38],360,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"Use the Knowledge Base to answer definitions and FAQs. If the user is making a decision or asking about reliability, route them to the decision menu.",{"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],620,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Decision check menu","Pick what you’re trying to decide. These checks catch bad data before it wins the meeting.","If it feels “done”, run the ugly checks.","",[65,68,71,74,77,80],{"id":66,"title":67},"trust_numbers","Numbers to trust",{"id":69,"title":70},"dirty_signal","Dirty signal check",{"id":72,"title":73},"automation_judgment","Auto vs judgment",{"id":75,"title":76},"compare_branches","Branch compare",{"id":78,"title":79},"signal_culture","Signal culture",{"id":81,"title":82},"talk_to_team","Talk to Insights",{"id":84,"name":85,"type":86,"typeVersion":16,"position":87,"parameters":89,"category":91,"deletable":8,"connectable":8},"node_if_trust_numbers","If: trust_numbers","if",[88,23],860,{"buttonId":66,"operator":90},"equals","routing",{"id":93,"name":94,"type":86,"typeVersion":16,"position":95,"parameters":96,"category":91,"deletable":8,"connectable":8},"node_if_dirty_signal","If: dirty_signal",[88,38],{"buttonId":69,"operator":90},{"id":98,"name":99,"type":86,"typeVersion":16,"position":100,"parameters":102,"category":91,"deletable":8,"connectable":8},"node_if_automation_judgment","If: automation_judgment",[88,101],320,{"buttonId":72,"operator":90},{"id":104,"name":105,"type":86,"typeVersion":16,"position":106,"parameters":108,"category":91,"deletable":8,"connectable":8},"node_if_compare_branches","If: compare_branches",[88,107],420,{"buttonId":75,"operator":90},{"id":110,"name":111,"type":86,"typeVersion":16,"position":112,"parameters":114,"category":91,"deletable":8,"connectable":8},"node_if_signal_culture","If: signal_culture",[88,113],520,{"buttonId":78,"operator":90},{"id":116,"name":117,"type":86,"typeVersion":16,"position":118,"parameters":119,"category":91,"deletable":8,"connectable":8},"node_if_talk_to_team","If: talk_to_team",[88,57],{"buttonId":81,"operator":90},{"id":121,"name":122,"type":123,"typeVersion":16,"position":124,"parameters":126,"category":51,"deletable":8,"connectable":8},"node_text_trust_numbers","Guidance: which numbers to trust","text-message",[125,23],1120,{"text":127},"Here’s how to tell *decision-grade* branch numbers from polished noise:\n\n1) **Traceability beats elegance.** Can you explain *how* the number is produced (systems, timing, exclusions) in one minute?\n2) **Stability check:** If a tiny process change (shift handover, promo end, staff absence) swings it wildly, it’s a mood ring—not a metric.\n3) **Denominator discipline:** “Up 20%” without the base count is how bad decisions wear suits.\n4) **Lag awareness:** Ask: *When* does this number become true? Yesterday’s precision can still be today’s wrong.\n5) **Per-branch comparability:** Same definition, same cut-off time, same inclusion rules—or don’t compare.\n\nIf you want another check, re-open the menu and pick **Dirty signal check** next.",{"id":129,"name":130,"type":123,"typeVersion":16,"position":131,"parameters":132,"category":51,"deletable":8,"connectable":8},"node_text_dirty_signal","Guidance: spot dirty signal fast",[125,38],{"text":133},"Dirty signal usually shows up as *confidence + convenience*. Quick tests before the room believes it:\n\n- **The “too clean” test:** perfect curves, no spikes, no missing days… real operations are messier.\n- **Timing mismatch:** does the spike happen *before* the supposed cause? If yes, you’re looking at scheduling/reporting artifacts.\n- **Reclassification smell:** sudden improvements with no operational story often mean definitions changed.\n- **One-source trap:** if only one dashboard says it, treat it as a hypothesis.\n- **Edge-case sampling:** check 5 real examples (calls, tickets, visits) behind the number. If the anecdotes don’t rhyme with the metric, pause.\n\nRule of thumb: when the slide feels “done,” that’s when you do the ugly checks.",{"id":135,"name":136,"type":123,"typeVersion":16,"position":137,"parameters":138,"category":51,"deletable":8,"connectable":8},"node_text_automation_judgment","Guidance: automation vs judgment",[125,101],{"text":139},"When to trust automation—and when to bring a human brain:\n\n**Trust automation when…**\n- The decision is frequent and reversible (staffing tweaks, routing rules).\n- Inputs are consistent and auditable (same capture method, same timing).\n- The cost of a wrong call is low *and* you’ll get fast feedback.\n\n**Require human judgment when…**\n- Definitions are shifting (new campaign, new script, new product).\n- The metric can be gamed (anything tied to incentives).\n- Outcomes are slow (retention, satisfaction) so errors hide for weeks.\n- The decision is one-way door (closing services, major policy changes).\n\nGood leaders automate the repeatable parts—and personally audit the assumptions that make automation look “obvious.”",{"id":141,"name":142,"type":123,"typeVersion":16,"position":143,"parameters":144,"category":51,"deletable":8,"connectable":8},"node_text_compare_branches","Guidance: compare branches & attribution",[125,107],{"text":145},"Comparing branches is where smart teams get tricked—because the spreadsheet looks impartial.\n\nUse this checklist:\n\n1) **Comparable context:** hours, staffing, footfall mix, local constraints. If context differs, normalize or don’t rank.\n2) **Selection effects:** “Better” branches often just receive different customers or different work.\n3) **Attribution humility:** last-touch stories are comforting, not always true. Ask what *would have happened anyway*.\n4) **Seasonality & events:** holidays, outages, local promotions. A single week can be a liar.\n5) **Guard against metric surfing:** if teams can choose the metric that makes them look best, you’ll get a leaderboard—of storytelling.\n\nIf you need a decision: prefer **direction + confidence** over fake precision. ‘Branch B is likely improving’ beats ‘B is +2.1% better’ when the inputs are squishy.",{"id":147,"name":148,"type":123,"typeVersion":16,"position":149,"parameters":150,"category":51,"deletable":8,"connectable":8},"node_text_signal_culture","Guidance: build a signal culture",[125,113],{"text":151},"A healthy signal culture makes decisions happen—without turning every meeting into a courtroom.\n\nPractical moves that work:\n\n- **Name your “decision metrics.”** A short list that actually triggers action (not vanity reporting).\n- **Write definitions once.** If people argue definitions mid-meeting, you’re not debating performance—you’re debating language.\n- **Pre-mortem the metric:** ask “How could this number lie?” before it does.\n- **Reward problem-finding.** If the first person to flag dirty data gets punished, you’ll get beautiful dashboards and ugly surprises.\n- **Keep a small ‘audit habit’:** weekly spot-checks of raw examples behind key metrics.\n\nSignal culture isn’t about more data. It’s about fewer arguments—and better ones.",{"id":153,"name":154,"type":123,"typeVersion":16,"position":155,"parameters":157,"category":51,"deletable":8,"connectable":8},"node_text_unknown","Fallback: choose an option",[125,156],720,{"text":158},"I didn’t catch a menu selection. Tap one of the buttons so I can route you to the right decision check—or choose **Talk to Insights** if this is high-stakes.",{"id":160,"name":161,"type":162,"typeVersion":16,"position":163,"parameters":164,"category":168,"deletable":8,"connectable":8},"node_handoff","Handoff to Insights Team","fallback",[125,57],{"handoffMessage":165,"departmentId":166,"departmentName":167},"Got it—looping in the Insights Team. Share the metric/report link (or a screenshot) and what decision you’re about to make. The fastest help comes from context + the exact definition you used.","insights","Insights Team","terminal",[170,174,176,178,181,183,185,187,189,191,194,196,198,200,202],{"id":171,"source":35,"target":41,"sourceHandle":172,"targetHandle":31,"type":173},"conn_input_to_kb","output","edge",{"id":175,"source":41,"target":53,"sourceHandle":172,"targetHandle":31,"type":173},"conn_kb_to_menu",{"id":177,"source":53,"target":84,"sourceHandle":172,"targetHandle":31,"type":173},"conn_menu_to_if1",{"id":179,"source":84,"target":93,"sourceHandle":180,"targetHandle":31,"type":173},"conn_if1_false_to_if2","false",{"id":182,"source":93,"target":98,"sourceHandle":180,"targetHandle":31,"type":173},"conn_if2_false_to_if3",{"id":184,"source":98,"target":104,"sourceHandle":180,"targetHandle":31,"type":173},"conn_if3_false_to_if4",{"id":186,"source":104,"target":110,"sourceHandle":180,"targetHandle":31,"type":173},"conn_if4_false_to_if5",{"id":188,"source":110,"target":116,"sourceHandle":180,"targetHandle":31,"type":173},"conn_if5_false_to_if6",{"id":190,"source":116,"target":153,"sourceHandle":180,"targetHandle":31,"type":173},"conn_if6_false_to_unknown",{"id":192,"source":84,"target":121,"sourceHandle":193,"targetHandle":31,"type":173},"conn_if1_true_to_text_trust","true",{"id":195,"source":93,"target":129,"sourceHandle":193,"targetHandle":31,"type":173},"conn_if2_true_to_text_dirty",{"id":197,"source":98,"target":135,"sourceHandle":193,"targetHandle":31,"type":173},"conn_if3_true_to_text_auto",{"id":199,"source":104,"target":141,"sourceHandle":193,"targetHandle":31,"type":173},"conn_if4_true_to_text_compare",{"id":201,"source":110,"target":147,"sourceHandle":193,"targetHandle":31,"type":173},"conn_if5_true_to_text_culture",{"id":203,"source":116,"target":160,"sourceHandle":193,"targetHandle":31,"type":173},"conn_if6_true_to_handoff","automation",[28,29,30,206,207,208],"attribution","data-hygiene","leadership-ops",[210],"WhatsApp","intermediate","Calypso","2026-06-18T11:03:41.988Z","/en/workflows/branch-signal-decision-sensemaker",{"en":214},{"title":9,"description":217,"ogDescription":218,"twitterDescription":219,"canonicalPath":214,"robots":220,"schemaType":221,"alternates":222},"Guide teams to trust the right branch signals, spot dirty data early, and choose when automation helps—or misleads—before decisions are made.","A practical, button driven guide to validate branch metrics, catch dirty signals, compare branches safely, and know when to escalate to human judgment.","Turn messy branch signals into decision ready checks. Spot polished noise, compare branches safely, and know when to trust automation vs. human judgment.","index,follow","HowTo",[223],{"hreflang":6,"href":214},1785947669101]