[{"data":1,"prerenderedAt":281},["ShallowReactive",2],{"/en/workflows/branch-numbers-reality-check-coach":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":261,"tags":262,"integrations":265,"difficulty":268,"author":269,"verified":34,"featured":34,"date":270,"modified":270,"icon":7,"imageSrc":7,"path":271,"alternates":272,"seo":273},"f0ab26d4-963e-47a3-871c-299dd41ab8a5","branch-numbers-reality-check-coach","en",null,true,"Branch Numbers Reality Check Coach","An interactive decision assistant that helps leaders pressure-test branch metrics, spot dirty signals early, and decide when automation is safe vs when human judgment must step in.","## How it works\nThis workflow is a fast, leader-friendly checkpoint you can run anytime a team is about to make a confident decision from branch numbers, conversation notes, or attribution reports. It uses your Knowledge Base first, then guides the user through a handful of decision-shaped prompts to separate trustworthy signals from polished noise.\n\nIt’s designed for the real world where bad data looks perfectly reasonable—right up until it wins an argument in a meeting. Users pick the situation they’re in (trusting a metric, spotting dirty signal, comparing branches, etc.), get a practical reality check, and can loop for another check or hand off to a human.\n\n## Key features\n- Knowledge Base–first answers, with routing to decision prompts when the question is messy or ambiguous\n- A single menu of “decision moments” (trust, dirty signal, automation vs judgment, comparisons, culture)\n- Practical red-flag guidance that focuses on what breaks first (definitions, lag, selection bias, incentives)\n- Quick loop-back to run multiple checks without restarting the conversation\n- Optional human handoff via routing when the user needs an analyst/operator to review context\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a user opens the flow.\n2. **Knowledge Base policy:** The assistant first attempts to answer using your Knowledge Base and stays grounded in your internal definitions.\n3. **Decision menu:** If routing is needed, the user sees a menu:\n   - Which branch numbers deserve trust?\n   - How to spot dirty signal before a meeting?\n   - When to trust automation vs human judgment?\n   - Comparing branches & attribution without fooling yourself\n   - Build a signal culture (decisions, not decks)\n   - Talk to a human\n4. **Targeted guidance:** Based on the selected option, the workflow sends a focused set of checks and “what to do next” suggestions.\n5. **Next step choice:** The user can either **run another check** (returns to the main menu) or **hand off to a human** (routes to a department).\n\n## Setup requirements\n- **Calypso Knowledge Base:** Recommended so the assistant can use your official metric definitions, branch taxonomy, and reporting rules.\n- **Routing/Departments in Calypso:** Create or select a department (e.g., “Analytics Ops”) for optional handoff.\n- No additional credentials are required for this workflow.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":205,"routingEnabled":8,"active":34},"wf_branch_numbers_reality_check_coach","calypso-public-library","1.0.0",1,[18,35,41,53,84,94,100,106,112,118,124,132,138,144,150,156,169,176,181,188,194],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":33,"deletable":34,"connectable":34},"cfg_001","Flow settings","flow-configs",[23,24],80,60,{"name":9,"description":26,"tags":27,"triggerType":32},"KB-first decision prompts to pressure-test branch metrics, detect dirty signal early, and choose when automation vs human judgment should lead.",[28,29,30,31],"signal-design","decision-systems","branch-metrics","data-quality","input","policy",false,{"id":36,"name":37,"type":32,"typeVersion":16,"position":38,"parameters":40,"category":32,"deletable":34,"connectable":8},"in_001","Start",[23,39],180,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"kbp_001","Knowledge Base first","knowledge-base-policy",[46,39],320,{"enabled":8,"fallbackToRouting":8,"sticky":34,"stickyMode":48,"activationOpener":49,"personalization":51},"default",{"enabled":8,"instruction":50},"Use the Knowledge Base definitions and operating rules first. If the user is heading toward a decision based on branch numbers or attribution, route them into the decision menu to run a quick reality check. Keep it practical: what to trust, what breaks first, and what to verify before acting.",{"useContactName":8},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"im_001","Decision menu","interactive-message",[58,39],560,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":64,"ctaUrl":64},"button","Decision Reality Check","Pick the situation you’re in. We’ll pressure-test the signal before it wins an argument in a meeting.","Fast checks beat confident regrets.","",[66,69,72,75,78,81],{"id":67,"title":68},"btn_trust_numbers","Trust branch nums",{"id":70,"title":71},"btn_dirty_signal","Spot dirty signal",{"id":73,"title":74},"btn_automation_vs_judgment","Auto vs judgment",{"id":76,"title":77},"btn_compare_branches","Compare branches",{"id":79,"title":80},"btn_signal_culture","Signal culture",{"id":82,"title":83},"btn_handoff","Talk to a human",{"id":85,"name":86,"type":87,"typeVersion":16,"position":88,"parameters":91,"category":93,"deletable":8,"connectable":8},"if_001","If: trust numbers","if",[89,90],800,120,{"buttonId":67,"operator":92},"equals","routing",{"id":95,"name":96,"type":87,"typeVersion":16,"position":97,"parameters":99,"category":93,"deletable":8,"connectable":8},"if_002","If: dirty signal",[89,98],200,{"buttonId":70,"operator":92},{"id":101,"name":102,"type":87,"typeVersion":16,"position":103,"parameters":105,"category":93,"deletable":8,"connectable":8},"if_003","If: automation vs judgment",[89,104],280,{"buttonId":73,"operator":92},{"id":107,"name":108,"type":87,"typeVersion":16,"position":109,"parameters":111,"category":93,"deletable":8,"connectable":8},"if_004","If: compare branches",[89,110],360,{"buttonId":76,"operator":92},{"id":113,"name":114,"type":87,"typeVersion":16,"position":115,"parameters":117,"category":93,"deletable":8,"connectable":8},"if_005","If: signal culture",[89,116],440,{"buttonId":79,"operator":92},{"id":119,"name":120,"type":87,"typeVersion":16,"position":121,"parameters":123,"category":93,"deletable":8,"connectable":8},"if_006","If: handoff",[89,122],520,{"buttonId":82,"operator":92},{"id":125,"name":126,"type":127,"typeVersion":16,"position":128,"parameters":130,"category":52,"deletable":8,"connectable":8},"tm_001","Guidance: trustworthy numbers","text-message",[129,90],1040,{"text":131},"Branch numbers deserve trust when they behave like *instruments*, not *scoreboards*.\n\nQuick trust checks:\n1) **Definition is stable:** Same numerator/denominator across branches and time. If the definition changed, you’re comparing different animals.\n2) **Collection is hard to game:** If staff can improve the metric by changing how they log, you’re measuring incentives.\n3) **Lag is understood:** If the metric reacts after the decision window, it’s a rear-view mirror.\n4) **Coverage is known:** Ask: “Who is missing?” A perfect chart with selective coverage is still fiction.\n5) **Reconciliation exists:** There’s a second source that should roughly agree (even if imperfect).\n\nIf a number looks *too clean*, don’t celebrate—ask what got excluded to make it look that way.",{"id":133,"name":134,"type":127,"typeVersion":16,"position":135,"parameters":136,"category":52,"deletable":8,"connectable":8},"tm_002","Guidance: dirty signal",[129,98],{"text":137},"Dirty signal rarely announces itself. It usually shows up as confidence without friction.\n\nBefore the meeting goes off the rails, run these red-flag checks:\n- **One branch is ‘special’:** A top/bottom branch often has a process difference, not a performance difference.\n- **Spiky changes near deadlines:** Sudden improvements around month-end are frequently logging behavior.\n- **Perfect alignment with incentives:** If bonuses track the metric tightly, expect “creative compliance.”\n- **Conversation notes that read like marketing:** Over-polished summaries often mean the messy parts were dropped.\n- **Attribution that explains everything:** If every channel gets full credit, your model is doing vibes.\n\nMeeting move: ask, “What would we expect to see if this were *wrong*?” Then look for that evidence on purpose.",{"id":139,"name":140,"type":127,"typeVersion":16,"position":141,"parameters":142,"category":52,"deletable":8,"connectable":8},"tm_003","Guidance: automation vs judgment",[129,104],{"text":143},"Trust automation when the world is repeatable. Demand judgment when it’s not.\n\nGood candidates for automation:\n- Clear rules, low ambiguity (e.g., threshold alerts with known lag)\n- Stable definitions and instrumentation\n- High volume, low downside per decision\n\nRequire human review when:\n- **Definitions are disputed** (“What counts as a lead?”)\n- **Branch context matters** (staffing changes, outages, local campaigns)\n- **Downside is asymmetric** (a wrong closure/reorg costs more than a missed optimization)\n- **The metric can be gamed** (automation will scale the gaming too)\n\nPractical rule: automate the *detection* and *triage*; keep humans for the *exceptions* and the *stakes*.",{"id":145,"name":146,"type":127,"typeVersion":16,"position":147,"parameters":148,"category":52,"deletable":8,"connectable":8},"tm_004","Guidance: compare branches",[129,110],{"text":149},"Branch comparisons fail for boring reasons—mostly hidden mismatches.\n\nBefore you rank branches, confirm:\n1) **Comparable populations:** Footfall, customer mix, hours, and capacity. Normalize where it matters.\n2) **Same opportunity set:** A branch can’t convert what it never receives.\n3) **Channel overlap:** Attribution often double-counts influence. Treat it as *directional*, not court evidence.\n4) **Time alignment:** Promotions, staffing shifts, and seasonality can make last month vs this month a trap.\n5) **Process differences:** One branch may log better, not perform better.\n\nDecision tip: compare *within bands* (similar size/market), and look for consistent gaps across multiple signals—not one heroic metric.",{"id":151,"name":152,"type":127,"typeVersion":16,"position":153,"parameters":154,"category":52,"deletable":8,"connectable":8},"tm_005","Guidance: signal culture",[129,116],{"text":155},"A healthy signal culture makes decisions easier—not prettier.\n\nLightweight habits that work:\n- **One-page metric contracts:** definition, owner, known biases, and when *not* to use it.\n- **Pre-mortems for big calls:** “If this decision is wrong, why?” Then check those failure modes.\n- **Decision logs:** what you believed, what you did, and what you’ll watch. It cures amnesia.\n- **Reward truth over tidiness:** Teams should be safe to surface messy reality early.\n- **Two-signal rule:** no major branch decision from a single metric, especially if it’s easy to game.\n\nRemember: slides don’t make decisions—tradeoffs do. Signals should clarify tradeoffs, not hide them.",{"id":157,"name":158,"type":56,"typeVersion":16,"position":159,"parameters":161,"category":52,"deletable":8,"connectable":8},"im_002","Next step",[160,104],1280,{"messageType":60,"headerText":162,"bodyText":163,"footerText":64,"sectionTitle":64,"buttons":164,"ctaDisplayText":64,"ctaUrl":64},"What do you want to do next?","Restart to run a different check, or hand this to a human to review context.",[165,168],{"id":166,"title":167},"btn_restart","Restart flow",{"id":82,"title":83},{"id":170,"name":171,"type":87,"typeVersion":16,"position":172,"parameters":175,"category":93,"deletable":8,"connectable":8},"if_007","If: restart",[173,174],1520,240,{"buttonId":166,"operator":92},{"id":177,"name":178,"type":87,"typeVersion":16,"position":179,"parameters":180,"category":93,"deletable":8,"connectable":8},"if_008","If: handoff (next)",[173,46],{"buttonId":82,"operator":92},{"id":182,"name":183,"type":127,"typeVersion":16,"position":184,"parameters":186,"category":52,"deletable":8,"connectable":8},"tm_006","Restart instructions",[185,174],1760,{"text":187},"To run another check, restart this workflow from the beginning (open it again from your inbox/chat entry point). \n\nTip: when you restart, bring one concrete detail—**metric name**, **time window**, and the **decision you’re about to make**. That’s where polished noise likes to hide.",{"id":189,"name":190,"type":127,"typeVersion":16,"position":191,"parameters":192,"category":52,"deletable":8,"connectable":8},"tm_007","No selection help",[129,122],{"text":193},"I didn’t catch a menu selection. Please tap one of the buttons above to pick the situation you’re in—or choose **Talk to a human** if this needs context review.",{"id":195,"name":196,"type":197,"typeVersion":16,"position":198,"parameters":200,"category":204,"deletable":8,"connectable":8},"fb_001","Handoff to Analytics Ops","fallback",[185,199],420,{"handoffMessage":201,"departmentId":202,"departmentName":203},"Got it. I’m routing this to Analytics Ops so a human can review the context (definitions, branch differences, and what might be getting excluded). If you can, paste the metric name, time window, and the decision you’re about to make.","dept_analytics_ops","Analytics Ops","terminal",[206,211,213,215,218,220,222,224,226,229,231,233,235,237,239,241,243,245,247,249,251,253,255,257,259],{"id":207,"source":36,"target":42,"sourceHandle":208,"targetHandle":209,"type":210},"c_in_kbp","out","in","edge",{"id":212,"source":42,"target":54,"sourceHandle":208,"targetHandle":209,"type":210},"c_kbp_im1",{"id":214,"source":54,"target":85,"sourceHandle":208,"targetHandle":209,"type":210},"c_im1_if1",{"id":216,"source":85,"target":95,"sourceHandle":217,"targetHandle":209,"type":210},"c_if1_false_if2","false",{"id":219,"source":95,"target":101,"sourceHandle":217,"targetHandle":209,"type":210},"c_if2_false_if3",{"id":221,"source":101,"target":107,"sourceHandle":217,"targetHandle":209,"type":210},"c_if3_false_if4",{"id":223,"source":107,"target":113,"sourceHandle":217,"targetHandle":209,"type":210},"c_if4_false_if5",{"id":225,"source":113,"target":119,"sourceHandle":217,"targetHandle":209,"type":210},"c_if5_false_if6",{"id":227,"source":85,"target":125,"sourceHandle":228,"targetHandle":209,"type":210},"c_if1_true_tm1","true",{"id":230,"source":95,"target":133,"sourceHandle":228,"targetHandle":209,"type":210},"c_if2_true_tm2",{"id":232,"source":101,"target":139,"sourceHandle":228,"targetHandle":209,"type":210},"c_if3_true_tm3",{"id":234,"source":107,"target":145,"sourceHandle":228,"targetHandle":209,"type":210},"c_if4_true_tm4",{"id":236,"source":113,"target":151,"sourceHandle":228,"targetHandle":209,"type":210},"c_if5_true_tm5",{"id":238,"source":119,"target":195,"sourceHandle":228,"targetHandle":209,"type":210},"c_if6_true_fb1",{"id":240,"source":119,"target":189,"sourceHandle":217,"targetHandle":209,"type":210},"c_if6_false_tm7",{"id":242,"source":125,"target":157,"sourceHandle":208,"targetHandle":209,"type":210},"c_tm1_next",{"id":244,"source":133,"target":157,"sourceHandle":208,"targetHandle":209,"type":210},"c_tm2_next",{"id":246,"source":139,"target":157,"sourceHandle":208,"targetHandle":209,"type":210},"c_tm3_next",{"id":248,"source":145,"target":157,"sourceHandle":208,"targetHandle":209,"type":210},"c_tm4_next",{"id":250,"source":151,"target":157,"sourceHandle":208,"targetHandle":209,"type":210},"c_tm5_next",{"id":252,"source":157,"target":170,"sourceHandle":208,"targetHandle":209,"type":210},"c_im2_if7",{"id":254,"source":170,"target":177,"sourceHandle":217,"targetHandle":209,"type":210},"c_if7_false_if8",{"id":256,"source":170,"target":182,"sourceHandle":228,"targetHandle":209,"type":210},"c_if7_true_tm6",{"id":258,"source":177,"target":195,"sourceHandle":228,"targetHandle":209,"type":210},"c_if8_true_fb1",{"id":260,"source":177,"target":182,"sourceHandle":217,"targetHandle":209,"type":210},"c_if8_false_tm6","automation",[28,29,30,31,263,264],"governance","attribution",[266,267],"Calypso Knowledge Base","Calypso Messaging","intermediate","Calypso","2026-04-27T11:03:39.165Z","/en/workflows/branch-numbers-reality-check-coach",{"en":271},{"title":9,"description":274,"ogDescription":275,"twitterDescription":276,"canonicalPath":271,"robots":277,"schemaType":278,"alternates":279},"Pressure test branch metrics, catch dirty signals early, and choose when automation is safe vs when judgment must lead—via guided prompts.","A practical decision checkpoint for branch metrics: spot polished noise, detect dirty signal, and decide when automation is safe vs when people must review.","Turn messy branch signals into decision ready checks. Spot dirty data early, compare branches safely, and know when to trust automation vs judgment.","index,follow","HowTo",[280],{"hreflang":6,"href":271},1778614431277]