[{"data":1,"prerenderedAt":245},["ShallowReactive",2],{"/en/workflows/branch-signal-confidence-screener":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":227,"tags":228,"integrations":230,"difficulty":232,"author":233,"verified":33,"featured":33,"date":234,"modified":234,"icon":7,"imageSrc":7,"path":235,"alternates":236,"seo":237},"76f0d04c-b89d-4597-a346-1c2859823a0f","branch-signal-confidence-screener","en",null,true,"Branch Signal Confidence Screener","A guided menu that helps branch leaders sanity-check metrics, spot dirty signal, and choose when to trust automation vs. human judgment—before the meeting gets confident and wrong.","## How it works\nThis workflow gives branch leaders a fast, decision-shaped “reality check” on the signals they’re about to use. Instead of debating dashboards, it routes them through a short menu: which numbers to trust, how to spot dirty signal early, when automation is safe, and what teams routinely misread when comparing branches.\n\nIt’s designed for the moment right before a confident meeting goes off the rails—when the data looks polished, the story feels neat, and the risk is highest. You’ll get crisp prompts that favor usable judgment over academic purity.\n\n## Key features\n- Knowledge-base policy sets a practical, plain-English advisory tone (no slide-deck cosplay).\n- Button-based menu routes users to the exact decision check they need—fast.\n- “Trust vs. noise” guidance tailored to branch metrics, conversations, and attribution comparisons.\n- Clear guardrails on when to trust automation and when humans must step in.\n- Optional handoff to a human owner when the situation is high-stakes or unclear.\n\n## Step-by-step\n1. **Input trigger** starts the workflow when a user opens the conversation.\n2. **Knowledge Base Policy** applies the workflow’s guidance style (direct, practical, anti-false-confidence).\n3. **Interactive menu** asks what the user needs help with (trust numbers, dirty signal, automation vs. judgment, messy evidence, branch comparisons, signal culture, or human help).\n4. **Routing checks (IF nodes)** evaluate which button was clicked.\n5. **Text guidance** returns a concise, operator-ready checklist for the selected topic.\n6. **Human handoff (optional)** routes to a fallback path when the user selects “Talk to a human.”\n\n## Setup requirements\n- No credentials required.\n- Publish this workflow to a Calypso Inbox channel where branch leaders or operators can message in.\n- (Optional) If you use department routing, set the fallback department to the correct owner in your Calypso workspace.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":188,"routingEnabled":8,"active":33},"wf_branch_signal_confidence_screener_v1","calypso-public-library","1.0.0",1,[18,34,41,53,88,97,106,111,118,124,130,136,143,149,156,162,169,174,182],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":24,"category":32,"deletable":33,"connectable":33},"node_flow_cfg","Workflow settings","flow-configs",[23,23],80,{"name":9,"description":25,"tags":26,"triggerType":31},"Menu-guided checks to help branch teams trust the right signals, spot dirty data early, and decide when automation needs human judgment.",[27,28,29,30],"decision-signals","branch-metrics","data-quality","automation-judgment","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],120,240,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb_policy","Decision-signal guidance policy","knowledge-base-policy",[46,39],360,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":48,"activationOpener":49,"personalization":51},"default",{"enabled":8,"instruction":50},"Be a practical advisor. Favor decision-ready checks over theory. Assume bad data often looks clean. Use plain English, light wit, and crisp next steps. If something is high-stakes or ambiguous, recommend human review.",{"useContactName":8},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"node_menu","Pick a decision check","interactive-message",[58,39],620,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":87,"ctaUrl":87},"button","Signal reality check","Choose what you’re trying to decide. I’ll give you a short checklist that avoids confident wrong conclusions.","Tip: High stakes? Watch for polished noise.","Options",[66,69,72,75,78,81,84],{"id":67,"title":68},"trust_branch_numbers","Trust the numbers",{"id":70,"title":71},"spot_dirty_signal","Spot dirty signal",{"id":73,"title":74},"automation_vs_judgment","Automation vs humans",{"id":76,"title":77},"messy_evidence","Use messy evidence",{"id":79,"title":80},"compare_branches_attribution","Compare branches",{"id":82,"title":83},"build_signal_culture","Signal culture",{"id":85,"title":86},"talk_to_human","Talk to a human","",{"id":89,"name":90,"type":91,"typeVersion":16,"position":92,"parameters":94,"category":96,"deletable":8,"connectable":8},"node_if_trust_numbers","If: Which numbers to trust","if",[93,39],860,{"buttonId":67,"operator":95},"equals","routing",{"id":98,"name":99,"type":100,"typeVersion":16,"position":101,"parameters":104,"category":52,"deletable":8,"connectable":8},"node_msg_trust_numbers","Trustworthy vs polished noise","text-message",[102,103],1120,160,{"text":105},"Here’s what typically *deserves trust* vs. what often looks great right before it lies to you:\n\nTrust these more:\n- Counts tied to a clear event: “application submitted,” “cash posted,” “appointment completed.”\n- Metrics with a stable definition *and* an audit trail (you can point to rows, not vibes).\n- Ratios with a denominator you’d bet your job on (e.g., eligible customers, not “reachable”).\n\nTreat these as polished noise until proven:\n- Anything that can be ‘improved’ by re-labeling (lead quality, intent, engagement).\n- Branch comparisons where one branch logs differently (same work, different paperwork).\n- Metrics that move *only* in the dashboard, not in customer reality.\n\nQuick test before you present it: “If this number doubled tomorrow, what physical thing would we notice by lunch?” If the answer is ‘nothing,’ it’s not decision-grade yet.",{"id":107,"name":108,"type":91,"typeVersion":16,"position":109,"parameters":110,"category":96,"deletable":8,"connectable":8},"node_if_dirty_signal","If: Spot dirty signal fast",[93,46],{"buttonId":70,"operator":95},{"id":112,"name":113,"type":100,"typeVersion":16,"position":114,"parameters":116,"category":52,"deletable":8,"connectable":8},"node_msg_dirty_signal","Dirty signal tripwires",[102,115],320,{"text":117},"Dirty signal usually shows up as *neat* numbers with messy causes. Tripwires to check before the meeting gets confident:\n\n- Sudden step-changes that coincide with a process change, training, comp plan, or new script.\n- “Miracle” improvements concentrated in one branch, one week, or one person.\n- Missingness that’s not random (e.g., the hardest cases mysteriously have no notes).\n- Perfectly round rates (80%, 90%)—humans love rounding; reality doesn’t.\n- Metrics improving while downstream outcomes don’t (more leads, same bookings).\n\nPractical move: pick 10 recent cases and trace them end-to-end. If you can’t explain *where the number came from* without squinting, don’t let it drive the decision.",{"id":119,"name":120,"type":91,"typeVersion":16,"position":121,"parameters":123,"category":96,"deletable":8,"connectable":8},"node_if_automation_vs_judgment","If: Automation vs human judgment",[93,122],480,{"buttonId":73,"operator":95},{"id":125,"name":126,"type":100,"typeVersion":16,"position":127,"parameters":128,"category":52,"deletable":8,"connectable":8},"node_msg_automation_vs_judgment","When to trust automation",[102,122],{"text":129},"Automation is great at consistency. It’s terrible at context—especially when incentives change.\n\nTrust automation more when:\n- The rule is simple, repeatable, and you can audit it.\n- Errors are cheap and reversible (routing a message, not denying credit).\n- The signal is high-volume and stable (lots of similar cases).\n\nInsist on human judgment when:\n- The decision is irreversible or high-impact.\n- Branch behavior can ‘game’ the inputs (logging, categorization, timing).\n- You’re seeing edge cases, low volume, or a brand-new process.\n\nA good default: automate the *routine*, escalate the *weird*, and review anything that becomes suddenly ‘too good.’",{"id":131,"name":132,"type":91,"typeVersion":16,"position":133,"parameters":135,"category":96,"deletable":8,"connectable":8},"node_if_messy_evidence","If: Use messy evidence",[93,134],600,{"buttonId":76,"operator":95},{"id":137,"name":138,"type":100,"typeVersion":16,"position":139,"parameters":141,"category":52,"deletable":8,"connectable":8},"node_msg_messy_evidence","Keep the truth while making it usable",[102,140],640,{"text":142},"Turning messy evidence into insight isn’t about making it pretty—it’s about not sanding off the truth.\n\nDo this:\n- Keep the raw notes/events. Summaries should link back to examples.\n- Track *why* something is missing (unknown vs not collected vs not applicable).\n- Separate “what happened” from “why we think it happened.”\n\nAvoid this:\n- Over-cleaning away outliers. Outliers are often where the process is broken.\n- Collapsing categories too early (“other” becomes a landfill).\n- Averaging away branch differences that matter operationally.\n\nUseful compromise: standardize *how you log*, not *what reality must look like.* Then build decisions on patterns you can still trace to real cases.",{"id":144,"name":145,"type":91,"typeVersion":16,"position":146,"parameters":148,"category":96,"deletable":8,"connectable":8},"node_if_compare_branches","If: Compare branches & attribution",[93,147],720,{"buttonId":79,"operator":95},{"id":150,"name":151,"type":100,"typeVersion":16,"position":152,"parameters":154,"category":52,"deletable":8,"connectable":8},"node_msg_compare_branches","Branch comparison misreads",[102,153],800,{"text":155},"What teams misread first when comparing branches, conversations, and attribution:\n\n1) **Different logging masquerading as performance.** One branch is strict; another is generous. Same reality, different data.\n2) **Case-mix differences.** A branch serving harder customers will look “worse” on naive rates.\n3) **Timing artifacts.** End-of-month pushes, delayed posting, and backlog clearance create fake winners.\n4) **Attribution fog.** If the channel definition changes, the “best channel” will follow the definition.\n\nMinimum fairness checklist:\n- Same definitions, same time windows, same denominator rules.\n- Compare distributions, not just averages (medians, ranges, and tails).\n- Pull 5 examples from each branch that represent ‘typical’ and ‘painful’ cases.\n\nIf you can’t explain the difference with concrete examples, you’re probably looking at measurement—not performance.",{"id":157,"name":158,"type":91,"typeVersion":16,"position":159,"parameters":161,"category":96,"deletable":8,"connectable":8},"node_if_signal_culture","If: Build a signal culture",[93,160],840,{"buttonId":82,"operator":95},{"id":163,"name":164,"type":100,"typeVersion":16,"position":165,"parameters":167,"category":52,"deletable":8,"connectable":8},"node_msg_signal_culture","Make signals help decisions (not slides)",[102,166],960,{"text":168},"A healthy signal culture doesn’t produce more charts. It produces faster, safer decisions.\n\nHabits that work:\n- **Decision first:** every metric should answer “What would we do if this moved?”\n- **One owner per definition:** otherwise definitions ‘evolve’ right when incentives do.\n- **Two levels of truth:** a headline metric *and* 3–5 concrete examples behind it.\n- **Pre-mortems:** ask “How could this metric fool us next month?” (It will try.)\n- **Celebrate catches, not just wins:** teams should get credit for finding measurement bugs.\n\nWitty but real rule: if your numbers never embarrass you, you’re not looking closely enough.",{"id":170,"name":171,"type":91,"typeVersion":16,"position":172,"parameters":173,"category":96,"deletable":8,"connectable":8},"node_if_human","If: Talk to a human",[93,166],{"buttonId":85,"operator":95},{"id":175,"name":176,"type":177,"typeVersion":16,"position":178,"parameters":179,"category":181,"deletable":8,"connectable":8},"node_fallback_handoff","Handoff to human","fallback",[102,102],{"handoffMessage":180,"departmentId":87,"departmentName":87},"Got it—this sounds worth a human read. Share the decision you’re making, the metric(s) in question, and what would change if you’re wrong.","terminal",{"id":183,"name":184,"type":100,"typeVersion":16,"position":185,"parameters":186,"category":52,"deletable":8,"connectable":8},"node_msg_no_match","No selection matched",[102,39],{"text":187},"I didn’t catch a selection. Pick an option from the buttons so I can route you to the right reality check.",[189,193,195,197,200,203,205,207,209,211,213,215,217,219,221,223,225],{"id":190,"source":35,"target":42,"sourceHandle":191,"targetHandle":192,"type":48},"conn_input_to_kb","out","in",{"id":194,"source":42,"target":54,"sourceHandle":191,"targetHandle":192,"type":48},"conn_kb_to_menu",{"id":196,"source":54,"target":89,"sourceHandle":191,"targetHandle":192,"type":48},"conn_menu_to_if1",{"id":198,"source":89,"target":98,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if1_true_to_msg","true",{"id":201,"source":89,"target":107,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if1_false_to_if2","false",{"id":204,"source":107,"target":112,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if2_true_to_msg",{"id":206,"source":107,"target":119,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if2_false_to_if3",{"id":208,"source":119,"target":125,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if3_true_to_msg",{"id":210,"source":119,"target":131,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if3_false_to_if4",{"id":212,"source":131,"target":137,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if4_true_to_msg",{"id":214,"source":131,"target":144,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if4_false_to_if5",{"id":216,"source":144,"target":150,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if5_true_to_msg",{"id":218,"source":144,"target":157,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if5_false_to_if6",{"id":220,"source":157,"target":163,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if6_true_to_msg",{"id":222,"source":157,"target":170,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if6_false_to_if7",{"id":224,"source":170,"target":175,"sourceHandle":199,"targetHandle":192,"type":48},"conn_if7_true_to_handoff",{"id":226,"source":170,"target":183,"sourceHandle":202,"targetHandle":192,"type":48},"conn_if7_false_to_nomatch","automation",[27,28,29,30,229],"signal-culture",[231],"Calypso Inbox","intermediate","Calypso","2026-05-05T11:03:44.808Z","/en/workflows/branch-signal-confidence-screener",{"en":235},{"title":9,"description":238,"ogDescription":239,"twitterDescription":240,"canonicalPath":235,"robots":241,"schemaType":242,"alternates":243},"Guide branch teams to trust the right numbers, spot dirty signal early, and choose when automation needs human judgment.","A practical menu to sanity check branch metrics, detect polished noise, and prevent confident wrong decisions—plus optional human handoff.","Sanity check branch signals fast: what to trust, what’s noise, when automation is safe, and when humans must step in.","index,follow","HowTo",[244],{"hreflang":6,"href":235},1778614431175]