[{"data":1,"prerenderedAt":228},["ShallowReactive",2],{"/en/workflows/branch-signals-trust-checks-before-you-decide":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":208,"tags":209,"integrations":213,"difficulty":215,"author":216,"verified":33,"featured":33,"date":217,"modified":217,"icon":7,"imageSrc":7,"path":218,"alternates":219,"seo":220},"8458d634-3ce6-425a-a1e4-a8f055ebd14d","branch-signals-trust-checks-before-you-decide","en",null,true,"Branch Signals: Trust Checks Before You Decide","A decision-focused assistant that helps teams separate trustworthy branch metrics from polished noise, spot dirty signals early, and choose when automation is safe vs when human judgment must lead.","## How it works\nThis workflow turns “we have numbers” into “we have decision-ready evidence.” It guides operators through quick, concrete checks that catch the most common ways branch metrics, conversations, and attribution get quietly wrong—right before a confident meeting locks in a bad call.\n\nIt starts with a knowledge-backed primer (so your team isn’t reinventing signal hygiene every time), then routes the user to the exact coaching they need: trust tests for branch metrics, dirty-signal detection, automation vs judgment calls, apples-to-oranges branch comparisons, and practical habits that build a signal culture that produces decisions (not just slides).\n\n## Key features\n- Knowledge-base assisted coaching before routing, so answers stay consistent across teams.\n- A single menu of decision-shaped paths (trust checks, dirty signal, automation vs judgment, comparisons, culture).\n- Clear “what to trust / what to doubt / what to do next” guidance in every branch.\n- Human handoff option for cases that shouldn’t be automated.\n- Works cleanly in WhatsApp-style interactive buttons for fast triage.\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a user opens the assistant (Input).\n2. **Set the guardrails:** The **Knowledge Base Policy** activates decision-signal guidance and then proceeds to routing.\n3. **Choose the decision you’re trying to make:** The user selects one option from an interactive button menu.\n4. **Route to the right coaching:** The workflow checks the selected button and sends the matching playbook:\n   1. **Which branch numbers deserve trust?** Practical trust tests and “polished noise” flags.\n   2. **How to spot dirty signal early** before the meeting goes off the rails.\n   3. **Automation vs human judgment:** when to trust the system, and when to slow down.\n   4. **Comparing branches & attribution:** what teams misread most often.\n   5. **Build a signal culture:** habits that turn evidence into decisions.\n5. **Handoff when needed:** If the user asks for a human, the workflow routes to a handoff (Fallback).\n\n## Setup requirements\n- **WhatsApp channel connected in Calypso** (or the Calypso channel where interactive buttons are supported).\n- **Optional but recommended:** Populate your Calypso Knowledge Base with your internal definitions (e.g., “qualified conversation,” “branch visit,” “conversion”) and known data caveats.\n- No additional credentials are required beyond your Calypso channel setup.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":172,"routingEnabled":8,"active":33},"wf_branch_signal_trust_checks_v1","calypso-public-library","1.0.0",1,[18,34,41,53,84,93,101,107,113,119,125,131,137,143,149,155,165],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_cfg","Flow settings","flow-configs",[23,24],-520,-40,{"name":9,"description":26,"tags":27,"triggerType":31},"Decision-focused assistant to separate trustworthy branch signals from polished noise, spot dirty data early, and choose when automation vs judgment should lead.",[28,29,30],"signal-quality","decision-systems","branch-ops","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":40,"category":31,"deletable":33,"connectable":8},"node_input","Start",[38,39],-300,120,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb_policy","Signal guidance policy","knowledge-base-policy",[46,39],-60,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":48,"activationOpener":49,"personalization":51},"ai_sticky_release",{"enabled":8,"instruction":50},"You’re making a decision, not writing a report. I’ll help you stress-test the signals (branch numbers, conversations, attribution) so you don’t get confidently misled. Pick what you’re deciding.",{"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 signal problem","interactive-message",[58,39],220,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":64,"ctaUrl":64},"button","Signal checks, without the fluff","What are you trying to decide right now? Choose one and I’ll give you the fastest trust test (and the most common ways teams get fooled).","Tip: If a number looks clean, that’s when to get suspicious.","",[66,69,72,75,78,81],{"id":67,"title":68},"btn_trust_branch_numbers","Trust branch numbers",{"id":70,"title":71},"btn_spot_dirty_signal","Spot dirty signal",{"id":73,"title":74},"btn_automation_vs_judgment","Automation vs human",{"id":76,"title":77},"btn_compare_branches_attr","Compare branches",{"id":79,"title":80},"btn_build_signal_culture","Signal culture",{"id":82,"title":83},"btn_handoff_human","Talk to a human",{"id":85,"name":86,"type":87,"typeVersion":16,"position":88,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_trust","If: trust branch numbers","if",[89,24],520,{"buttonId":67,"operator":91},"equals","routing",{"id":94,"name":95,"type":96,"typeVersion":16,"position":97,"parameters":99,"category":52,"deletable":8,"connectable":8},"node_msg_trust","Trust checks for branch numbers","text-message",[98,24],820,{"text":100},"Here’s how to tell which branch numbers deserve trust (and which are polished noise):\n\n1) **Define the unit first**: “visits,” “conversations,” “leads,” “revenue” — pick one primary unit per decision.\n2) **Look for counting rules that change by branch**: Different logging habits = fake performance gaps.\n3) **Check denominator health** (the part everyone forgets): If one branch has fewer opportunities, the rate can look heroic for the wrong reason.\n4) **Watch for ‘too-smooth’ trends**: Real operations are lumpy. Perfect lines often mean backfilled data, batching, or a dashboard averaging away pain.\n5) **Confirm timing alignment**: Are you comparing the same weeks, same promo periods, same staffing levels?\n\nFast next step: tell me the **metric**, the **time window**, and which **branches** you’re comparing. I’ll tell you what typically breaks first.",{"id":102,"name":103,"type":87,"typeVersion":16,"position":104,"parameters":106,"category":92,"deletable":8,"connectable":8},"node_if_dirty","If: spot dirty signal",[89,105],80,{"buttonId":70,"operator":91},{"id":108,"name":109,"type":96,"typeVersion":16,"position":110,"parameters":111,"category":52,"deletable":8,"connectable":8},"node_msg_dirty","Dirty signal early warnings",[98,105],{"text":112},"Dirty signal usually looks *reasonable* right up until someone bets their budget on it. Early warning signs:\n\n- **Sudden improvement with no operational story** (no staffing change, no promo, no process shift).\n- **One field drives everything** (e.g., a single tag, source, or status flip makes the dashboard ‘win’).\n- **Missingness isn’t random**: if busy branches log less, performance looks magically better.\n- **Attribution that always flatters the newest campaign**: that’s often a tracking change, not demand.\n- **Conversation counts rising while outcomes don’t**: can be duplicates, spam, or reopened threads.\n\nQuick test (5 minutes): pick 10 records from the “best” branch/week and ask: **Would a skeptical human agree this counts?** If you want, share what’s ‘up and to the right’ and I’ll suggest the most likely contamination source.",{"id":114,"name":115,"type":87,"typeVersion":16,"position":116,"parameters":118,"category":92,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[89,117],200,{"buttonId":73,"operator":91},{"id":120,"name":121,"type":96,"typeVersion":16,"position":122,"parameters":123,"category":52,"deletable":8,"connectable":8},"node_msg_auto","When to trust automation vs humans",[98,117],{"text":124},"Automation is great at consistency. Humans are great at context. The mistake is asking either one to do the other’s job.\n\n**Trust automation when:**\n- The definition is stable (same counting rules week to week).\n- Errors are small and symmetric (noise cancels out rather than biasing one branch).\n- The decision is reversible (you can undo it next week).\n\n**Bring human judgment when:**\n- The metric is new, recently changed, or politically important.\n- Branches differ in process (walk-ins vs appointments, different staffing, different logging discipline).\n- The decision is high-stakes or hard to reverse (headcount, closures, major budget shifts).\n\nRule of thumb: if you can’t explain **why the number moved** in plain language, don’t automate the decision that depends on it.",{"id":126,"name":127,"type":87,"typeVersion":16,"position":128,"parameters":130,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[89,129],320,{"buttonId":76,"operator":91},{"id":132,"name":133,"type":96,"typeVersion":16,"position":134,"parameters":135,"category":52,"deletable":8,"connectable":8},"node_msg_compare","Branch comparison & attribution traps",[98,129],{"text":136},"Most branch comparisons fail for boring reasons (which is why they keep failing):\n\n1) **Different opportunity mix**: Branch A gets easier cases; Branch B gets messier ones. Compare like-with-like where possible.\n2) **Different logging behavior**: “Good” branches might just be better at paperwork.\n3) **Rate vs volume confusion**: A higher conversion rate on tiny volume is not operational proof.\n4) **Attribution credit inflation**: The channel that touches last often looks like the hero.\n5) **Calendar traps**: holidays, local events, staffing gaps — the map matters.\n\nPractical move: before ranking branches, write the 3 assumptions that *must* be true for the comparison to be fair. If any are shaky, treat the ranking as a hypothesis, not a verdict.",{"id":138,"name":139,"type":87,"typeVersion":16,"position":140,"parameters":142,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: build a signal culture",[89,141],440,{"buttonId":79,"operator":91},{"id":144,"name":145,"type":96,"typeVersion":16,"position":146,"parameters":147,"category":52,"deletable":8,"connectable":8},"node_msg_culture","Build a signal culture (decisions > slides)",[98,141],{"text":148},"A strong signal culture doesn’t create more dashboards. It creates faster, cleaner decisions.\n\nTry these habits:\n- **One metric, one decision**: If the number can’t change a choice, don’t promote it.\n- **Name the failure mode** on every chart: “This breaks if duplicates spike” or “This breaks if logging drops when busy.”\n- **Keep a ‘definition changelog’**: when counting rules change, your trendline is now two stories.\n- **Reward truth-telling**: don’t punish branches for reporting mess; punish hiding it.\n- **Make sampling normal**: 10-record spot checks beat 10-slide decks.\n\nIf you tell me what decision keeps getting stuck (budget, staffing, marketing, training), I can suggest which 2–3 signals are worth standardizing first.",{"id":150,"name":151,"type":87,"typeVersion":16,"position":152,"parameters":154,"category":92,"deletable":8,"connectable":8},"node_if_handoff","If: talk to a human",[89,153],560,{"buttonId":82,"operator":91},{"id":156,"name":157,"type":158,"typeVersion":16,"position":159,"parameters":160,"category":164,"deletable":8,"connectable":8},"node_fallback","Handoff to team","fallback",[98,153],{"handoffMessage":161,"departmentId":162,"departmentName":163},"Got it — I’m routing this to a teammate. To speed things up, share: (1) the decision you’re making, (2) the metric(s) in question, (3) which branches/time window, and (4) what ‘looks too good to be true’.","ops-analytics","Ops Analytics","terminal",{"id":166,"name":167,"type":158,"typeVersion":16,"position":168,"parameters":170,"category":164,"deletable":8,"connectable":8},"node_fallback_default","Default fallback",[89,169],700,{"handoffMessage":171,"departmentId":162,"departmentName":163},"I didn’t catch that selection. If you share what decision you’re making (and the metric), I can route you—or I can hand you to a teammate.",[173,178,180,182,185,188,190,192,194,196,198,200,202,204,206],{"id":174,"source":35,"target":42,"sourceHandle":175,"targetHandle":176,"type":177},"conn_input_to_kb","out","in","edge",{"id":179,"source":42,"target":54,"sourceHandle":175,"targetHandle":176,"type":177},"conn_kb_to_menu",{"id":181,"source":54,"target":85,"sourceHandle":175,"targetHandle":176,"type":177},"conn_menu_to_if_trust",{"id":183,"source":85,"target":94,"sourceHandle":184,"targetHandle":176,"type":177},"conn_if_trust_true","true",{"id":186,"source":85,"target":102,"sourceHandle":187,"targetHandle":176,"type":177},"conn_if_trust_false","false",{"id":189,"source":102,"target":108,"sourceHandle":184,"targetHandle":176,"type":177},"conn_if_dirty_true",{"id":191,"source":102,"target":114,"sourceHandle":187,"targetHandle":176,"type":177},"conn_if_dirty_false",{"id":193,"source":114,"target":120,"sourceHandle":184,"targetHandle":176,"type":177},"conn_if_auto_true",{"id":195,"source":114,"target":126,"sourceHandle":187,"targetHandle":176,"type":177},"conn_if_auto_false",{"id":197,"source":126,"target":132,"sourceHandle":184,"targetHandle":176,"type":177},"conn_if_compare_true",{"id":199,"source":126,"target":138,"sourceHandle":187,"targetHandle":176,"type":177},"conn_if_compare_false",{"id":201,"source":138,"target":144,"sourceHandle":184,"targetHandle":176,"type":177},"conn_if_culture_true",{"id":203,"source":138,"target":150,"sourceHandle":187,"targetHandle":176,"type":177},"conn_if_culture_false",{"id":205,"source":150,"target":156,"sourceHandle":184,"targetHandle":176,"type":177},"conn_if_handoff_true",{"id":207,"source":150,"target":166,"sourceHandle":187,"targetHandle":176,"type":177},"conn_if_handoff_false","automation",[28,29,30,210,211,212],"attribution","analytics-hygiene","leadership-ops",[214],"WhatsApp","intermediate","Calypso","2026-04-02T11:03:39.805Z","/en/workflows/branch-signals-trust-checks-before-you-decide",{"en":218},{"title":9,"description":221,"ogDescription":222,"twitterDescription":223,"canonicalPath":218,"robots":224,"schemaType":225,"alternates":226},"Guide teams to trust the right branch metrics, spot dirty signals early, and choose when to rely on automation vs judgment.","A practical decision coach for branch metrics and attribution: trust tests, dirty signal flags, automation vs judgment, and clean next steps.","Stop confident wrong decisions. Run quick trust checks on branch numbers, spot dirty signals, and know when automation is safe vs when humans must decide.","index,follow","HowTo",[227],{"hreflang":6,"href":218},1775310170319]