[{"data":1,"prerenderedAt":229},["ShallowReactive",2],{"/en/workflows/branch-signal-audit-for-better-decisions":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":210,"tags":211,"integrations":214,"difficulty":216,"author":217,"verified":33,"featured":33,"date":218,"modified":218,"icon":7,"imageSrc":7,"path":219,"alternates":220,"seo":221},"ea2836ed-6ed8-4c19-a2e3-acd52455b273","branch-signal-audit-for-better-decisions","en",null,true,"Branch Signal Audit for Better Decisions","A guided menu that helps leaders and analysts sanity-check branch numbers, spot dirty signals, and choose when to trust automation vs human judgment—before a confident meeting goes confidently wrong.","## How it works\nThis workflow turns “we have a number” into “we can trust this decision.” It starts by checking your Calypso Knowledge Base for an answer, then guides the operator through a simple menu to diagnose whether a branch metric is real, polished noise, or quietly broken.\n\nIt’s designed for messy reality: partial attribution, inconsistent conversations, branch-level quirks, and dashboards that look precise right up until they aren’t. The outcome is a decision-shaped next step (what to verify, what to ignore, and when to escalate to a human).\n\n## Key features\n- Knowledge Base first: answers common questions before routing to the decision menu\n- Button-based menu for fast triage (branch numbers, dirty signal, attribution comparisons, automation vs judgment, and culture)\n- Practical, operator-ready guidance messages that point to specific checks and failure modes\n- Safe fallback to a human handoff when the situation is high-stakes or ambiguous\n- Loop-back design so operators can run multiple audits in one session\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a message comes in.\n2. **Knowledge Base assist:** Calypso checks the Knowledge Base and responds when it has a solid match; otherwise it continues to guided routing.\n3. **Menu prompt:** The user picks what they need help with:\n   - Which branch numbers to trust\n   - How to spot dirty signal\n   - When to trust automation vs human judgment\n   - How to compare branches & attribution without fooling yourself\n   - How to build a signal culture that produces decisions (not slides)\n   - Talk to a human\n4. **Decision routing:** The workflow routes based on the selected button.\n5. **Advice output + loop:** A tailored guidance message is sent and the workflow returns to the menu so the operator can run the next check.\n6. **Human handoff (optional):** If “Talk to a human” is selected (or the input doesn’t match the buttons), the workflow escalates via fallback handoff.\n\n## Setup requirements\n- **Calypso Knowledge Base (optional but recommended):** Populate short, practical articles (definitions, metric rules, known branch exceptions, attribution logic).\n- **No additional credentials required** for this workflow itself.\n- **Operational prerequisite:** A defined human support destination (e.g., your Analytics Ops or Branch Performance team) for handoffs.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":176,"routingEnabled":8,"active":33},"wf_branch_signal_audit_v1","calypso-public-library","1.0.0",1,[18,34,41,53,84,93,102,107,114,120,127,133,140,146,153,159,169],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_cfg","Workflow settings","flow-configs",[23,24],-40,40,{"name":9,"description":26,"tags":27,"triggerType":31},"Guided audit menu to sanity-check branch numbers, detect dirty signal, and choose automation vs human judgment. Escalates to human when needed.",[28,29,30],"signal-quality","branch-analytics","decision-making","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":40,"category":31,"deletable":33,"connectable":8},"node_input","Incoming message",[38,39],140,220,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb","Knowledge Base assist","knowledge-base-policy",[46,39],360,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":48,"activationOpener":49,"personalization":51},"default",{"enabled":8,"instruction":50},"Answer like an experienced advisor: practical, decision-shaped, and lightly witty. Prefer concrete checks, failure modes, and what to do next. If the Knowledge Base does not clearly apply, do not guess—allow routing to the menu.",{"useContactName":8},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"node_menu","Pick an audit","interactive-message",[58,39],600,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":64,"ctaUrl":64},"button","Signal audit menu","What are you trying to decide (or defend) right now? Pick the closest match and I’ll give you the checks that usually save the meeting.","If it looks clean fast, it’s hiding a mess.","",[66,69,72,75,78,81],{"id":67,"title":68},"branch_numbers","Trust branch numbers",{"id":70,"title":71},"dirty_signal","Spot dirty signal",{"id":73,"title":74},"automation_judgment","Auto vs judgment",{"id":76,"title":77},"compare_attribution","Branch comparison",{"id":79,"title":80},"signal_culture","Signal culture",{"id":82,"title":83},"handoff","Talk to a human",{"id":85,"name":86,"type":87,"typeVersion":16,"position":88,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_branch","If: branch numbers","if",[89,39],840,{"buttonId":67,"operator":91},"equals","routing",{"id":94,"name":95,"type":96,"typeVersion":16,"position":97,"parameters":100,"category":52,"deletable":8,"connectable":8},"node_txt_branch","Branch numbers: trust check","text-message",[98,99],1080,120,{"text":101},"Branch numbers that deserve trust usually have *friction* built in—rules, consistency, and known blind spots.\n\nQuick trust checks:\n- **Definition check:** Can you say what counts (and what doesn’t) in one sentence? If not, it’s a story, not a metric.\n- **Denominator sanity:** Is the “per X” stable across branches (traffic, eligible customers, staffed hours)? If the denominator floats, the leaderboard lies.\n- **Lag + revision:** Do yesterday’s numbers change today? If they never revise, they’re probably not capturing reality.\n- **Exception list:** Which branches break the rules (pilot programs, staffing gaps, local promos)? If you can’t name them, you’re about to misread them.\n\nIf you want one move: **compare trend vs level.** Levels are noisy; trend consistency is harder to fake.",{"id":103,"name":104,"type":87,"typeVersion":16,"position":105,"parameters":106,"category":92,"deletable":8,"connectable":8},"node_if_dirty","If: dirty signal",[89,46],{"buttonId":70,"operator":91},{"id":108,"name":109,"type":96,"typeVersion":16,"position":110,"parameters":112,"category":52,"deletable":8,"connectable":8},"node_txt_dirty","Dirty signal: early warning",[98,111],260,{"text":113},"Dirty data rarely announces itself. It shows up as *confidence with no edges*.\n\nFast ways to spot it before the meeting goes off the rails:\n- **Too-smooth charts:** Real operations have bumps. Perfectly steady lines often mean missing events or late ingestion.\n- **One field does all the work:** If attribution hinges on a single tag/source, assume it’s being mis-set somewhere.\n- **Sudden step-change with no story:** If the metric jumps but frontline teams have no corresponding “what changed,” suspect tracking.\n- **Conversation mismatch:** If calls/chats say one thing and the dashboard says another, trust the conversations first—then investigate why.\n\nPractical move: **sample 10 records** (different branches, different days). Dirty signal shows up faster in examples than in averages.",{"id":115,"name":116,"type":87,"typeVersion":16,"position":117,"parameters":119,"category":92,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[89,118],500,{"buttonId":73,"operator":91},{"id":121,"name":122,"type":96,"typeVersion":16,"position":123,"parameters":125,"category":52,"deletable":8,"connectable":8},"node_txt_auto","Automation vs judgment: guardrails",[98,124],400,{"text":126},"Trust automation when the decision is **repeatable, reversible, and measured**. Reach for humans when it’s **novel, high-stakes, or politically costly**.\n\nUse this rule of thumb:\n- **Automate:** routing, alerts, prioritization, and “checklists with math.”\n- **Human judgment:** exceptions, policy, reputational risk, and anything with real customer harm.\n\nTwo practical guardrails:\n- **Define a stop condition:** “If volume drops by X” or “if branch exception list includes Y,” automation must escalate.\n- **Instrument regret:** track overrides and outcomes. If humans override often *and* are right, the automation is confidently wrong.",{"id":128,"name":129,"type":87,"typeVersion":16,"position":130,"parameters":132,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[89,131],640,{"buttonId":76,"operator":91},{"id":134,"name":135,"type":96,"typeVersion":16,"position":136,"parameters":138,"category":52,"deletable":8,"connectable":8},"node_txt_compare","Comparisons: what teams misread",[98,137],540,{"text":139},"Branch comparisons fail when we pretend the inputs are equal. They aren’t.\n\nWhat teams repeatedly misread:\n- **Mix effects:** One branch gets harder cases, different customer segments, or different staffing. Normalizing only by volume is not enough.\n- **Attribution gravity:** The channel that logs the last touch “wins” even when it didn’t cause the outcome.\n- **Operational constraints:** Hours, training, outages, local promos—these change behavior more than dashboards admit.\n\nPractical comparison method:\n- Compare **within-branch over time** first.\n- Then compare branches only after you align **eligibility, hours, and mix** (even roughly).\n- Treat attribution as a **clue**, not a verdict—triangulate with conversations and operational events.",{"id":141,"name":142,"type":87,"typeVersion":16,"position":143,"parameters":145,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: build signal culture",[89,144],780,{"buttonId":79,"operator":91},{"id":147,"name":148,"type":96,"typeVersion":16,"position":149,"parameters":151,"category":52,"deletable":8,"connectable":8},"node_txt_culture","Signal culture: make decisions happen",[98,150],680,{"text":152},"A good signal culture doesn’t produce more dashboards. It produces **fewer arguments** and **faster decisions**.\n\nWhat works in practice:\n- **One-page metric contracts:** name, definition, owner, update lag, known blind spots, and what decision it supports.\n- **Explicit uncertainty:** require a confidence label (High/Medium/Low) so teams stop bluffing with decimals.\n- **Pre-mortems for metrics:** “How could this number be wrong?” before you use it to reward/punish branches.\n- **Decision logs:** write down what you decided and what signal you trusted. Your future self will thank you (and your postmortems will get shorter).",{"id":154,"name":155,"type":87,"typeVersion":16,"position":156,"parameters":158,"category":92,"deletable":8,"connectable":8},"node_if_handoff","If: talk to a human",[89,157],920,{"buttonId":82,"operator":91},{"id":160,"name":161,"type":162,"typeVersion":16,"position":163,"parameters":164,"category":168,"deletable":8,"connectable":8},"node_fallback","Handoff to Analytics Ops","fallback",[98,157],{"handoffMessage":165,"departmentId":166,"departmentName":167},"Got it—this sounds like it deserves human judgment. I’m handing this to Analytics Ops with your last message and context. If this is urgent, include: branch(es), date range, metric name, and what decision is on the line.","analytics-ops","Analytics Ops","terminal",{"id":170,"name":171,"type":96,"typeVersion":16,"position":172,"parameters":174,"category":52,"deletable":8,"connectable":8},"node_txt_unknown","Unrecognized selection",[98,173],1040,{"text":175},"I may be missing the click—please use one of the menu buttons so I can route you to the right audit. If this is time-sensitive, choose **Talk to a human**.",[177,180,182,184,187,190,192,194,196,198,200,202,204,206,208],{"id":178,"source":35,"target":42,"sourceHandle":48,"targetHandle":48,"type":179},"conn_input_kb","edge",{"id":181,"source":42,"target":54,"sourceHandle":48,"targetHandle":48,"type":179},"conn_kb_menu",{"id":183,"source":54,"target":85,"sourceHandle":48,"targetHandle":48,"type":179},"conn_menu_if_branch",{"id":185,"source":85,"target":94,"sourceHandle":186,"targetHandle":48,"type":179},"conn_if_branch_true_txt","true",{"id":188,"source":85,"target":103,"sourceHandle":189,"targetHandle":48,"type":179},"conn_if_branch_false_if_dirty","false",{"id":191,"source":103,"target":108,"sourceHandle":186,"targetHandle":48,"type":179},"conn_if_dirty_true_txt",{"id":193,"source":103,"target":115,"sourceHandle":189,"targetHandle":48,"type":179},"conn_if_dirty_false_if_auto",{"id":195,"source":115,"target":121,"sourceHandle":186,"targetHandle":48,"type":179},"conn_if_auto_true_txt",{"id":197,"source":115,"target":128,"sourceHandle":189,"targetHandle":48,"type":179},"conn_if_auto_false_if_compare",{"id":199,"source":128,"target":134,"sourceHandle":186,"targetHandle":48,"type":179},"conn_if_compare_true_txt",{"id":201,"source":128,"target":141,"sourceHandle":189,"targetHandle":48,"type":179},"conn_if_compare_false_if_culture",{"id":203,"source":141,"target":147,"sourceHandle":186,"targetHandle":48,"type":179},"conn_if_culture_true_txt",{"id":205,"source":141,"target":154,"sourceHandle":189,"targetHandle":48,"type":179},"conn_if_culture_false_if_handoff",{"id":207,"source":154,"target":160,"sourceHandle":186,"targetHandle":48,"type":179},"conn_if_handoff_true_fallback",{"id":209,"source":154,"target":170,"sourceHandle":189,"targetHandle":48,"type":179},"conn_if_handoff_false_unknown","automation",[28,29,30,212,213],"data-hygiene","attribution",[215],"Calypso Knowledge Base","intermediate","Calypso","2026-07-29T11:03:48.370Z","/en/workflows/branch-signal-audit-for-better-decisions",{"en":219},{"title":9,"description":222,"ogDescription":223,"twitterDescription":224,"canonicalPath":219,"robots":225,"schemaType":226,"alternates":227},"Guide teams to trust the right branch numbers, spot dirty signals, and choose automation vs judgment with a routed decision menu.","A practical workflow to sanity check branch metrics, detect dirty signals early, and avoid confident wrong decisions—plus a fast human handoff when needed.","Stop polished noise from driving decisions. Audit branch signals, spot dirty data, and decide when automation is enough (and when a human must weigh in).","index,follow","HowTo",[228],{"hreflang":6,"href":219},1785947666144]