[{"data":1,"prerenderedAt":253},["ShallowReactive",2],{"/en/workflows/branch-data-trust-coach":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":232,"tags":233,"integrations":237,"difficulty":240,"author":241,"verified":32,"featured":32,"date":242,"modified":242,"icon":7,"imageSrc":7,"path":243,"alternates":244,"seo":245},"3c1d4cc7-455a-4b53-81b5-8f9a9fd0863b","branch-data-trust-coach","en",null,true,"Branch Data Trust Coach","A guided decision helper that turns messy branch metrics and conversations into safer, decision-ready next steps—without over-cleaning away the truth.","## How it works\nThis workflow acts like a practical “numbers bouncer” for branch decisions. It starts by letting the Knowledge Base answer direct questions (when you already have documented standards), then guides the operator through a menu of decision-shaped checks: which branch numbers deserve trust, how to spot dirty signals, when automation is safe, how to compare branches without fooling yourself, and how to build a culture where signals lead to decisions—not decks.\n\nWhen the operator needs a human read (usually because the data looks neat but smells off), the workflow offers a clean escalation path to an Analytics Support handoff. Otherwise, it closes with a short “do this next” checklist so the team leaves with action—not vibes.\n\n## Key features\n- Knowledge Base-first behavior to answer documented signal standards before routing\n- Button-based menu for fast triage (no long forms, no academic detours)\n- Practical guidance paths focused on decision risk: trust, dirtiness, automation vs judgment, comparisons, attribution, culture\n- Built-in “Next steps” chooser to either loop back, close, or escalate\n- Routed handoff to Analytics Support when confidence is high but evidence is shaky\n\n## Step-by-step\n1. **Input trigger** starts the workflow when a user enters the flow.\n2. **Knowledge Base Policy** attempts to answer from your Calypso Knowledge Base (and continues to routing when it can’t).\n3. **Choose a decision check** via an interactive button menu (e.g., “Which branch numbers can I trust?”).\n4. **Route by selection** using IF nodes that match the selected button id.\n5. **Deliver the relevant guidance** as a concise text message (tailored to the chosen risk pattern).\n6. **Pick next steps** from a second button menu: escalate to Analytics Support, go back to the main menu, or close.\n7. **Escalate or close**:\n   - If escalation is chosen, the workflow hands off to **Analytics Support**.\n   - If close is chosen, the workflow sends a final “safe next move” message.\n   - If back is chosen, it returns to the main menu.\n\n## Setup requirements\n- **Calypso Knowledge Base** (optional but recommended): add/maintain articles for metric definitions, branch reporting rules, attribution standards, and known data pitfalls.\n- **Calypso Inbox routing**: ensure the **Analytics Support** department exists (or update the department id/name in the fallback node).\n- No additional credentials are required beyond Calypso access.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":188,"routingEnabled":8,"active":32},"wf-branch-data-trust-coach","calypso-public-library","1.0.0",1,[18,33,39,51,79,88,94,100,106,112,120,126,132,138,144,159,166,171,182],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":24,"category":31,"deletable":32,"connectable":32},"node-flow-configs","Flow settings","flow-configs",[23,23],80,{"name":9,"description":25,"tags":26,"triggerType":30},"Turn messy branch signals into safer decisions with KB-first answers, guided triage, and optional escalation.",[27,28,29],"branch-metrics","signal-quality","decision-making","input","policy",false,{"id":34,"name":35,"type":30,"typeVersion":16,"position":36,"parameters":38,"category":30,"deletable":32,"connectable":8},"node-input","Input",[37,37],220,{},{"id":40,"name":41,"type":42,"typeVersion":16,"position":43,"parameters":45,"category":50,"deletable":8,"connectable":8},"node-kb-policy","Knowledge Base: Signal standards","knowledge-base-policy",[44,37],440,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":46,"activationOpener":47,"personalization":49},"default",{"enabled":8,"instruction":48},"Answer using the Knowledge Base when the user asks about metric definitions, reporting rules, attribution standards, or known data pitfalls. If the question is ambiguous or the KB doesn’t cover it, continue to the decision menu and guide the user to a safe next step.",{"useContactName":8},"response",{"id":52,"name":53,"type":54,"typeVersion":16,"position":55,"parameters":57,"category":50,"deletable":8,"connectable":8},"node-main-menu","Decision menu","interactive-message",[56,37],660,{"messageType":58,"headerText":59,"bodyText":60,"footerText":61,"sectionTitle":62,"buttons":63,"ctaDisplayText":62,"ctaUrl":62},"button","Make signals decision-ready","Pick what you’re trying to decide. If the data looks *too* clean, you’re probably one meeting away from a confident mistake.","Choose one:","",[64,67,70,73,76],{"id":65,"title":66},"trust-numbers","Trust numbers",{"id":68,"title":69},"dirty-signal","Dirty signal",{"id":71,"title":72},"automation-vs-judgment","Auto vs human",{"id":74,"title":75},"compare-branches","Compare branches",{"id":77,"title":78},"signal-culture","Signal culture",{"id":80,"name":81,"type":82,"typeVersion":16,"position":83,"parameters":85,"category":87,"deletable":8,"connectable":8},"node-if-trust","IF: trust numbers","if",[84,23],900,{"buttonId":65,"operator":86},"equals","routing",{"id":89,"name":90,"type":82,"typeVersion":16,"position":91,"parameters":93,"category":87,"deletable":8,"connectable":8},"node-if-dirty","IF: dirty signal",[84,92],160,{"buttonId":68,"operator":86},{"id":95,"name":96,"type":82,"typeVersion":16,"position":97,"parameters":99,"category":87,"deletable":8,"connectable":8},"node-if-auto","IF: automation vs judgment",[84,98],240,{"buttonId":71,"operator":86},{"id":101,"name":102,"type":82,"typeVersion":16,"position":103,"parameters":105,"category":87,"deletable":8,"connectable":8},"node-if-compare","IF: compare branches",[84,104],320,{"buttonId":74,"operator":86},{"id":107,"name":108,"type":82,"typeVersion":16,"position":109,"parameters":111,"category":87,"deletable":8,"connectable":8},"node-if-culture","IF: signal culture",[84,110],400,{"buttonId":77,"operator":86},{"id":113,"name":114,"type":115,"typeVersion":16,"position":116,"parameters":118,"category":50,"deletable":8,"connectable":8},"node-msg-trust","Guidance: which numbers to trust","text-message",[117,23],1140,{"text":119},"Branch numbers you can usually trust are the ones that are:\n\n1) **Defined like a contract** (everyone agrees what counts, what doesn’t, and when it’s recorded).\n2) **Hard to “touch up” locally** (captured automatically, not retyped, not self-reported).\n3) **Stable under harmless changes** (a dashboard color change shouldn’t move revenue).\n\nPolished noise usually looks like:\n- Perfectly smooth trends with no operational reason.\n- Sudden step-changes right after targets/bonuses changed.\n- Metrics that improve while customer complaints, refunds, or backlog quietly worsen.\n\nPractical move: pick **one anchor metric** (hard to game) and treat everything else as supporting cast until it agrees with the anchor.",{"id":121,"name":122,"type":115,"typeVersion":16,"position":123,"parameters":124,"category":50,"deletable":8,"connectable":8},"node-msg-dirty","Guidance: spot dirty signal",[117,92],{"text":125},"Dirty signal doesn’t announce itself. It shows up as *credible-looking numbers that break in the meeting.* Watch for:\n\n- **Timestamp weirdness**: activity recorded in batches, at day-end, or mysteriously “always at 9:00am.”\n- **Definition drift**: same metric name, different counting rules across branches.\n- **Missingness that isn’t random**: the worst days are the days with “no data.” Convenient.\n- **Channel spillover**: calls become chats, chats become walk-ins—volume shifts but demand didn’t.\n\nQuick test before the meeting: ask “**What would have to be true operationally for this spike to be real?**” If nobody can describe the real-world mechanism, you’re looking at a reporting artifact until proven otherwise.",{"id":127,"name":128,"type":115,"typeVersion":16,"position":129,"parameters":130,"category":50,"deletable":8,"connectable":8},"node-msg-auto","Guidance: automation vs judgment",[117,98],{"text":131},"Trust automation when the decision is:\n- **Repeatable** (same inputs, same logic, every time)\n- **Low-regret** (a wrong call is recoverable)\n- **Well-instrumented** (you can tell when it’s failing)\n\nKeep human judgment in the loop when:\n- The metric can be gamed, reclassified, or “massaged.”\n- The action is **irreversible** (staffing cuts, branch closures, policy changes).\n- You’re comparing apples to “apples, but with a different peel.” (Different mix, different customer base, different process.)\n\nRule of thumb: **Automate the checklist, not the verdict.** Let automation surface anomalies and enforce definitions; let humans decide when context beats the model.",{"id":133,"name":134,"type":115,"typeVersion":16,"position":135,"parameters":136,"category":50,"deletable":8,"connectable":8},"node-msg-compare","Guidance: compare branches & attribution",[117,104],{"text":137},"Branch comparisons go wrong for predictable reasons:\n\n- **Mix shift**: one branch serves harder cases; “average time” is a trap.\n- **Different clocks**: one branch logs on creation, another on completion.\n- **Attribution fog**: the branch that closes gets credit; the branch that did the work gets blamed.\n\nSafer comparisons:\n1) Compare on **like-for-like slices** (same product, same customer segment, same channel).\n2) Track **leading indicators** (backlog age, rework rate) alongside outcomes.\n3) Use a **paired metric**: every ‘win’ should have a corresponding ‘cost’ metric watching for hidden damage.\n\nIf a branch “improves” on everything at once, don’t applaud yet—verify definitions first.",{"id":139,"name":140,"type":115,"typeVersion":16,"position":141,"parameters":142,"category":50,"deletable":8,"connectable":8},"node-msg-culture","Guidance: build a signal culture",[117,110],{"text":143},"A healthy signal culture isn’t more dashboards. It’s fewer debates that start with “whose numbers are right?”\n\nWhat works:\n- **One source of truth per metric** (owner, definition, refresh cadence).\n- **A ‘definition change’ log** (so trend breaks don’t become folklore).\n- **Red-team questions** as a norm: “What would make this false?”\n- **Decision memos over slide theater**: what we saw, what we did, what we’ll watch next.\n\nWitty-but-true: the first thing that usually fails isn’t the data pipeline—it’s the team’s ability to admit uncertainty *before* committing to a confident plan.",{"id":145,"name":146,"type":54,"typeVersion":16,"position":147,"parameters":149,"category":50,"deletable":8,"connectable":8},"node-next-steps","Next steps",[148,98],1380,{"messageType":58,"headerText":150,"bodyText":151,"footerText":62,"sectionTitle":62,"buttons":152,"ctaDisplayText":62,"ctaUrl":62},"What next?","If the numbers look clean but your instincts say “off,” that’s a valid signal too. Choose the safest next move.",[153,156],{"id":154,"title":155},"escalate-analytics","Escalate to analyst",{"id":157,"title":158},"close","Done",{"id":160,"name":161,"type":82,"typeVersion":16,"position":162,"parameters":165,"category":87,"deletable":8,"connectable":8},"node-if-escalate","IF: escalate",[163,164],1620,200,{"buttonId":154,"operator":86},{"id":167,"name":168,"type":82,"typeVersion":16,"position":169,"parameters":170,"category":87,"deletable":8,"connectable":8},"node-if-close","IF: close",[163,104],{"buttonId":157,"operator":86},{"id":172,"name":173,"type":174,"typeVersion":16,"position":175,"parameters":177,"category":181,"deletable":8,"connectable":8},"node-handoff","Handoff: Analytics Support","fallback",[176,164],1860,{"handoffMessage":178,"departmentId":179,"departmentName":180},"I’m handing this to Analytics Support. To speed things up, share: (1) branch(es), (2) metric(s), (3) time window, (4) what decision is being made, and (5) what feels ‘off’ about the signal.","analytics-support","Analytics Support","terminal",{"id":183,"name":184,"type":115,"typeVersion":16,"position":185,"parameters":186,"category":50,"deletable":8,"connectable":8},"node-close-msg","Close message",[176,104],{"text":187},"Good stop point. If you do one thing before acting: write down (a) the decision, (b) the one anchor metric you trust most, and (c) the fastest way you’d detect you’re wrong. That last part is how grown-up decisions stay grown-up.",[189,192,194,196,198,200,202,204,206,208,210,212,214,216,218,220,222,224,226,228,230],{"id":190,"source":34,"target":40,"sourceHandle":62,"targetHandle":62,"type":191},"con-input-to-kb","main",{"id":193,"source":40,"target":52,"sourceHandle":62,"targetHandle":62,"type":191},"con-kb-to-menu",{"id":195,"source":52,"target":80,"sourceHandle":62,"targetHandle":62,"type":191},"con-menu-to-if-trust",{"id":197,"source":52,"target":89,"sourceHandle":62,"targetHandle":62,"type":191},"con-menu-to-if-dirty",{"id":199,"source":52,"target":95,"sourceHandle":62,"targetHandle":62,"type":191},"con-menu-to-if-auto",{"id":201,"source":52,"target":101,"sourceHandle":62,"targetHandle":62,"type":191},"con-menu-to-if-compare",{"id":203,"source":52,"target":107,"sourceHandle":62,"targetHandle":62,"type":191},"con-menu-to-if-culture",{"id":205,"source":80,"target":113,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-trust-to-msg",{"id":207,"source":89,"target":121,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-dirty-to-msg",{"id":209,"source":95,"target":127,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-auto-to-msg",{"id":211,"source":101,"target":133,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-compare-to-msg",{"id":213,"source":107,"target":139,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-culture-to-msg",{"id":215,"source":113,"target":145,"sourceHandle":62,"targetHandle":62,"type":191},"con-msg-trust-to-next",{"id":217,"source":121,"target":145,"sourceHandle":62,"targetHandle":62,"type":191},"con-msg-dirty-to-next",{"id":219,"source":127,"target":145,"sourceHandle":62,"targetHandle":62,"type":191},"con-msg-auto-to-next",{"id":221,"source":133,"target":145,"sourceHandle":62,"targetHandle":62,"type":191},"con-msg-compare-to-next",{"id":223,"source":139,"target":145,"sourceHandle":62,"targetHandle":62,"type":191},"con-msg-culture-to-next",{"id":225,"source":145,"target":160,"sourceHandle":62,"targetHandle":62,"type":191},"con-next-to-if-escalate",{"id":227,"source":145,"target":167,"sourceHandle":62,"targetHandle":62,"type":191},"con-next-to-if-close",{"id":229,"source":160,"target":172,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-escalate-to-handoff",{"id":231,"source":167,"target":183,"sourceHandle":62,"targetHandle":62,"type":191},"con-if-close-to-close-msg","automation",[27,28,29,234,235,236],"data-trust","attribution","ops-analytics",[238,239],"Calypso Knowledge Base","Calypso Inbox","intermediate","Calypso","2026-06-13T11:04:21.686Z","/en/workflows/branch-data-trust-coach",{"en":243},{"title":9,"description":246,"ogDescription":247,"twitterDescription":248,"canonicalPath":243,"robots":249,"schemaType":250,"alternates":251},"Guide teams to trust the right branch signals, spot dirty data early, and choose when to automate or escalate to analysts.","A decision ready triage for branch metrics: detect polished noise, compare branches safely, and know when automation needs human judgment.","Stop confident wrong decisions. Triage branch signals, spot dirty data, compare branches safely, and escalate when the numbers look too neat.","index,follow","HowTo",[252],{"hreflang":6,"href":243},1785947669171]