[{"data":1,"prerenderedAt":252},["ShallowReactive",2],{"/en/workflows/signal-to-decision-coach-for-branch-leaders":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":231,"tags":232,"integrations":235,"difficulty":238,"author":239,"verified":33,"featured":33,"date":240,"modified":240,"icon":7,"imageSrc":7,"path":241,"alternates":242,"seo":243},"861f7979-03d5-40e8-9861-9d84c1acda79","signal-to-decision-coach-for-branch-leaders","en",null,true,"Signal-to-Decision Coach for Branch Leaders","A guided menu that helps teams decide which branch numbers to trust, spot dirty signals before meetings, and choose when to rely on automation vs human judgment—then offers a quick checklist or a handoff to an analyst.","## How it works\nThis workflow turns messy metrics, conversations, and branch-level events into decision-ready guidance—without pretending your data is cleaner than it is. It starts by using your Knowledge Base to answer common “what does this metric mean?” questions, then routes people into a practical coaching menu focused on what usually goes wrong first.\n\nThe outcome is simple: fewer confident wrong decisions. Users get quick, concrete checks for trusting (or doubting) branch numbers, spotting dirty signal before a meeting goes off the rails, and choosing when automation can decide vs when a human needs to look.\n\n## Key features\n- Knowledge Base-first answers for definitions and context before routing into decision coaching\n- Button-based triage menu for common decision scenarios (trust metrics, dirty signal, automation vs judgment, comparisons)\n- A reusable “Quick action” step that offers a checklist or a handoff\n- Optional escalation to a human via routing fallback to an Analytics/Insights team\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a user messages in.\n2. **Knowledge Base policy:** Calypso answers from your Knowledge Base when it can; otherwise it continues into the coaching menu.\n3. **Decision coaching menu:** The user picks what they need:\n   - Trust (or doubt) a branch metric\n   - Spot dirty signal before a meeting\n   - Decide when to trust automation vs human judgment\n   - Compare branches/conversations/attribution without fooling yourself\n   - Talk to an analyst now\n4. **Targeted guidance:** The workflow sends a practical set of checks and “what usually breaks first” warnings for the chosen scenario.\n5. **Quick action:** The user can either:\n   1) get a compact checklist to copy into notes, or\n   2) hand off to an Analytics/Insights team.\n\n## Setup requirements\n- **Calypso Knowledge Base:** Recommended (no special credentials required) so the KB step can answer metric definitions and internal terminology.\n- **Routing:** Configure a department for escalation (e.g., **Analytics & Insights**) if you want the handoff option to reach the right team.\n- No external app credentials are required for this workflow.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":187,"routingEnabled":8,"active":33},"wf_signal_to_decision_coach_branch_metrics","calypso-public-library","1.0.0",1,[18,34,41,53,81,91,97,103,109,115,123,129,135,141,157,164,169,176],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_configs","Workflow settings","flow-configs",[23,24],80,60,{"name":9,"description":26,"tags":27,"triggerType":31},"KB-first decision coaching to help teams trust the right branch numbers, spot dirty signals early, and choose automation vs human judgment.",[28,29,30],"signal-hygiene","branch-metrics","decision-making","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":40,"category":31,"deletable":33,"connectable":8},"node_input","Incoming message",[38,39],120,240,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb_policy","Knowledge Base: answer first","knowledge-base-policy",[46,39],340,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":48,"activationOpener":49,"personalization":51},"default",{"enabled":8,"instruction":50},"Use the Knowledge Base to define metrics and internal terms. If the user is asking for judgment, comparison, or reliability checks, proceed to the coaching menu.",{"useContactName":8},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"node_menu","Decision coaching menu","interactive-message",[58,39],580,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":64,"ctaUrl":64},"button","Research & decision coaching","Pick what you’re trying to decide. I’ll help you separate trustworthy signal from polished noise (before the meeting does).","Tip: Ask for definitions—I'll use the Knowledge Base first.","",[66,69,72,75,78],{"id":67,"title":68},"trust_metric","Trust this metric?",{"id":70,"title":71},"spot_dirty_signal","Spot dirty signal",{"id":73,"title":74},"automation_vs_judgment","Automation vs human",{"id":76,"title":77},"compare_branches","Compare branches",{"id":79,"title":80},"talk_to_analyst_now","Talk to analyst",{"id":82,"name":83,"type":84,"typeVersion":16,"position":85,"parameters":88,"category":90,"deletable":8,"connectable":8},"node_if_trust_metric","If: trust_metric","if",[86,87],820,140,{"buttonId":67,"operator":89},"equals","routing",{"id":92,"name":93,"type":84,"typeVersion":16,"position":94,"parameters":96,"category":90,"deletable":8,"connectable":8},"node_if_spot_dirty_signal","If: spot_dirty_signal",[86,95],220,{"buttonId":70,"operator":89},{"id":98,"name":99,"type":84,"typeVersion":16,"position":100,"parameters":102,"category":90,"deletable":8,"connectable":8},"node_if_automation_vs_judgment","If: automation_vs_judgment",[86,101],300,{"buttonId":73,"operator":89},{"id":104,"name":105,"type":84,"typeVersion":16,"position":106,"parameters":108,"category":90,"deletable":8,"connectable":8},"node_if_compare_branches","If: compare_branches",[86,107],380,{"buttonId":76,"operator":89},{"id":110,"name":111,"type":84,"typeVersion":16,"position":112,"parameters":114,"category":90,"deletable":8,"connectable":8},"node_if_talk_to_analyst_now","If: talk_to_analyst_now",[86,113],460,{"buttonId":79,"operator":89},{"id":116,"name":117,"type":118,"typeVersion":16,"position":119,"parameters":121,"category":52,"deletable":8,"connectable":8},"node_text_trust_metric","Guidance: trust a metric","text-message",[120,87],1060,{"text":122},"Quick trust test (branch metrics):\n1) **Definition stability:** Has the metric definition changed in the last 30–60 days? If yes, treat trends as suspect.\n2) **Coverage & missingness:** What % of branches/events are “unknown/other”? Pretty charts can hide ugly gaps.\n3) **Incentive check:** If the metric can be gamed, assume it is. Look for sudden step-changes right after targets changed.\n4) **Denominator sanity:** Most branch fights are denominator fights. Verify the base (eligible customers, open days, routed conversations).\n5) **Lag vs lead:** Are you reading a lagging indicator like it predicts the future? That’s how confident meetings happen.\n\nIf you tell me the metric name and the decision it’s driving, I can suggest the 2–3 checks that matter most.",{"id":124,"name":125,"type":118,"typeVersion":16,"position":126,"parameters":127,"category":52,"deletable":8,"connectable":8},"node_text_spot_dirty_signal","Guidance: spot dirty signal",[120,95],{"text":128},"Dirty-signal radar (before the meeting goes off the rails):\n- **Too clean:** Perfectly smooth lines often mean aggregation, backfills, or filters—not reality.\n- **One-source miracles:** “The dashboard says…” is not evidence. Ask for a second view (raw counts, logs, or a different system).\n- **Schema drift:** New campaign naming, new branch codes, new routing rules—same label, different meaning.\n- **Outliers with stories:** If one branch is ‘crushing it’, check whether they changed process, staffing, or tagging.\n- **Attribution gravity:** The channel with the best tracking will ‘win’ on paper, not necessarily in the business.\n\nGive me the chart/claim in one sentence and I’ll tell you where to poke first.",{"id":130,"name":131,"type":118,"typeVersion":16,"position":132,"parameters":133,"category":52,"deletable":8,"connectable":8},"node_text_automation_vs_judgment","Guidance: automation vs judgment",[120,101],{"text":134},"When to trust automation (and when to pull a human in):\n✅ **Let automation decide** when the rule is stable, stakes are low/medium, inputs are validated, and you can measure errors.\n⚠️ **Require human judgment** when:\n- the metric is easy to game,\n- the cost of a false positive is high (customer impact, compliance, reputational risk),\n- inputs are incomplete or delayed,\n- the environment changed (new branch process, new campaign, new routing).\n\nA good default: automate the *routine*, escalate the *weird*, and measure the *misses*.",{"id":136,"name":137,"type":118,"typeVersion":16,"position":138,"parameters":139,"category":52,"deletable":8,"connectable":8},"node_text_compare_branches","Guidance: comparing branches",[120,107],{"text":140},"Comparing branches/conversations/attribution without fooling yourself:\n1) **Normalize first:** Compare per eligible base (footfall, active customers, routed chats), not raw totals.\n2) **Check mix:** A ‘better’ branch may just have easier customer segments, different hours, or different product mix.\n3) **Look for policy changes:** Staffing, scripts, tagging rules, and routing changes create fake performance.\n4) **Confidence, not certainty:** Small samples love big conclusions. Ask: “How noisy is this?”\n5) **Attribution trap:** The best-tracked channel will look best. Treat attribution as a clue, not a verdict.\n\nIf you share what you’re comparing and the time window, I’ll suggest the fairest baseline.",{"id":142,"name":143,"type":56,"typeVersion":16,"position":144,"parameters":146,"category":52,"deletable":8,"connectable":8},"node_quick_action","Quick action",[120,145],520,{"messageType":60,"headerText":147,"bodyText":148,"footerText":149,"sectionTitle":64,"buttons":150,"ctaDisplayText":64,"ctaUrl":64},"Want something you can use right now?","Choose an option: I can send a copy-ready checklist, or route you to an analyst for a quick sanity check.","Good decisions love receipts.",[151,154],{"id":152,"title":153},"get_checklist","Send the checklist",{"id":155,"title":156},"talk_to_human","Route to analyst",{"id":158,"name":159,"type":84,"typeVersion":16,"position":160,"parameters":163,"category":90,"deletable":8,"connectable":8},"node_if_get_checklist","If: get_checklist",[161,162],1280,500,{"buttonId":152,"operator":89},{"id":165,"name":166,"type":84,"typeVersion":16,"position":167,"parameters":168,"category":90,"deletable":8,"connectable":8},"node_if_talk_to_human","If: talk_to_human",[161,58],{"buttonId":155,"operator":89},{"id":170,"name":171,"type":118,"typeVersion":16,"position":172,"parameters":174,"category":52,"deletable":8,"connectable":8},"node_text_checklist","Checklist: decision-ready signals",[173,162],1500,{"text":175},"Copy-ready checklist (signal → decision):\n- **What decision** will change if this number moves?\n- **Definition:** What exactly is counted? What is excluded?\n- **Denominator:** What’s the eligible base? Has it changed?\n- **Coverage:** Missing/unknown rates by branch.\n- **Drift:** Any process/tagging/routing changes in the period?\n- **Gaming risk:** Could someone ‘improve’ this without improving reality?\n- **Second view:** Can we verify with raw counts/logs or another system?\n- **Noise:** Sample size and variance—are we overreacting?\n\nIf you paste the metric + time window + decision, I’ll help you run the checklist in 2 minutes.",{"id":177,"name":178,"type":179,"typeVersion":16,"position":180,"parameters":182,"category":186,"deletable":8,"connectable":33},"node_fallback_analytics","Handoff: Analytics & Insights","fallback",[173,181],620,{"handoffMessage":183,"departmentId":184,"departmentName":185},"Routing you to Analytics & Insights for a quick signal sanity check. Please share: metric name, branches/time window, and the decision you’re trying to make.","dept_analytics_insights","Analytics & Insights","terminal",[188,192,194,196,198,200,202,204,207,209,211,213,215,217,219,221,223,225,227,229],{"id":189,"source":35,"target":42,"sourceHandle":190,"targetHandle":191,"type":48},"conn_input_to_kb","out","in",{"id":193,"source":42,"target":54,"sourceHandle":190,"targetHandle":191,"type":48},"conn_kb_to_menu",{"id":195,"source":54,"target":82,"sourceHandle":190,"targetHandle":191,"type":48},"conn_menu_to_if_trust",{"id":197,"source":54,"target":92,"sourceHandle":190,"targetHandle":191,"type":48},"conn_menu_to_if_dirty",{"id":199,"source":54,"target":98,"sourceHandle":190,"targetHandle":191,"type":48},"conn_menu_to_if_auto",{"id":201,"source":54,"target":104,"sourceHandle":190,"targetHandle":191,"type":48},"conn_menu_to_if_compare",{"id":203,"source":54,"target":110,"sourceHandle":190,"targetHandle":191,"type":48},"conn_menu_to_if_talk_now",{"id":205,"source":82,"target":116,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_trust_to_text","true",{"id":208,"source":92,"target":124,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_dirty_to_text",{"id":210,"source":98,"target":130,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_auto_to_text",{"id":212,"source":104,"target":136,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_compare_to_text",{"id":214,"source":110,"target":177,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_talk_now_to_fallback",{"id":216,"source":116,"target":142,"sourceHandle":190,"targetHandle":191,"type":48},"conn_text_trust_to_quick",{"id":218,"source":124,"target":142,"sourceHandle":190,"targetHandle":191,"type":48},"conn_text_dirty_to_quick",{"id":220,"source":130,"target":142,"sourceHandle":190,"targetHandle":191,"type":48},"conn_text_auto_to_quick",{"id":222,"source":136,"target":142,"sourceHandle":190,"targetHandle":191,"type":48},"conn_text_compare_to_quick",{"id":224,"source":142,"target":158,"sourceHandle":190,"targetHandle":191,"type":48},"conn_quick_to_if_checklist",{"id":226,"source":142,"target":165,"sourceHandle":190,"targetHandle":191,"type":48},"conn_quick_to_if_talk",{"id":228,"source":158,"target":170,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_checklist_to_text",{"id":230,"source":165,"target":177,"sourceHandle":206,"targetHandle":191,"type":48},"conn_if_talk_to_fallback","automation",[28,29,30,233,234],"attribution","automation-guardrails",[236,237],"Calypso Knowledge Base","WhatsApp","intermediate","Calypso","2026-06-12T11:04:27.629Z","/en/workflows/signal-to-decision-coach-for-branch-leaders",{"en":241},{"title":244,"description":245,"ogDescription":246,"twitterDescription":247,"canonicalPath":241,"robots":248,"schemaType":249,"alternates":250},"Signal to Decision Coach for Branch Metrics","Guide teams to trust the right branch numbers, spot dirty signals, and choose automation vs judgment—with checklists and escalation.","A practical decision coach for branch metrics: spot dirty signals early, avoid polished noise, and know when automation can decide vs when humans must.","Turn messy branch signals into decision ready checks: what to trust, what to doubt, and when automation needs human judgment—plus a quick checklist.","index,follow","HowTo",[251],{"hreflang":6,"href":241},1785947669196]