[{"data":1,"prerenderedAt":229},["ShallowReactive",2],{"/en/workflows/reality-tests-for-branch-numbers-attribution":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":209,"tags":210,"integrations":213,"difficulty":216,"author":217,"verified":34,"featured":34,"date":218,"modified":218,"icon":7,"imageSrc":7,"path":219,"alternates":220,"seo":221},"82942a44-8543-4901-af3e-554c1dc0ac8e","reality-tests-for-branch-numbers-attribution","en",null,true,"Reality Tests for Branch Numbers & Attribution","A decision-ready coaching flow that helps teams spot polished noise, detect dirty signals, and choose when to trust automation versus human judgment—before the meeting goes confidently wrong.","## How it works\nThis workflow turns messy branch numbers, conversation notes, and attribution claims into practical “can we trust this?” decisions. It starts with a knowledge-guided coaching layer (so answers stay consistent), then routes people into short, decision-shaped playbooks—designed for the moment right before a confident meeting goes off the rails.\n\nInstead of asking teams to “improve data quality,” it helps them pressure-test the specific signals they’re about to act on: which numbers are sturdy, which are suspiciously smooth, when automation earns trust, and where humans must stay in the loop.\n\n## Key features\n- Knowledge-guided responses first, then a menu of decision-focused playbooks.\n- Interactive list routing for fast self-serve triage (branch numbers, dirty signals, automation vs judgment, comparisons, culture).\n- Each path ends in a practical checklist you can use immediately in a meeting.\n- A built-in escalation path to a human (handoff) when the situation is political, ambiguous, or high-stakes.\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow.\n2. **Knowledge-guided coaching:** The workflow applies a knowledge-base policy to keep advice consistent and grounded.\n3. **Pick the decision you’re making:** The user chooses from an interactive menu:\n   - Trust these branch numbers?\n   - Spot dirty signal before the meeting\n   - Automation vs human judgment\n   - Comparing branches & attribution\n   - Build a signal culture (less slides, more decisions)\n   - Talk to a human\n4. **Routing:** The workflow matches the user’s choice and delivers the relevant checklist.\n5. **Escalation:** If the user asks for a human (or nothing matches), the workflow hands off to a designated team.\n\n## Setup requirements\n- No credentials required.\n- A Calypso channel that supports interactive messages (e.g., WhatsApp) and a team ready to receive handoffs (configured as the destination department in Calypso).",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":174,"routingEnabled":8,"active":34},"wf_reality_tests_branch_attribution_v1","calypso-public-library","1.0.0",1,[18,35,41,53,85,95,103,108,114,120,126,132,138,144,150,156,167],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":33,"deletable":8,"connectable":34},"node_flowcfg","Workflow settings","flow-configs",[23,24],80,60,{"name":9,"description":26,"tags":27,"triggerType":32},"Decision-ready coaching for branch metrics, dirty signals, automation vs judgment, and attribution comparisons.",[28,29,30,31],"signal-quality","branch-metrics","attribution","decision-systems","input","policy",false,{"id":36,"name":37,"type":32,"typeVersion":16,"position":38,"parameters":40,"category":32,"deletable":34,"connectable":8},"node_input","Start",[23,39],220,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb","Signal coaching policy","knowledge-base-policy",[46,39],280,{"enabled":8,"fallbackToRouting":8,"sticky":34,"stickyMode":48,"activationOpener":49,"personalization":51},"default",{"enabled":8,"instruction":50},"Coach the user in plain, practical language. Be skeptical of polished numbers. Offer checklists and decision tests. Use light wit, not jargon.",{"useContactName":8},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"node_menu","Choose a decision check","interactive-message",[58,39],500,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":84,"ctaUrl":84},"list","Decision signal coach","Pick what you’re about to decide. I’ll help you separate sturdy signals from polished noise—before the meeting gets emotionally attached to the wrong number.","Tip: Start with Branch numbers.","Decision checks",[66,69,72,75,78,81],{"id":67,"title":68},"trust_branch_numbers","Trust branch numbers",{"id":70,"title":71},"spot_dirty_signal","Spot dirty signal",{"id":73,"title":74},"automation_vs_judgment","Automation vs judgment",{"id":76,"title":77},"compare_branches_attribution","Branch & attribution",{"id":79,"title":80},"build_signal_culture","Build signal culture",{"id":82,"title":83},"talk_to_human","Talk to a human","",{"id":86,"name":87,"type":88,"typeVersion":16,"position":89,"parameters":92,"category":94,"deletable":8,"connectable":8},"node_if_trust","If: trust branch numbers","if",[90,91],720,120,{"buttonId":67,"operator":93},"equals","routing",{"id":96,"name":97,"type":98,"typeVersion":16,"position":99,"parameters":101,"category":52,"deletable":8,"connectable":34},"node_msg_trust","Checklist: numbers you can trust","text-message",[100,91],940,{"text":102},"Here’s how to tell *decision-grade* branch numbers from polished noise:\n\n1) **Start with the “boring but stable” metrics** (usually trustworthy)\n- Completed transactions / fulfilled services (not “started”).\n- Cash collected / settled revenue (not “expected”).\n- Inventory movements with reconciliation (not “stock on hand” alone).\n\n2) **Be suspicious of metrics that look smooth** (often misleading)\n- Anything that can be “fixed” by changing a dropdown or a definition.\n- Ratios without counts (conversion rate with tiny volume).\n- Metrics that improved *exactly* after a target was announced.\n\n3) **Trust increases when…**\n- The number ties to a ledger, settlement, or audit trail.\n- You can explain a spike with a real-world event *and* see it in multiple signals.\n- The metric stays directionally similar across two independent sources.\n\n4) **Trust collapses when…**\n- Backfills happen quietly (“we corrected last month”).\n- One branch has a “different process” (translation: different data).\n- The number depends on manual tagging or optional fields.\n\nIf you tell me: *metric + time window + how it’s captured*, I’ll suggest the fastest trust test.",{"id":104,"name":105,"type":88,"typeVersion":16,"position":106,"parameters":107,"category":94,"deletable":8,"connectable":8},"node_if_dirty","If: spot dirty signal",[90,39],{"buttonId":70,"operator":93},{"id":109,"name":110,"type":98,"typeVersion":16,"position":111,"parameters":112,"category":52,"deletable":8,"connectable":34},"node_msg_dirty","Checklist: dirty signal detectors",[100,39],{"text":113},"Dirty signal usually looks *fine* until it’s used to win an argument. Quick detectors:\n\n**A. The “definition drift” test**\n- Ask: “What exactly counts?” If two people answer differently, the chart is already lying.\n\n**B. The “optional field” trap**\n- Any metric relying on free-text reasons, tags, or manual statuses will trend toward optimism.\n\n**C. The “late data” ambush**\n- Check freshness: What % of last week’s records arrive late or get edited?\n- If backfills are common, compare *finalized* weeks, not the latest day.\n\n**D. The “branch behavior changed” false win**\n- Did the team learn how to avoid being counted? (Common when metrics become targets.)\n\n**E. The “single-source hero” warning**\n- If one dashboard is the only witness, treat it as an allegation, not a fact.\n\nMeeting-safe move: present the number *with its failure mode* (“This is strong unless tagging is incomplete; tagging is 78% this week”). It prevents confident nonsense.",{"id":115,"name":116,"type":88,"typeVersion":16,"position":117,"parameters":119,"category":94,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[90,118],320,{"buttonId":73,"operator":93},{"id":121,"name":122,"type":98,"typeVersion":16,"position":123,"parameters":124,"category":52,"deletable":8,"connectable":34},"node_msg_auto","Guide: when to trust automation",[100,118],{"text":125},"Automation is great at consistency. It’s terrible at embarrassment.\n\n**Trust automation when:**\n- The decision is reversible (you can undo it cheaply).\n- The inputs are constrained (few ways to be wrong).\n- There’s a clear feedback loop (you’ll know within days if it failed).\n- Edge cases are rare and you’ve defined what “rare” means.\n\n**Keep humans in the loop when:**\n- The decision is high-cost, public, or political.\n- Branches have different workflows (automation will punish the “weird” branch).\n- You’re using proxies (sentiment, intent, attribution) as if they were facts.\n- The metric can be gamed once people learn the rule.\n\n**Practical hybrid:**\n- Automate *triage*, not *verdicts*: flag anomalies, require a short human reason to override.\n- Use “two-signal” rules: automation acts only when two independent indicators agree.\n\nIf you share the decision (“close branch hours?”, “reassign leads?”, “budget shift?”), I’ll suggest the safest automation boundary.",{"id":127,"name":128,"type":88,"typeVersion":16,"position":129,"parameters":131,"category":94,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[90,130],420,{"buttonId":76,"operator":93},{"id":133,"name":134,"type":98,"typeVersion":16,"position":135,"parameters":136,"category":52,"deletable":8,"connectable":34},"node_msg_compare","Checklist: comparisons that don’t lie",[100,130],{"text":137},"Branch comparisons fail for the same reasons, on repeat. Here’s the clean way to argue with numbers:\n\n**1) Normalize before you moralize**\n- Compare per: operating hour, staff hour, footfall, leads received, or catchment size.\n- Raw totals mostly measure “how busy” not “how good.”\n\n**2) Don’t compare different funnels**\n- If Branch A logs every walk-in and Branch B logs only qualified leads, conversion rates are theater.\n\n**3) Attribution: treat it as a map, not a judge**\n- Last-touch is easy and often wrong.\n- Self-reported source is useful and biased.\n- Platform-reported source is precise and incomplete.\n\n**4) Watch for timing tricks**\n- Marketing effects arrive with lag; operational changes can be immediate.\n- Compare consistent windows (e.g., week-over-week finalized weeks).\n\n**5) The fastest sanity check**\n- Ask: “What would we expect to move *with* this metric?” If nothing co-moves, it’s likely measurement, not reality.\n\nIf you tell me what you’re comparing (e.g., “Branch 3 vs Branch 7 on conversion”), I’ll list the top 3 confounders to eliminate first.",{"id":139,"name":140,"type":88,"typeVersion":16,"position":141,"parameters":143,"category":94,"deletable":8,"connectable":8},"node_if_culture","If: build signal culture",[90,142],520,{"buttonId":79,"operator":93},{"id":145,"name":146,"type":98,"typeVersion":16,"position":147,"parameters":148,"category":52,"deletable":8,"connectable":34},"node_msg_culture","Guide: culture that produces decisions",[100,142],{"text":149},"A healthy signal culture doesn’t produce better slides. It produces faster, calmer decisions.\n\n**Make these rules explicit:**\n1) **Every metric needs a failure mode.** If you can’t say how it lies, you will eventually believe it.\n2) **One page beats ten charts.** Require: decision, options, evidence, uncertainty, next check.\n3) **Separate “tracking” from “targets.”** The moment a metric becomes a goal, it becomes a game.\n4) **Keep a small list of “decision metrics.”** Too many KPIs is just hiding from judgment.\n5) **Reward truth-telling.** Celebrate the person who finds the data issue *before* launch, not after.\n\nLightweight ritual: once a month, run a 20-minute “Metric Postmortem”: which number misled us, why, and what guardrail we add.",{"id":151,"name":152,"type":88,"typeVersion":16,"position":153,"parameters":155,"category":94,"deletable":8,"connectable":8},"node_if_human","If: talk to a human",[90,154],620,{"buttonId":82,"operator":93},{"id":157,"name":158,"type":159,"typeVersion":16,"position":160,"parameters":162,"category":166,"deletable":8,"connectable":34},"node_handoff","Handoff to decision support","fallback",[100,161],660,{"handoffMessage":163,"departmentId":164,"departmentName":165},"Got it. I’m looping in a human for this—high-stakes, ambiguous, or political decisions deserve actual judgment. Share: the decision, the key numbers, and what would change your mind.","decision-support","Decision Support","terminal",{"id":168,"name":169,"type":159,"typeVersion":16,"position":170,"parameters":172,"category":166,"deletable":8,"connectable":34},"node_handoff_default","Default handoff (no match)",[100,171],760,{"handoffMessage":173,"departmentId":164,"departmentName":165},"I didn’t catch that choice. I’m routing you to a human so you don’t get stuck. Share the decision you’re making and the signals you’re using.",[175,179,181,183,186,189,191,193,195,197,199,201,203,205,207],{"id":176,"source":36,"target":42,"sourceHandle":177,"targetHandle":178,"type":48},"conn_input_kb","out","in",{"id":180,"source":42,"target":54,"sourceHandle":177,"targetHandle":178,"type":48},"conn_kb_menu",{"id":182,"source":54,"target":86,"sourceHandle":177,"targetHandle":178,"type":48},"conn_menu_if1",{"id":184,"source":86,"target":96,"sourceHandle":185,"targetHandle":178,"type":48},"conn_if1_true_msg","true",{"id":187,"source":86,"target":104,"sourceHandle":188,"targetHandle":178,"type":48},"conn_if1_false_if2","false",{"id":190,"source":104,"target":109,"sourceHandle":185,"targetHandle":178,"type":48},"conn_if2_true_msg",{"id":192,"source":104,"target":115,"sourceHandle":188,"targetHandle":178,"type":48},"conn_if2_false_if3",{"id":194,"source":115,"target":121,"sourceHandle":185,"targetHandle":178,"type":48},"conn_if3_true_msg",{"id":196,"source":115,"target":127,"sourceHandle":188,"targetHandle":178,"type":48},"conn_if3_false_if4",{"id":198,"source":127,"target":133,"sourceHandle":185,"targetHandle":178,"type":48},"conn_if4_true_msg",{"id":200,"source":127,"target":139,"sourceHandle":188,"targetHandle":178,"type":48},"conn_if4_false_if5",{"id":202,"source":139,"target":145,"sourceHandle":185,"targetHandle":178,"type":48},"conn_if5_true_msg",{"id":204,"source":139,"target":151,"sourceHandle":188,"targetHandle":178,"type":48},"conn_if5_false_if6",{"id":206,"source":151,"target":157,"sourceHandle":185,"targetHandle":178,"type":48},"conn_if6_true_handoff",{"id":208,"source":151,"target":168,"sourceHandle":188,"targetHandle":178,"type":48},"conn_if6_false_default_handoff","automation",[28,29,30,31,211,212],"data-hygiene","automation-judgment",[214,215],"WhatsApp","Calypso Inbox","intermediate","Calypso","2026-03-31T11:04:40.907Z","/en/workflows/reality-tests-for-branch-numbers-attribution",{"en":219},{"title":9,"description":222,"ogDescription":223,"twitterDescription":224,"canonicalPath":219,"robots":225,"schemaType":226,"alternates":227},"Route teams to quick signal checks: trust branch metrics, spot dirty data, judge automation vs humans, and avoid confident wrong decisions.","A practical coaching workflow: pressure test branch numbers, catch dirty signals, decide when to trust automation, and compare attribution without fooling yourself.","Turn messy branch signals into decision ready checks. Spot polished noise, choose automation vs judgment, and avoid the confident wrong meeting.","index,follow","HowTo",[228],{"hreflang":6,"href":219},1775310170502]