[{"data":1,"prerenderedAt":224},["ShallowReactive",2],{"/en/workflows/signal-sense-checks-for-branch-decisions":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":212,"verified":33,"featured":33,"date":213,"modified":213,"icon":7,"imageSrc":7,"path":214,"alternates":215,"seo":216},"725f4c8a-720b-45e0-a82c-25efe65a8ebd","signal-sense-checks-for-branch-decisions","en",null,true,"Signal Sense Checks for Branch Decisions","A decision-ready coach that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and decide when automation is safe vs. when judgment must lead.","## How it works\nThis workflow acts like a calm, sharp advisor in the moments right before a team turns “numbers” into a decision. It answers common questions about branch performance signals, attribution, and conversation evidence—without polishing away the messy parts that usually contain the truth.\n\nIt first checks your Calypso Knowledge Base for any internal definitions (what a metric really means, how it’s calculated, known caveats). Then it routes the user through a short menu of decision-shaped sense checks—so the team can spot dirty signal before a confident meeting goes off the rails.\n\n## Key features\n- Starts with a Knowledge Base policy so answers follow your internal metric definitions and caveats\n- Button-based menu to quickly route to the right “sense check” (trust, hygiene, automation, messy evidence, culture)\n- Practical guidance tuned for branch comparisons, attribution pitfalls, and conversational evidence\n- “Talk to an analyst” handoff path to route unclear or high-stakes cases to a human\n- Built to loop back to the menu so users can run multiple checks in one session\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a user opens the workflow entry point.\n2. **Knowledge Base grounding:** The **Knowledge Base Policy** activates to prioritize your internal definitions and known limitations before advice is given.\n3. **Choose a sense check:** A **button menu** asks what the user is trying to decide (e.g., which branch numbers to trust, how to spot dirty signal, when to trust automation).\n4. **Routing:** The workflow evaluates the clicked button through a sequence of **IF** checks.\n5. **Guidance delivery:** For the matched choice, a **text message** returns a field-tested checklist and common failure modes.\n6. **Continue or escalate:** After guidance, the workflow returns to the menu for another check—or routes to **Talk to an analyst** for human support.\n\n## Setup requirements\n- **Calypso Knowledge Base (recommended):** Populate definitions for your branch metrics, attribution rules, and known data caveats. No additional credentials are required in this workflow.\n- **Routing (optional but included):** Configure the destination department for the “Talk to an analyst” handoff in Calypso (department ID/name).",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":169,"routingEnabled":8,"active":33},"wf_signal_sense_checks_branch_decisions","calypso-public-library","1.0.0",1,[18,34,40,52,83,92,100,106,112,118,124,130,136,141,147,153,163],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"cfg1","Workflow settings","flow-configs",[23,24],80,60,{"name":9,"description":26,"tags":27,"triggerType":31},"Decision-shaped sense checks to separate trustworthy branch signals from polished noise, spot dirty signal early, and apply automation guardrails.",[28,29,30],"signal-quality","branch-metrics","decision-systems","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":39,"category":31,"deletable":33,"connectable":8},"in1","Start",[23,38],180,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"kb1","Knowledge Base grounding","knowledge-base-policy",[45,38],320,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":47,"activationOpener":48,"personalization":50},"ai_sticky_release",{"enabled":8,"instruction":49},"Use our internal metric definitions and caveats. Be practical, plainspoken, and decision-focused. Flag likely failure modes and what to verify next.",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"menu1","Pick a sense check","interactive-message",[57,38],580,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Signal sense checks","What are you trying to decide right now? Pick one and I’ll give you a quick, decision-grade check (no academic fog, no false confidence).","Tip: If it looks too clean, the mess moved upstream.","",[65,68,71,74,77,80],{"id":66,"title":67},"trust_branch_numbers","Trust numbers",{"id":69,"title":70},"spot_dirty_signal","Dirty signal",{"id":72,"title":73},"automation_vs_judgment","Automation guardrail",{"id":75,"title":76},"messy_evidence_insight","Messy evidence",{"id":78,"title":79},"build_signal_culture","Signal culture",{"id":81,"title":82},"talk_to_analyst","Talk to analyst",{"id":84,"name":85,"type":86,"typeVersion":16,"position":87,"parameters":89,"category":91,"deletable":8,"connectable":8},"if_trust","IF: Trust branch numbers","if",[88,38],820,{"buttonId":66,"operator":90},"equals","routing",{"id":93,"name":94,"type":95,"typeVersion":16,"position":96,"parameters":98,"category":51,"deletable":8,"connectable":8},"txt_trust","Trust check: branch numbers","text-message",[97,23],1060,{"text":99},"Here’s how to tell decision-grade branch numbers from polished noise:\n\n1) **Ask “what would make this number lie?”** (timing shifts, definition drift, routing changes, incentives).\n2) **Prefer counts you can audit**: transactions, calls, appointments kept. Be skeptical of composite “scores” unless you can decompose them.\n3) **Check denominator stability**: branches ‘improving’ because the denominator shrank is a classic.\n4) **Look for boundary changes**: territory shifts, hours, staffing, product mix. A branch didn’t ‘learn’ overnight—your system likely moved.\n5) **Compare like-for-like windows**: same weekday mix, same seasonality band, same campaign exposure.\n6) **Triangulate**: one metric + one operational constraint + one customer signal beats a single dashboard hero number.\n\nIf this is high-stakes, use **Talk to an analyst** for a review.",{"id":101,"name":102,"type":86,"typeVersion":16,"position":103,"parameters":105,"category":91,"deletable":8,"connectable":8},"if_dirty","IF: Spot dirty signal",[88,104],280,{"buttonId":69,"operator":90},{"id":107,"name":108,"type":95,"typeVersion":16,"position":109,"parameters":110,"category":51,"deletable":8,"connectable":8},"txt_dirty","Dirty signal: early warnings",[97,38],{"text":111},"Dirty data rarely looks dirty. It looks *confident*. Here are the tells:\n\n- **Too-smooth trend lines** right after a process/tool change (that’s usually instrumentation, not performance).\n- **Sudden cross-branch convergence** (everyone ‘improves’ together) — often a definition or routing change.\n- **Missingness that isn’t random**: the hardest cases disappear first (e.g., unlogged calls, skipped dispositions).\n- **Outliers that are ‘explained’ instantly** in the meeting. Fast explanations are where wrong decisions are born.\n- **Lag mismatch**: leading indicators move, but the supposed outcomes don’t (or vice versa).\n\nQuick checks to run before the meeting:\n1) Ask for a **top-10 underlying records** sample.\n2) Check **before/after** any policy/tool change date.\n3) Verify **unique entities** (customers/leads) vs raw events (calls/clicks).\n\nIf this decision can’t afford a false positive, use **Talk to an analyst**.",{"id":113,"name":114,"type":86,"typeVersion":16,"position":115,"parameters":117,"category":91,"deletable":8,"connectable":8},"if_auto","IF: Automation vs judgment",[88,116],380,{"buttonId":72,"operator":90},{"id":119,"name":120,"type":95,"typeVersion":16,"position":121,"parameters":122,"category":51,"deletable":8,"connectable":8},"txt_auto","Guardrails: automation vs judgment",[97,104],{"text":123},"When should leaders trust automation—and when should they grab the wheel?\n\n**Automation is safe when:**\n- The input signal is **stable, well-defined, and routinely audited**.\n- Mistakes are **reversible** and low-cost.\n- The model/rule has a clear **‘why’** you can explain in one breath.\n\n**Human judgment must lead when:**\n- Incentives can game the metric (people will optimize *the number*, not the outcome).\n- The context changes fast (seasonality, staffing, local events, new product, new routing).\n- The downside is asymmetric (one bad call costs more than ten good ones help).\n\nPractical guardrail: **Automate the boring 80% + escalate the weird 20%**. If the system can’t tell you what “weird” looks like, it’s not ready to drive.\n\nFor a decision review, use **Talk to an analyst**.",{"id":125,"name":126,"type":86,"typeVersion":16,"position":127,"parameters":129,"category":91,"deletable":8,"connectable":8},"if_messy","IF: Messy evidence to insight",[88,128],480,{"buttonId":75,"operator":90},{"id":131,"name":132,"type":95,"typeVersion":16,"position":133,"parameters":134,"category":51,"deletable":8,"connectable":8},"txt_messy","Make messy evidence usable",[97,116],{"text":135},"Turning messy evidence into usable insight (without cleaning away the truth):\n\n1) **Keep the mess, label it.** Don’t delete ‘bad’ records—tag them (unknown, duplicate, delayed, unclassified). Deleting hides systemic issues.\n2) **Separate signal from measurement.** A branch can improve while its logging worsens (or vice versa). Track both.\n3) **Use ‘minimum viable truth.’** What’s the simplest slice you trust? Start there, then widen.\n4) **Prefer decision thresholds over precision.** You rarely need 2 decimal places; you need ‘act / don’t act / investigate’.\n5) **Write the rival hypothesis.** If Branch A “wins,” what non-performance reason could explain it (mix, routing, incentive, exposure)?\n\nIf you need help turning this into a decision memo, use **Talk to an analyst**.",{"id":137,"name":138,"type":86,"typeVersion":16,"position":139,"parameters":140,"category":91,"deletable":8,"connectable":8},"if_culture","IF: Build signal culture",[88,57],{"buttonId":78,"operator":90},{"id":142,"name":143,"type":95,"typeVersion":16,"position":144,"parameters":145,"category":51,"deletable":8,"connectable":8},"txt_culture","Culture: decisions, not slides",[97,128],{"text":146},"A strong signal culture makes decisions happen—without worshipping dashboards.\n\nHabits that work:\n- **One metric, one owner, one definition.** Ambiguity is where meetings go to die.\n- **Every metric gets a ‘how it fails’ footnote.** If it has no caveats, it’s probably misunderstood.\n- **Decision logs beat slide decks.** Record: what we decided, what we believed, what we’ll check next.\n- **Reward escalations.** People should get credit for saying “this signal is dirty” *before* the decision.\n- **Triangulate by default.** No branch comparison without: volume + mix + at least one customer/conversation cue.\n\nIf you’re rolling this out and want guardrails, use **Talk to an analyst**.",{"id":148,"name":149,"type":86,"typeVersion":16,"position":150,"parameters":152,"category":91,"deletable":8,"connectable":8},"if_handoff","IF: Talk to an analyst",[88,151],680,{"buttonId":81,"operator":90},{"id":154,"name":155,"type":156,"typeVersion":16,"position":157,"parameters":158,"category":162,"deletable":8,"connectable":8},"fb_analyst","Handoff to analyst","fallback",[97,151],{"handoffMessage":159,"departmentId":160,"departmentName":161},"Got it. I’m handing this to an analyst so we can sanity-check the signal and the decision risk. If you can, share: the metric definition, date range, what changed recently, and what decision is on the table.","analytics","Analytics","terminal",{"id":164,"name":165,"type":95,"typeVersion":16,"position":166,"parameters":167,"category":51,"deletable":8,"connectable":8},"txt_retry","No selection",[97,57],{"text":168},"I didn’t catch a button selection. Please choose one of the options in the menu to get the right sense check.",[170,175,177,179,182,185,187,189,191,193,195,197,199,201,203],{"id":171,"source":35,"target":41,"sourceHandle":172,"targetHandle":173,"type":174},"e_in1_kb1","out","in","edge",{"id":176,"source":41,"target":53,"sourceHandle":172,"targetHandle":173,"type":174},"e_kb1_menu1",{"id":178,"source":53,"target":84,"sourceHandle":172,"targetHandle":173,"type":174},"e_menu1_if_trust",{"id":180,"source":84,"target":93,"sourceHandle":181,"targetHandle":173,"type":174},"e_if_trust_true_txt_trust","true",{"id":183,"source":84,"target":101,"sourceHandle":184,"targetHandle":173,"type":174},"e_if_trust_false_if_dirty","false",{"id":186,"source":101,"target":107,"sourceHandle":181,"targetHandle":173,"type":174},"e_if_dirty_true_txt_dirty",{"id":188,"source":101,"target":113,"sourceHandle":184,"targetHandle":173,"type":174},"e_if_dirty_false_if_auto",{"id":190,"source":113,"target":119,"sourceHandle":181,"targetHandle":173,"type":174},"e_if_auto_true_txt_auto",{"id":192,"source":113,"target":125,"sourceHandle":184,"targetHandle":173,"type":174},"e_if_auto_false_if_messy",{"id":194,"source":125,"target":131,"sourceHandle":181,"targetHandle":173,"type":174},"e_if_messy_true_txt_messy",{"id":196,"source":125,"target":137,"sourceHandle":184,"targetHandle":173,"type":174},"e_if_messy_false_if_culture",{"id":198,"source":137,"target":142,"sourceHandle":181,"targetHandle":173,"type":174},"e_if_culture_true_txt_culture",{"id":200,"source":137,"target":148,"sourceHandle":184,"targetHandle":173,"type":174},"e_if_culture_false_if_handoff",{"id":202,"source":148,"target":154,"sourceHandle":181,"targetHandle":173,"type":174},"e_if_handoff_true_fb_analyst",{"id":204,"source":148,"target":164,"sourceHandle":184,"targetHandle":173,"type":174},"e_if_handoff_false_txt_retry","automation",[28,29,30,207,208],"data-hygiene","automation-guardrails",[210],"Calypso Knowledge Base","intermediate","Calypso","2026-05-20T11:03:59.602Z","/en/workflows/signal-sense-checks-for-branch-decisions",{"en":214},{"title":9,"description":217,"ogDescription":218,"twitterDescription":219,"canonicalPath":214,"robots":220,"schemaType":221,"alternates":222},"Turn messy branch signals into safer decisions with quick checks for dirty data, metric trust, and when automation needs human judgment.","A practical workflow to sanity check branch numbers, spot dirty signal early, and decide when to trust automation vs. human judgment—grounded in your KB.","Stop confident wrong decisions: quick sense checks for branch metrics, dirty signal, attribution traps, and automation guardrails—grounded in your KB.","index,follow","HowTo",[223],{"hreflang":6,"href":214},1780761214159]