[{"data":1,"prerenderedAt":292},["ShallowReactive",2],{"/en/workflows/branch-signal-decision-briefing":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":272,"tags":273,"integrations":276,"difficulty":279,"author":280,"verified":33,"featured":33,"date":281,"modified":281,"icon":7,"imageSrc":7,"path":282,"alternates":283,"seo":284},"5703878a-8fa5-4df9-9379-3ae0c9a41b22","branch-signal-decision-briefing","en",null,true,"Branch Signal Decision Briefing","Turn messy branch metrics and conversation signals into decision-ready checks. Helps teams spot polished noise, dirty data, and when automation needs human judgment.","## How it works\nThis workflow helps branch leaders and ops teams pressure-test “good-looking” numbers before they become confident wrong decisions. It first attempts to answer using your Calypso Knowledge Base (so repeat questions get consistent answers), then guides the user through a practical decision-shaped menu: metric trust checks, dirty-signal spotting, automation vs. judgment, branch comparisons, and building a signal culture.\n\nWhen the user needs help beyond the playbook, they can request a handoff to a human (e.g., an insights/analytics desk). The goal is not to over-clean the data—it’s to keep the truth intact long enough to make a better call.\n\n## Key features\n- Knowledge Base-first responses for consistent guidance on common signal/metric questions.\n- Button-based menu to route users to the right decision check quickly.\n- Practical “sanity checks” for branch numbers that often look fine until they fail.\n- Clear guidance on when automation is safe and when judgment must stay in the loop.\n- Optional handoff to a human team via Calypso routing when the situation is messy or high-stakes.\n\n## Step-by-step\n1. **Trigger:** A user sends a message into the workflow.\n2. **Knowledge Base attempt:** The workflow tries to answer using the **Signal Decision Knowledge** policy.\n3. **Menu:** The user receives **Choose a decision check** with buttons:\n   - Audit a branch metric\n   - Spot dirty signal\n   - Automation vs judgment\n   - Compare branches & attribution\n   - Build signal culture\n   - Talk to an analyst\n4. **Routing:** The workflow checks which button was clicked and sends the matching guidance message.\n5. **Next actions:** The user gets a **What would you like to do next?** menu:\n   - Back to menu\n   - Talk to an analyst\n6. **Handoff (optional):** If requested, the workflow routes the conversation to **Insights Desk** with a short context-setting message.\n\n## Setup requirements\n- **Calypso Knowledge Base** content for signal definitions, metric rules, and your organization’s preferred measurement practices (recommended).\n- **Calypso Inbox routing** configured with a destination team/department (used for the “Talk to an analyst” handoff).\n- No additional external credentials are required for this workflow as written.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":218,"routingEnabled":8,"active":33},"wf_branch_signal_decision_briefing_v1","calypso-public-library","1.0.0",1,[18,34,41,53,85,94,102,108,115,121,127,133,140,146,153,159,170,177,192,198,203,211],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":32,"deletable":33,"connectable":33},"node_flow_cfg","Workflow settings","flow-configs",[23,24],60,40,{"name":9,"description":26,"tags":27,"triggerType":31},"Decision-shaped guidance to audit branch numbers, spot dirty signals, and route high-stakes cases to a human.",[28,29,30],"branch-metrics","signal-hygiene","decision-systems","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,180,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb_policy","Signal Decision Knowledge","knowledge-base-policy",[46,39],340,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":48,"activationOpener":49,"personalization":51},"ai_sticky_release",{"enabled":8,"instruction":50},"I can help you sanity-check branch numbers and messy signals—without cleaning away the truth. Pick a decision check below, or ask your question plainly.",{"useContactName":8},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"node_menu_main","Choose a decision check","interactive-message",[58,39],560,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":84,"ctaUrl":84},"button","Decision checks","Choose the kind of signal you’re dealing with. The fastest way to avoid a confident wrong decision is to test the *definition*, not just the dashboard.","Tip: Up with no “why” = hypothesis, not conclusion.","Options",[66,69,72,75,78,81],{"id":67,"title":68},"audit_branch_metric","Audit a metric",{"id":70,"title":71},"spot_dirty_signal","Spot dirty signal",{"id":73,"title":74},"automation_vs_judgment","Auto vs judgment",{"id":76,"title":77},"compare_branches_attribution","Compare & attribute",{"id":79,"title":80},"build_signal_culture","Build signal culture",{"id":82,"title":83},"talk_to_analyst","Talk to an analyst","",{"id":86,"name":87,"type":88,"typeVersion":16,"position":89,"parameters":91,"category":93,"deletable":8,"connectable":8},"node_if_audit","If: Audit a branch metric","if",[90,39],780,{"buttonId":67,"operator":92},"equals","routing",{"id":95,"name":96,"type":97,"typeVersion":16,"position":98,"parameters":100,"category":52,"deletable":8,"connectable":8},"node_text_audit","Metric trust checks","text-message",[99,38],1000,{"text":101},"Here’s the fastest “is this metric decision-ready?” audit:\n\n1) **Definition lock:** Can two people compute it and get the same answer? If not, it’s vibes.\n2) **Denominator sanity:** What’s the base? (per branch, per customer, per conversation?) Denominators create miracles.\n3) **Coverage:** Are there missing days/queues/branches that conveniently vanish? Missingness often has opinions.\n4) **Lag & timing:** Is it early and noisy (daily) or stable enough (weekly/monthly) for the decision you’re making?\n5) **Incentives & gaming:** If people can win by moving this number, they will—especially quietly.\n\nIf you want one shortcut: **ask what changed operationally**. If the metric moved but reality didn’t, the pipeline changed—not performance.",{"id":103,"name":104,"type":88,"typeVersion":16,"position":105,"parameters":107,"category":93,"deletable":8,"connectable":8},"node_if_dirty","If: Spot dirty signal",[90,106],280,{"buttonId":70,"operator":92},{"id":109,"name":110,"type":97,"typeVersion":16,"position":111,"parameters":113,"category":52,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal detectors",[99,112],260,{"text":114},"Dirty data rarely looks dirty. It looks *confident*.\n\nWatch for these tells before a meeting goes off the rails:\n- **Step-change without a cause:** A clean vertical jump usually means a tracking change, backfill, or definition drift.\n- **Too-smooth trends:** Real operations are lumpy. Perfect smoothness can be aggregation masking pain.\n- **One branch is “special” every week:** Repeated outlier = pipeline quirk, policy difference, or a different customer mix.\n- **Volume doesn’t match capacity:** If conversations rise but staffing/footfall didn’t, check routing, bot deflection, or channel tagging.\n\nTwo questions that save careers:\n1) “What would we expect to see *if this were wrong*?”\n2) “Which part of the process could create this pattern without changing reality?”",{"id":116,"name":117,"type":88,"typeVersion":16,"position":118,"parameters":120,"category":93,"deletable":8,"connectable":8},"node_if_auto","If: Automation vs judgment",[90,119],380,{"buttonId":73,"operator":92},{"id":122,"name":123,"type":97,"typeVersion":16,"position":124,"parameters":125,"category":52,"deletable":8,"connectable":8},"node_text_auto","When to trust automation",[99,119],{"text":126},"Automation is great at consistency. It’s terrible at context.\n\n**Trust automation more when:**\n- Definitions are stable and written down.\n- Volume is high (noise averages out).\n- The downside is limited (you can reverse the decision quickly).\n- You have drift checks (alerts when inputs/coverage change).\n\n**Require human judgment when:**\n- Sample sizes are small (a few customers can “move” a branch).\n- Incentives are strong (people can game the metric).\n- The decision is one-way (hiring, closing, major budget shifts).\n- The story depends on *why* (conversations, sentiment, local events), not just *what*.\n\nPractical rule: **automate the recommendation, not the responsibility**.",{"id":128,"name":129,"type":88,"typeVersion":16,"position":130,"parameters":132,"category":93,"deletable":8,"connectable":8},"node_if_compare","If: Compare branches & attribution",[90,131],480,{"buttonId":76,"operator":92},{"id":134,"name":135,"type":97,"typeVersion":16,"position":136,"parameters":138,"category":52,"deletable":8,"connectable":8},"node_text_compare","Branch comparison pitfalls",[99,137],500,{"text":139},"Branch comparisons go wrong in the same predictable ways:\n\n- **Mix shift:** Different customer types, product mix, or issue complexity. The “better branch” may just have easier problems.\n- **Seasonality & local events:** One branch has construction outside or a local festival—your dashboard won’t mention it.\n- **Channel tagging drift:** If one branch routes more chats/WhatsApp into a different bucket, it can look like performance changed.\n- **Attribution magnetism:** A branch that talks to customers later in the journey can “steal credit” (or take blame) depending on your rules.\n\nQuick fix: compare **like-with-like slices** (same issue type, same channel, similar volume bands) before you compare totals.",{"id":141,"name":142,"type":88,"typeVersion":16,"position":143,"parameters":145,"category":93,"deletable":8,"connectable":8},"node_if_culture","If: Build signal culture",[90,144],580,{"buttonId":79,"operator":92},{"id":147,"name":148,"type":97,"typeVersion":16,"position":149,"parameters":151,"category":52,"deletable":8,"connectable":8},"node_text_culture","Signal culture that drives decisions",[99,150],620,{"text":152},"A good signal culture makes decisions easier, not slide decks longer.\n\nSteal these habits:\n- **Metric owner + definition:** One named owner, one written definition, one place to change it.\n- **Decision log:** “We decided X because Y.” Later you’ll learn what was signal vs. theater.\n- **Confidence labels:** Green/yellow/red—not for drama, for honesty about data quality and sample size.\n- **Pre-mortem prompt:** “If we’re wrong, what’s the first thing that will show it?”\n- **Escalation norm:** It’s respected (not punished) to say: “This is noisy—hold the decision.”\n\nWit-sized truth: if the only time you discuss data quality is after a bad outcome, you don’t have a data culture—you have an apology process.",{"id":154,"name":155,"type":88,"typeVersion":16,"position":156,"parameters":158,"category":93,"deletable":8,"connectable":8},"node_if_handoff","If: Talk to an analyst",[90,157],680,{"buttonId":82,"operator":92},{"id":160,"name":161,"type":162,"typeVersion":16,"position":163,"parameters":165,"category":169,"deletable":8,"connectable":8},"node_handoff","Route to Insights Desk","fallback",[99,164],740,{"handoffMessage":166,"departmentId":167,"departmentName":168},"Routing you to the Insights Desk. To speed this up, share: which branch(es), date range, the exact metric name/definition, and what decision you’re trying to make.","insights-desk","Insights Desk","terminal",{"id":171,"name":172,"type":97,"typeVersion":16,"position":173,"parameters":175,"category":52,"deletable":8,"connectable":8},"node_text_unknown","Unrecognized selection",[99,174],860,{"text":176},"I didn’t catch a menu selection. Pick a button from the last menu message so I can route you to the right decision check—or send one sentence (metric + branch + the decision you’re making).",{"id":178,"name":179,"type":56,"typeVersion":16,"position":180,"parameters":183,"category":52,"deletable":8,"connectable":8},"node_menu_next","What would you like to do next?",[181,182],1220,420,{"messageType":60,"headerText":184,"bodyText":185,"footerText":84,"sectionTitle":64,"buttons":186,"ctaDisplayText":84,"ctaUrl":84},"Next step","Want another check, or do you need a human to dig in?",[187,190],{"id":188,"title":189},"back_to_menu","Back to menu",{"id":191,"title":83},"handoff_insights",{"id":193,"name":194,"type":88,"typeVersion":16,"position":195,"parameters":197,"category":93,"deletable":8,"connectable":8},"node_if_back","If: Back to menu",[196,119],1440,{"buttonId":188,"operator":92},{"id":199,"name":200,"type":88,"typeVersion":16,"position":201,"parameters":202,"category":93,"deletable":8,"connectable":8},"node_if_handoff2","If: Handoff from next step",[196,137],{"buttonId":191,"operator":92},{"id":204,"name":205,"type":97,"typeVersion":16,"position":206,"parameters":209,"category":52,"deletable":8,"connectable":8},"node_text_back","Re-open the menu",[207,208],1660,360,{"text":210},"To bring the decision-check menu back, send a new message with **menu** (or tell me the metric + branch + decision in one sentence).",{"id":212,"name":213,"type":97,"typeVersion":16,"position":214,"parameters":216,"category":52,"deletable":8,"connectable":8},"node_text_close","Close",[207,215],600,{"text":217},"Understood. If you need another decision check later, just message again and I’ll bring the menu back.",[219,222,224,226,229,232,234,236,238,240,242,244,246,248,250,252,254,256,258,260,262,264,266,268,270],{"id":220,"source":35,"target":42,"sourceHandle":221,"targetHandle":221,"type":221},"conn_input_to_kb","default",{"id":223,"source":42,"target":54,"sourceHandle":221,"targetHandle":221,"type":221},"conn_kb_to_menu",{"id":225,"source":54,"target":86,"sourceHandle":221,"targetHandle":221,"type":221},"conn_menu_to_if_audit",{"id":227,"source":86,"target":95,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_audit_true_to_text","true",{"id":230,"source":86,"target":103,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_audit_false_to_if_dirty","false",{"id":233,"source":103,"target":109,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_dirty_true_to_text",{"id":235,"source":103,"target":116,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_dirty_false_to_if_auto",{"id":237,"source":116,"target":122,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_auto_true_to_text",{"id":239,"source":116,"target":128,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_auto_false_to_if_compare",{"id":241,"source":128,"target":134,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_compare_true_to_text",{"id":243,"source":128,"target":141,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_compare_false_to_if_culture",{"id":245,"source":141,"target":147,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_culture_true_to_text",{"id":247,"source":141,"target":154,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_culture_false_to_if_handoff",{"id":249,"source":154,"target":160,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_handoff_true_to_fallback",{"id":251,"source":154,"target":171,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_handoff_false_to_unknown",{"id":253,"source":95,"target":178,"sourceHandle":221,"targetHandle":221,"type":221},"conn_text_audit_to_next",{"id":255,"source":109,"target":178,"sourceHandle":221,"targetHandle":221,"type":221},"conn_text_dirty_to_next",{"id":257,"source":122,"target":178,"sourceHandle":221,"targetHandle":221,"type":221},"conn_text_auto_to_next",{"id":259,"source":134,"target":178,"sourceHandle":221,"targetHandle":221,"type":221},"conn_text_compare_to_next",{"id":261,"source":147,"target":178,"sourceHandle":221,"targetHandle":221,"type":221},"conn_text_culture_to_next",{"id":263,"source":178,"target":193,"sourceHandle":221,"targetHandle":221,"type":221},"conn_menu_next_to_if_back",{"id":265,"source":193,"target":204,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_back_true_to_back_text",{"id":267,"source":193,"target":199,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_back_false_to_if_handoff2",{"id":269,"source":199,"target":160,"sourceHandle":228,"targetHandle":221,"type":221},"conn_if_handoff2_true_to_fallback",{"id":271,"source":199,"target":212,"sourceHandle":231,"targetHandle":221,"type":221},"conn_if_handoff2_false_to_close","automation",[28,29,30,274,275],"attribution","leadership",[277,278],"Calypso Knowledge Base","Calypso Inbox Routing","intermediate","Calypso","2026-07-31T11:04:57.329Z","/en/workflows/branch-signal-decision-briefing",{"en":282},{"title":9,"description":285,"ogDescription":286,"twitterDescription":287,"canonicalPath":282,"robots":288,"schemaType":289,"alternates":290},"Guide teams to trust the right branch numbers, spot dirty signals early, and know when automation needs human judgment—with optional handoff.","A practical, decision shaped workflow to sanity check branch metrics, catch dirty data before meetings, and route high stakes cases to a human.","Pressure test branch numbers, detect polished noise, and decide when automation is safe. Includes a quick handoff path for messy cases.","index,follow","HowTo",[291],{"hreflang":6,"href":282},1785947666116]