[{"data":1,"prerenderedAt":274},["ShallowReactive",2],{"/en/workflows/branch-signal-trust-decision-coach":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":255,"tags":256,"integrations":259,"difficulty":261,"author":262,"verified":32,"featured":32,"date":263,"modified":263,"icon":7,"imageSrc":7,"path":264,"alternates":265,"seo":266},"d8e0e570-89d1-4011-b782-4212390e8f4d","branch-signal-trust-decision-coach","en",null,true,"Branch Signal Trust & Decision Coach","An interactive decision coach that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and know when to rely on automation vs human judgment.","## How it works\nThis workflow turns messy branch-level numbers, conversations, and “events” into decision-ready guidance—without pretending every dashboard is a truth machine. It starts by checking your Knowledge Base (so repeated questions get consistent answers), then routes people into a practical menu of common signal problems.\n\nEach path gives a tight set of guardrails: what to trust, what’s likely contaminated, what to measure next, and when you should slow down and use human judgment before a confident meeting drives a wrong call.\n\n## Key features\n- Knowledge Base-first answers for consistency, then menu-based routing when the question needs coaching\n- A decision-shaped topic menu covering branch numbers, dirty signal detection, automation vs judgment, attribution comparisons, and signal culture\n- Follow-up buttons to either return to the menu or hand off to a human team\n- Built-in “default” handling when users don’t pick a supported option\n\n## Step-by-step\n1. **Trigger:** A message enters the workflow.\n2. **Knowledge Base check:** The workflow attempts to answer from your Knowledge Base first; if it can’t, it continues to guided routing.\n3. **Main menu:** The user picks what they’re trying to decide (trust branch numbers, spot dirty signals, automation vs judgment, comparing branches/attribution, or building signal culture).\n4. **Coaching response:** The workflow sends a tailored advisory message for the selected topic.\n5. **Next step prompt:** The user chooses either:\n   1. **More topics** (returns to the main menu), or\n   2. **Talk to a person** (hands off to the Analytics Ops team).\n6. **If no valid selection is detected:** The workflow asks the user to pick a menu option and returns to the main menu.\n\n## Setup requirements\n- No credentials required.\n- (Optional) A populated Knowledge Base improves first-response quality and consistency.\n- Configure the **Analytics Ops** department in your routing settings if you want the human handoff path to work as-is.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":201,"routingEnabled":8,"active":32},"wf-branch-signal-trust-coach","calypso-public-library","1.0.0",1,[18,33,40,52,80,90,98,104,110,116,122,128,134,140,146,153,170,177,183,191],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":24,"category":31,"deletable":32,"connectable":32},"node-flow-configs","Workflow settings","flow-configs",[23,23],40,{"name":9,"description":25,"tags":26,"triggerType":30},"Interactive coaching workflow to triage branch signal reliability and decision guardrails.",[27,28,29],"signal-hygiene","branch-metrics","decision-systems","input","policy",false,{"id":34,"name":35,"type":30,"typeVersion":16,"position":36,"parameters":39,"category":30,"deletable":32,"connectable":8},"node-input","Incoming message",[37,38],120,220,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node-kb-policy","Knowledge Base first","knowledge-base-policy",[45,38],360,{"enabled":8,"fallbackToRouting":8,"sticky":32,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":32,"instruction":49},"",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node-main-menu","Decision signals menu","interactive-message",[57,38],620,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":49,"ctaUrl":49},"list","Decision Signals Coach","Pick what you’re trying to decide. I’ll help you separate trustworthy signal from polished noise—before the meeting does something irreversible.","Tip: If the number looks perfect, ask what it’s hiding.","Choose a focus",[65,68,71,74,77],{"id":66,"title":67},"trust_branch_numbers","Trust branch numbers",{"id":69,"title":70},"spot_dirty_signal","Spot dirty signal",{"id":72,"title":73},"automation_vs_judgment","Automation vs judgment",{"id":75,"title":76},"compare_branches_attribution","Branches & attribution",{"id":78,"title":79},"build_signal_culture","Build signal culture",{"id":81,"name":82,"type":83,"typeVersion":16,"position":84,"parameters":87,"category":89,"deletable":8,"connectable":8},"node-if-trust-branch","If: trust branch numbers","if",[85,86],880,140,{"buttonId":66,"operator":88},"equals","routing",{"id":91,"name":92,"type":93,"typeVersion":16,"position":94,"parameters":96,"category":51,"deletable":8,"connectable":8},"node-text-trust-branch","Advice: trust vs noise","text-message",[95,86],1140,{"text":97},"Here’s the blunt rule: branch numbers are trustworthy when they’re *hard to game* and *easy to explain*.\n\nWhat usually deserves trust:\n- Counts tied to a real constraint (capacity, inventory, staffed hours)\n- Measures with stable definitions and boring collection paths\n- Numbers that reconcile to at least one independent source\n\nWhat’s often polished noise:\n- Anything that jumps right after incentives or leaderboard pressure\n- “Composite scores” where no one can name the ingredients confidently\n- Perfectly smooth trends in a messy world\n\nFast reality checks before you act:\n1) Ask “what would have to be true for this to be wrong?”\n2) Look for definition drift (same label, different meaning) across branches.\n3) Compare *distribution*, not just averages—one branch spike can launder a problem into a ‘good’ mean.",{"id":99,"name":100,"type":83,"typeVersion":16,"position":101,"parameters":103,"category":89,"deletable":8,"connectable":8},"node-if-dirty-signal","If: spot dirty signal",[85,102],240,{"buttonId":69,"operator":88},{"id":105,"name":106,"type":93,"typeVersion":16,"position":107,"parameters":108,"category":51,"deletable":8,"connectable":8},"node-text-dirty-signal","Advice: dirty signal",[95,102],{"text":109},"Dirty signal is sneaky because it looks *clean* on slides.\n\nEarly warning signs (the usual suspects):\n- Sudden step-changes right after a process change (“new script”, “new form”, “new tag”)\n- Missingness that isn’t random (only some branches ‘forget’ fields)\n- Overly tidy timestamps (everything happens at :00 or :30)\n- ‘Other’ category quietly growing\n\nBefore the meeting goes off the rails, do this:\n1) Pick one metric and trace 5 real examples end-to-end.\n2) Look at who produces the data and what they’re rewarded for.\n3) Split by branch, channel, and staff cohort—dirt clusters.\n\nIf the metric is used for performance management, assume it’s being managed. Then verify.",{"id":111,"name":112,"type":83,"typeVersion":16,"position":113,"parameters":115,"category":89,"deletable":8,"connectable":8},"node-if-automation","If: automation vs judgment",[85,114],340,{"buttonId":72,"operator":88},{"id":117,"name":118,"type":93,"typeVersion":16,"position":119,"parameters":120,"category":51,"deletable":8,"connectable":8},"node-text-automation","Advice: automation vs judgment",[95,114],{"text":121},"Trust automation when the decision is frequent, reversible, and the signal is well-behaved.\n\nGood automation territory:\n- Routing, prioritization, and guardrails (catching anomalies)\n- Decisions where being *consistently okay* beats occasionally brilliant\n\nRequire human judgment when:\n- The cost of being wrong is asymmetric (one bad call hurts more than many good ones help)\n- The environment changed (new policy, competitor move, system migration)\n- The metric can be gamed or ‘optimized’ without improving reality\n\nPractical rule: automate the *detection* and *recommendation*, but keep humans on the *exceptions* and *irreversible calls*.",{"id":123,"name":124,"type":83,"typeVersion":16,"position":125,"parameters":127,"category":89,"deletable":8,"connectable":8},"node-if-compare","If: compare branches & attribution",[85,126],440,{"buttonId":75,"operator":88},{"id":129,"name":130,"type":93,"typeVersion":16,"position":131,"parameters":132,"category":51,"deletable":8,"connectable":8},"node-text-compare","Advice: comparisons & attribution",[95,126],{"text":133},"Teams misread branch comparisons by treating ‘different’ as ‘better’ and attribution as ‘truth’.\n\nCommon traps:\n- Different branch mix (customers, footfall, staffing) disguised as performance\n- Small numbers: one weird week becomes a ‘trend’\n- Attribution that double-counts influence or ignores what would’ve happened anyway\n\nMake comparisons more honest:\n1) Compare like-with-like segments (same customer type, similar capacity).\n2) Use ranges and uncertainty, not single-point brag numbers.\n3) Ask what changed *first*: the behavior, the logging, or the storytelling.\n\nAttribution tip: if two channels both ‘get credit’ for the same outcome, your model is measuring reporting convenience, not causality.",{"id":135,"name":136,"type":83,"typeVersion":16,"position":137,"parameters":139,"category":89,"deletable":8,"connectable":8},"node-if-culture","If: build signal culture",[85,138],540,{"buttonId":78,"operator":88},{"id":141,"name":142,"type":93,"typeVersion":16,"position":143,"parameters":144,"category":51,"deletable":8,"connectable":8},"node-text-culture","Advice: signal culture",[95,138],{"text":145},"A good signal culture doesn’t create more dashboards—it creates fewer bad decisions.\n\nDo the basics relentlessly:\n- One owner per metric definition (no committee definitions)\n- A short ‘known failure modes’ note next to each key number\n- Pre-mortems: “How could this metric mislead us this month?”\n\nMeeting hygiene that actually works:\n1) Start with decisions, not data. “What are we choosing today?”\n2) Require one disconfirming check before committing (a single ‘reality anchor’).\n3) Celebrate people who find data problems early. They’re saving you money—quietly.\n\nIf your best analysts spend their time making slides prettier, your signal culture is already in trouble.",{"id":147,"name":148,"type":93,"typeVersion":16,"position":149,"parameters":151,"category":51,"deletable":8,"connectable":8},"node-text-default","Default: choose from menu",[95,150],660,{"text":152},"I can help most when you pick one of the menu options above. Which situation are you in right now?",{"id":154,"name":155,"type":55,"typeVersion":16,"position":156,"parameters":158,"category":51,"deletable":8,"connectable":8},"node-followup","Next step",[157,114],1400,{"messageType":159,"headerText":160,"bodyText":161,"footerText":162,"sectionTitle":49,"buttons":163,"ctaDisplayText":49,"ctaUrl":49},"button","What next?","Want another angle, or should we bring in a human to sanity-check the situation?","Good decisions love boring verification.",[164,167],{"id":165,"title":166},"more_topics","More topics",{"id":168,"title":169},"talk_to_person","Talk to a person",{"id":171,"name":172,"type":83,"typeVersion":16,"position":173,"parameters":176,"category":89,"deletable":8,"connectable":8},"node-if-more","If: more topics",[174,175],1660,300,{"buttonId":165,"operator":88},{"id":178,"name":179,"type":83,"typeVersion":16,"position":180,"parameters":182,"category":89,"deletable":8,"connectable":8},"node-if-talk","If: talk to a person",[174,181],400,{"buttonId":168,"operator":88},{"id":184,"name":185,"type":93,"typeVersion":16,"position":186,"parameters":189,"category":51,"deletable":8,"connectable":8},"node-text-restart","Restart: reopen menu",[187,188],1920,260,{"text":190},"To pick another topic, send a new message and I’ll reopen the menu.",{"id":192,"name":193,"type":194,"typeVersion":16,"position":195,"parameters":196,"category":200,"deletable":8,"connectable":32},"node-fallback-handoff","Handoff to Analytics Ops","fallback",[187,126],{"handoffMessage":197,"departmentId":198,"departmentName":199},"Got it. I’m handing this to Analytics Ops so a person can help you validate the signal before you make a high-confidence wrong decision.","dept-analytics-ops","Analytics Ops","terminal",[202,207,209,211,214,217,219,221,223,225,227,229,231,233,235,237,239,241,243,245,247,249,251,253],{"id":203,"source":34,"target":41,"sourceHandle":204,"targetHandle":205,"type":206},"conn-input-kb","out","in","edge",{"id":208,"source":41,"target":53,"sourceHandle":204,"targetHandle":205,"type":206},"conn-kb-menu",{"id":210,"source":53,"target":81,"sourceHandle":204,"targetHandle":205,"type":206},"conn-menu-if1",{"id":212,"source":81,"target":91,"sourceHandle":213,"targetHandle":205,"type":206},"conn-if1-true","true",{"id":215,"source":81,"target":99,"sourceHandle":216,"targetHandle":205,"type":206},"conn-if1-false","false",{"id":218,"source":99,"target":105,"sourceHandle":213,"targetHandle":205,"type":206},"conn-if2-true",{"id":220,"source":99,"target":111,"sourceHandle":216,"targetHandle":205,"type":206},"conn-if2-false",{"id":222,"source":111,"target":117,"sourceHandle":213,"targetHandle":205,"type":206},"conn-if3-true",{"id":224,"source":111,"target":123,"sourceHandle":216,"targetHandle":205,"type":206},"conn-if3-false",{"id":226,"source":123,"target":129,"sourceHandle":213,"targetHandle":205,"type":206},"conn-if4-true",{"id":228,"source":123,"target":135,"sourceHandle":216,"targetHandle":205,"type":206},"conn-if4-false",{"id":230,"source":135,"target":141,"sourceHandle":213,"targetHandle":205,"type":206},"conn-if5-true",{"id":232,"source":135,"target":147,"sourceHandle":216,"targetHandle":205,"type":206},"conn-if5-false",{"id":234,"source":91,"target":154,"sourceHandle":204,"targetHandle":205,"type":206},"conn-trust-to-followup",{"id":236,"source":105,"target":154,"sourceHandle":204,"targetHandle":205,"type":206},"conn-dirty-to-followup",{"id":238,"source":117,"target":154,"sourceHandle":204,"targetHandle":205,"type":206},"conn-automation-to-followup",{"id":240,"source":129,"target":154,"sourceHandle":204,"targetHandle":205,"type":206},"conn-compare-to-followup",{"id":242,"source":141,"target":154,"sourceHandle":204,"targetHandle":205,"type":206},"conn-culture-to-followup",{"id":244,"source":147,"target":154,"sourceHandle":204,"targetHandle":205,"type":206},"conn-default-to-followup",{"id":246,"source":154,"target":171,"sourceHandle":204,"targetHandle":205,"type":206},"conn-followup-ifmore",{"id":248,"source":171,"target":184,"sourceHandle":213,"targetHandle":205,"type":206},"conn-ifmore-true-restart",{"id":250,"source":171,"target":178,"sourceHandle":216,"targetHandle":205,"type":206},"conn-ifmore-false-iftalk",{"id":252,"source":178,"target":192,"sourceHandle":213,"targetHandle":205,"type":206},"conn-iftalk-true-handoff",{"id":254,"source":178,"target":184,"sourceHandle":216,"targetHandle":205,"type":206},"conn-iftalk-false-restart","automation",[27,28,29,257,258],"attribution","research",[260],"WhatsApp","intermediate","Calypso","2026-06-07T11:04:01.092Z","/en/workflows/branch-signal-trust-decision-coach",{"en":264},{"title":9,"description":267,"ogDescription":268,"twitterDescription":269,"canonicalPath":264,"robots":270,"schemaType":271,"alternates":272},"Route teams to practical checks that separate trustworthy branch signals from noise—plus a clear handoff path when judgment beats automation.","A guided coach for branch decisions: spot dirty signal early, avoid polished noise, and know when automation should (and shouldn’t) drive the call.","Turn messy branch signals into decision ready guidance. Catch dirty data before the confident meeting—and hand off when a human should decide.","index,follow","HowTo",[273],{"hreflang":6,"href":264},1785947669287]