[{"data":1,"prerenderedAt":223},["ShallowReactive",2],{"/en/workflows/branch-signal-reality-audit":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":205,"tags":206,"integrations":209,"difficulty":211,"author":210,"verified":32,"featured":32,"date":212,"modified":212,"icon":7,"imageSrc":7,"path":213,"alternates":214,"seo":215},"cf4a46b5-f2d4-417c-96a1-7a46dfe44ad0","branch-signal-reality-audit","en",null,true,"Branch Signal Reality Audit","An advisor-style decision helper that routes leaders through practical checks for noisy branch metrics, dirty signals, and when to trust automation vs human judgment.","## How it works\nThis workflow helps branch and regional leaders turn “good-looking” metrics, conversations, and local events into decisions they can defend. It starts with a Knowledge Base-first experience (so common questions can be answered immediately), then routes users into a short menu of decision-shaped topics when the request is messy, ambiguous, or needs judgment.\n\nIt’s built for the moment right before the confident meeting goes off the rails: someone shows a clean chart, everyone nods, and the decision quietly bakes in bad assumptions. This flow adds fast guardrails—without turning your team into a statistics seminar.\n\n## Key features\n- Knowledge Base-first responses for common definitions and recurring questions\n- Button-based menu that routes users into practical, decision-ready checks (no hunting)\n- Dedicated guidance for “trustworthy vs polished noise” branch numbers\n- A clear split between where automation earns trust and where humans must stay in the loop\n- Optional handoff to a human owner when the situation is sensitive or high-stakes\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow (Input).\n2. **Knowledge Base policy:** If the user’s question can be answered directly from your Knowledge Base, they get an immediate answer; otherwise the flow continues to routing.\n3. **Topic menu:** The user picks what they need help with (buttons).\n4. **Routing (IF chain):** The workflow matches the selected button ID and routes to the corresponding guidance.\n5. **Outcome:** The user receives a concise advisory message with practical checks and next-step framing. If they choose **“Talk to a human”**, the workflow hands off to routing/department handling.\n\n## Setup requirements\n- No credentials required.\n- (Optional) Enable and maintain your Calypso Knowledge Base content so the Knowledge Base policy can answer common questions before routing to the menu.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":170,"routingEnabled":8,"active":32},"wf_branch_signal_reality_audit_v1","calypso-public-library","1.0.0",1,[18,33,39,51,82,92,98,104,110,116,122,130,136,142,148,154,163],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":24,"category":31,"deletable":32,"connectable":32},"node_flow_cfg","Flow configs","flow-configs",[23,23],0,{"name":9,"description":25,"tags":26,"triggerType":30},"Decision helper for auditing branch metrics and messy signals before they turn into confident wrong decisions.",[27,28,29],"signal-quality","branch-metrics","decision-making","input","policy",false,{"id":34,"name":35,"type":30,"typeVersion":16,"position":36,"parameters":38,"category":30,"deletable":32,"connectable":8},"node_input","Start",[23,37],140,{},{"id":40,"name":41,"type":42,"typeVersion":16,"position":43,"parameters":45,"category":50,"deletable":8,"connectable":8},"node_kb","Knowledge Base first","knowledge-base-policy",[44,37],220,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":46,"activationOpener":47,"personalization":49},"default",{"enabled":8,"instruction":48},"Ask a question about branch performance signals, attribution, or what to trust. If it needs judgment, pick a topic from the menu.",{"useContactName":8},"response",{"id":52,"name":53,"type":54,"typeVersion":16,"position":55,"parameters":57,"category":50,"deletable":8,"connectable":8},"node_menu","Choose what you’re deciding","interactive-message",[56,37],460,{"messageType":58,"headerText":59,"bodyText":60,"footerText":61,"sectionTitle":62,"buttons":63,"ctaDisplayText":62,"ctaUrl":62},"button","Research & Decision Support","Pick what you’re trying to decide. I’ll help you separate trustworthy signal from polished noise (before the meeting does it for you).","Tip: If it looks too clean, ask what changed.","",[64,67,70,73,76,79],{"id":65,"title":66},"trust_numbers","Trust numbers",{"id":68,"title":69},"spot_dirty_signal","Spot dirty signal",{"id":71,"title":72},"automation_vs_judgment","Automation vs humans",{"id":74,"title":75},"messy_evidence","Use messy evidence",{"id":77,"title":78},"compare_branches","Compare branches",{"id":80,"title":81},"talk_to_human","Talk to a human",{"id":83,"name":84,"type":85,"typeVersion":16,"position":86,"parameters":89,"category":91,"deletable":8,"connectable":8},"node_if_trust","IF: trust_numbers","if",[87,88],700,80,{"buttonId":65,"operator":90},"equals","routing",{"id":93,"name":94,"type":85,"typeVersion":16,"position":95,"parameters":97,"category":91,"deletable":8,"connectable":8},"node_if_dirty","IF: spot_dirty_signal",[87,96],160,{"buttonId":68,"operator":90},{"id":99,"name":100,"type":85,"typeVersion":16,"position":101,"parameters":103,"category":91,"deletable":8,"connectable":8},"node_if_auto","IF: automation_vs_judgment",[87,102],240,{"buttonId":71,"operator":90},{"id":105,"name":106,"type":85,"typeVersion":16,"position":107,"parameters":109,"category":91,"deletable":8,"connectable":8},"node_if_messy","IF: messy_evidence",[87,108],320,{"buttonId":74,"operator":90},{"id":111,"name":112,"type":85,"typeVersion":16,"position":113,"parameters":115,"category":91,"deletable":8,"connectable":8},"node_if_compare","IF: compare_branches",[87,114],400,{"buttonId":77,"operator":90},{"id":117,"name":118,"type":85,"typeVersion":16,"position":119,"parameters":121,"category":91,"deletable":8,"connectable":8},"node_if_human","IF: talk_to_human",[87,120],480,{"buttonId":80,"operator":90},{"id":123,"name":124,"type":125,"typeVersion":16,"position":126,"parameters":128,"category":50,"deletable":8,"connectable":8},"node_text_trust","Trustworthy vs polished noise","text-message",[127,88],980,{"text":129},"Branch numbers that deserve trust usually have three boring qualities: (1) stable definitions, (2) boring collection, (3) visible gaps.\n\n**Trust more:**\n- Counts tied to a clear operational event (opened ticket, fulfilled order, cash posted)\n- Metrics with known “missingness” (you can see what didn’t report)\n- Measures that move *with* operational levers (staffing, hours, inventory)\n\n**Trust less (polished noise):**\n- Composite scores with changing ingredients\n- “Conversion” where the denominator is fuzzy (walk-ins? leads? ‘conversations’?)\n- Any metric that improved right after you changed incentives or dashboards\n\n**Fast test:** Ask, “If this number doubled, what exactly happened in the branch?” If nobody can answer in one sentence, the number is probably decorative.",{"id":131,"name":132,"type":125,"typeVersion":16,"position":133,"parameters":134,"category":50,"deletable":8,"connectable":8},"node_text_dirty","Spot dirty signal before the meeting",[127,96],{"text":135},"Dirty signal almost always shows up as *confidence without friction*. Here are the early smells:\n\n- **Step-changes at month boundaries** (definitions or logging changed)\n- **Perfectly smooth trends** (real operations are lumpy; smooth often means averaged-away truth)\n- **One branch is “miraculously consistent”** while peers aren’t (often a process difference, not performance)\n- **Outliers that match reporting schedules** (not customer behavior)\n\n**Meeting-saver questions (use one):**\n1) “What would make this chart wrong?”\n2) “Where does this number physically come from?”\n3) “What’s the fastest way to fake this metric?”\n\nIf a metric can be gamed in under a day, don’t let it drive a quarter’s decision.",{"id":137,"name":138,"type":125,"typeVersion":16,"position":139,"parameters":140,"category":50,"deletable":8,"connectable":8},"node_text_auto","Automation vs human judgment",[127,102],{"text":141},"Automation earns trust when the world is repetitive and the cost of a miss is bounded. Humans stay essential when the data is negotiable and the downside is asymmetric.\n\n**Trust automation more when:**\n- Inputs are well-defined and logged the same way across branches\n- You can monitor errors quickly (and reverse decisions)\n- The decision is frequent, small, and time-sensitive (routing, prioritization)\n\n**Keep humans in the loop when:**\n- The metric is incentive-sensitive (people can ‘perform for the dashboard’)\n- Branch context matters (weather, local events, staffing shocks)\n- A wrong call is expensive or reputational\n\nRule of thumb: automate *decisions*, not *accountability*. A model can pick a queue order; a leader must own the tradeoff.",{"id":143,"name":144,"type":125,"typeVersion":16,"position":145,"parameters":146,"category":50,"deletable":8,"connectable":8},"node_text_messy","Make messy evidence usable (without sterilizing it)",[127,108],{"text":147},"Cleaning can quietly delete the truth—especially in conversations and branch events.\n\n**Do this instead:**\n- Keep a “raw lane” and a “decision lane.” Summarize, but don’t overwrite.\n- Preserve **who/when/where** (branch, time window, channel). Context is often the signal.\n- Treat contradictions as data: two teams disagreeing often means a definition gap, not a people problem.\n\n**Useful synthesis pattern:**\n1) What did we observe (verbatim where possible)?\n2) What would we expect if the story were true?\n3) What’s one cheap check by tomorrow?\n\nIf your insights never include uncertainty, you’re not ‘clear’—you’re just early wrong.",{"id":149,"name":150,"type":125,"typeVersion":16,"position":151,"parameters":152,"category":50,"deletable":8,"connectable":8},"node_text_compare","Comparing branches & attribution (what goes wrong first)",[127,114],{"text":153},"Branch comparisons fail in predictable ways:\n\n- **Different denominators:** one branch counts ‘leads’ as calls; another counts ‘leads’ as anyone who walked in.\n- **Different opportunity:** footfall, hours, staffing mix, local demand shocks.\n- **Channel mixing:** marketing ‘wins’ credited to the branch that closed, not the channel that created intent.\n\n**Make comparisons decision-grade:**\n- Compare *rates* only when the denominator is truly comparable.\n- Pair each metric with a “fairness note”: what makes this branch not like the others?\n- Use “matched windows” (same days of week, same promo periods).\n\nAttribution tip: if every channel claims the win, you don’t have attribution—you have a group project.",{"id":155,"name":156,"type":157,"typeVersion":16,"position":158,"parameters":159,"category":162,"deletable":8,"connectable":8},"node_handoff","Handoff to human","fallback",[127,120],{"handoffMessage":160,"departmentId":62,"departmentName":161},"Got it. This sounds like a high-stakes or context-heavy call. I’m handing this to a human so you can walk through the evidence and the decision together.","General","terminal",{"id":164,"name":165,"type":125,"typeVersion":16,"position":166,"parameters":168,"category":50,"deletable":8,"connectable":8},"node_text_default","Default: ask to choose a button",[127,167],560,{"text":169},"Choose one of the buttons above so I can route you to the right checks. If it’s sensitive or time-critical, pick **Talk to a human**.",[171,175,177,179,182,185,187,189,191,193,195,197,199,201,203],{"id":172,"source":34,"target":40,"sourceHandle":173,"targetHandle":30,"type":174},"edge_input_to_kb","output","edge",{"id":176,"source":40,"target":52,"sourceHandle":173,"targetHandle":30,"type":174},"edge_kb_to_menu",{"id":178,"source":52,"target":83,"sourceHandle":173,"targetHandle":30,"type":174},"edge_menu_to_if1",{"id":180,"source":83,"target":123,"sourceHandle":181,"targetHandle":30,"type":174},"edge_if1_true_to_trust","true",{"id":183,"source":83,"target":93,"sourceHandle":184,"targetHandle":30,"type":174},"edge_if1_false_to_if2","false",{"id":186,"source":93,"target":131,"sourceHandle":181,"targetHandle":30,"type":174},"edge_if2_true_to_dirty",{"id":188,"source":93,"target":99,"sourceHandle":184,"targetHandle":30,"type":174},"edge_if2_false_to_if3",{"id":190,"source":99,"target":137,"sourceHandle":181,"targetHandle":30,"type":174},"edge_if3_true_to_auto",{"id":192,"source":99,"target":105,"sourceHandle":184,"targetHandle":30,"type":174},"edge_if3_false_to_if4",{"id":194,"source":105,"target":143,"sourceHandle":181,"targetHandle":30,"type":174},"edge_if4_true_to_messy",{"id":196,"source":105,"target":111,"sourceHandle":184,"targetHandle":30,"type":174},"edge_if4_false_to_if5",{"id":198,"source":111,"target":149,"sourceHandle":181,"targetHandle":30,"type":174},"edge_if5_true_to_compare",{"id":200,"source":111,"target":117,"sourceHandle":184,"targetHandle":30,"type":174},"edge_if5_false_to_if6",{"id":202,"source":117,"target":155,"sourceHandle":181,"targetHandle":30,"type":174},"edge_if6_true_to_handoff",{"id":204,"source":117,"target":164,"sourceHandle":184,"targetHandle":30,"type":174},"edge_if6_false_to_default","automation",[27,28,29,207,208],"data-hygiene","automation-judgment",[210],"Calypso","intermediate","2026-06-15T11:03:48.705Z","/en/workflows/branch-signal-reality-audit",{"en":213},{"title":9,"description":216,"ogDescription":217,"twitterDescription":218,"canonicalPath":213,"robots":219,"schemaType":220,"alternates":221},"Route leaders to practical checks for noisy branch metrics, dirty signals, and when to trust automation vs human judgment.","A decision helper for branch teams: identify polished noise, catch dirty signals early, and choose when automation is safe vs when humans must decide.","Stop confident wrong decisions: triage branch metrics, spot dirty signals, and know when automation deserves trust vs when judgment must lead.","index,follow","HowTo",[222],{"hreflang":6,"href":213},1785947669155]