[{"data":1,"prerenderedAt":222},["ShallowReactive",2],{"/en/workflows/branch-signal-sensecheck-coach":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":202,"tags":203,"integrations":207,"difficulty":209,"author":210,"verified":33,"featured":33,"date":211,"modified":211,"icon":7,"imageSrc":7,"path":212,"alternates":213,"seo":214},"59b4cf31-c5df-4f94-989a-113e62be86fa","branch-signal-sensecheck-coach","en",null,true,"Branch Signal Sense‑Check Coach","A conversational decision-coaching workflow that helps branch leaders and analysts separate trustworthy numbers from polished noise, spot dirty signals early, and choose when automation is safe versus when human judgment must lead.","## How it works\nThis workflow turns “messy signal” moments (branch numbers, conversation notes, attribution debates, and dashboards that look suspiciously clean) into decision-shaped guidance your team can use immediately. It starts by letting your Knowledge Base answer common questions, then routes the user into a short set of practical coaching paths.\n\nIt’s designed for the real failure mode: bad data that looks fine right up until a confident meeting makes a wrong call. The prompts are plain-spoken, oriented around what to trust, what to challenge, and what to check first—without asking anyone to become a statistician.\n\n## Key features\n- Knowledge Base first: answers known policy/process questions before routing into coaching paths.\n- Button-driven triage: users choose the exact decision problem (trusting branch numbers, dirty signals, automation vs judgment, comparisons, culture).\n- Guardrail-style guidance: each path gives quick checks, common traps, and what to do next.\n- Loop-back menu: after any guidance, users can pick another path without restarting.\n- Human handoff option: routes to a fallback handoff when someone needs a real person.\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a message arrives in **Calypso Inbox**.\n2. **Knowledge Base policy check:** Calypso attempts to answer using your Knowledge Base. If it can’t confidently answer, it continues to the coaching menu.\n3. **Decision menu:** The user picks one option:\n   - **Which branch numbers deserve trust**\n   - **Spot dirty signal before the meeting**\n   - **Automation vs human judgment**\n   - **Comparing branches & attribution traps**\n   - **Building a signal culture (less slide, more decision)**\n   - **Talk to a person**\n4. **Guidance path:** The workflow sends a tailored guidance message for the selected option.\n5. **Loop back:** After delivering guidance, the workflow returns to the menu so the user can run another check.\n6. **Handoff (optional):** If the user selects **Talk to a person**, the workflow sends a handoff message and routes to the configured team.\n\n## Setup requirements\n- **Calypso Inbox** connected to the channel where your team receives these questions.\n- **Calypso Knowledge Base** content (recommended): definitions of key metrics, branch reporting rules, attribution conventions, and known data-quality caveats.\n- No external credentials are required by this workflow.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":169,"routingEnabled":8,"active":33},"wf_branch_signal_sense_check_coach_v1","calypso-public-library","1.0.0",1,[18,34,40,52,83,92,100,105,111,117,123,129,135,141,147,152,162],{"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],120,80,{"name":9,"description":26,"tags":27,"triggerType":31},"Decision coaching for branch signals: trust checks, dirty-signal spotting, automation vs judgment, comparison traps, and culture guardrails.",[28,29,30],"signal-hygiene","branch-metrics","decision-systems","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":39,"category":31,"deletable":33,"connectable":8},"node_input","Inbound message",[23,38],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":8,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"Answer using the Knowledge Base when possible. If the user’s request is about signal trust, branch comparisons, attribution confusion, or “is this number real?”, provide a short practical answer. If confidence is low or the request is ambiguous, route to the coaching menu.",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_menu","Choose what you’re deciding","interactive-message",[57,38],620,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Signal sense-check","Pick the decision you’re trying to make. I’ll give you the fast checks that prevent a confident wrong call.","Tip: check definitions, timing, incentives.","",[65,68,71,74,77,80],{"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 or human",{"id":75,"title":76},"compare_branches_attribution","Compare branches",{"id":78,"title":79},"build_signal_culture","Build signal culture",{"id":81,"title":82},"talk_to_person","Talk to a person",{"id":84,"name":85,"type":86,"typeVersion":16,"position":87,"parameters":89,"category":91,"deletable":8,"connectable":8},"node_if_trust","If: trust branch numbers","if",[88,23],880,{"buttonId":66,"operator":90},"equals","routing",{"id":93,"name":94,"type":95,"typeVersion":16,"position":96,"parameters":98,"category":51,"deletable":8,"connectable":8},"node_text_trust","Trust checks for branch numbers","text-message",[97,23],1140,{"text":99},"Here’s the branch-number trust checklist (the boring stuff that saves you):\n\n1) Definition lock: what EXACTLY is counted (and what is excluded)? If two people describe it differently, it’s not a metric—it’s a vibe.\n2) Timing reality: when does it post, and what backfills later? Fresh-looking numbers can be half-baked.\n3) Denominator sanity: ask “out of what?” Great rates often hide shrinking denominators.\n4) Incentive pressure: if someone is rewarded for the number, assume it will drift—often in subtle, plausible ways.\n5) Reconciliation hook: can you tie it to an external-ish anchor (cash movement, inventory change, appointment logs)? One anchor beats five pretty charts.\n\nIf you want: tell me the metric name + the decision you’re about to make, and I’ll suggest the *first* two checks that usually catch the lie.",{"id":101,"name":102,"type":86,"typeVersion":16,"position":103,"parameters":104,"category":91,"deletable":8,"connectable":8},"node_if_dirty","If: spot dirty signal",[88,38],{"buttonId":69,"operator":90},{"id":106,"name":107,"type":95,"typeVersion":16,"position":108,"parameters":109,"category":51,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal early-warning signs",[97,38],{"text":110},"How to spot dirty signal *before* the meeting turns into a victory lap:\n\n- Sudden “step changes” with no operational story (no staffing shift, no promo, no weather/event, no policy change). Miracles require receipts.\n- Too-consistent improvement across every branch. Real life is lumpy.\n- Missing data that looks like zeros (or zeros that look like missing).\n- A metric that improves while its natural counter-metric stays flat (e.g., conversions up but footfall unchanged).\n- A perfect narrative with no messy edge cases.\n\nFast move: ask for 10 raw examples (calls, tickets, transactions, lead records) behind the number. If the examples are hard to fetch, the number is probably harder to trust.",{"id":112,"name":113,"type":86,"typeVersion":16,"position":114,"parameters":116,"category":91,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[88,115],320,{"buttonId":72,"operator":90},{"id":118,"name":119,"type":95,"typeVersion":16,"position":120,"parameters":121,"category":51,"deletable":8,"connectable":8},"node_text_auto","When to trust automation",[97,115],{"text":122},"When leaders should trust automation (and when they really shouldn’t):\n\nTrust automation when:\n- The input signals are stable, well-defined, and hard to game.\n- The cost of a wrong decision is low or reversible.\n- You have a clean feedback loop (you’ll know within days/weeks if it worked).\n\nForce human judgment when:\n- Definitions are contested (“what counts?” arguments).\n- The metric is reward-linked (gaming risk is high).\n- You’re comparing branches with different realities (mix, staffing, demand).\n- The downside is asymmetric (one bad call is expensive).\n\nRule of thumb: automate the *routine decision*, not the *responsibility*. Keep a human accountable for edge cases and for updating the rules when reality changes.",{"id":124,"name":125,"type":86,"typeVersion":16,"position":126,"parameters":128,"category":91,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[88,127],420,{"buttonId":75,"operator":90},{"id":130,"name":131,"type":95,"typeVersion":16,"position":132,"parameters":133,"category":51,"deletable":8,"connectable":8},"node_text_compare","Branch comparison traps",[97,127],{"text":134},"What teams repeatedly misread when comparing branches, conversations, and attribution:\n\n- Different denominators: Branch A’s “conversion” might be out of walk-ins; Branch B’s might be out of booked appointments.\n- Channel mix drift: A branch that gets higher-intent leads will look “better” even if execution is worse.\n- Conversation volume bias: more calls can mean more problems, not more demand.\n- Attribution double-counting: the same customer touches multiple channels—credit gets assigned to whoever logs last.\n- Operational constraints: staffing, inventory, local rules, weather, and geography quietly dominate.\n\nFair comparison move: normalize on *opportunities of the same kind*, then compare distribution (median + spread), not just averages. If the spread collapses overnight, suspect reporting, not excellence.",{"id":136,"name":137,"type":86,"typeVersion":16,"position":138,"parameters":140,"category":91,"deletable":8,"connectable":8},"node_if_culture","If: build signal culture",[88,139],520,{"buttonId":78,"operator":90},{"id":142,"name":143,"type":95,"typeVersion":16,"position":144,"parameters":145,"category":51,"deletable":8,"connectable":8},"node_text_culture","Build a signal culture that decides",[97,139],{"text":146},"How to build a signal culture that helps decisions happen (not just slides):\n\n- Always pair a metric with a decision: “If this moves, what will we do?” No decision = vanity.\n- Publish definitions like policy. If it’s optional, it will be reinterpreted.\n- Track ‘known failure modes’ openly (late postings, backfills, outages, common mis-tags).\n- Require one counter-metric per headline metric (keeps storytelling honest).\n- Make it normal to ask for raw examples. Not to shame—just to stay anchored.\n\nA little wit, a lot of truth: dashboards don’t lie, but they *do* enable lying when nobody asks boring questions.",{"id":148,"name":149,"type":86,"typeVersion":16,"position":150,"parameters":151,"category":91,"deletable":8,"connectable":8},"node_if_human","If: talk to a person",[88,57],{"buttonId":81,"operator":90},{"id":153,"name":154,"type":155,"typeVersion":16,"position":156,"parameters":157,"category":161,"deletable":8,"connectable":8},"node_fallback_handoff","Handoff to team","fallback",[97,57],{"handoffMessage":158,"departmentId":159,"departmentName":160},"Got it—looping in a teammate for a human review. If you can, paste the metric name, the branch set, and the decision you’re about to make (hire/allocate budget/change process/etc.).","ops-analytics","Operations Analytics","terminal",{"id":163,"name":164,"type":95,"typeVersion":16,"position":165,"parameters":167,"category":51,"deletable":8,"connectable":8},"node_text_unknown","If: no match",[97,166],720,{"text":168},"I didn’t catch a menu choice. Try tapping one of the buttons—then I can give you the right checks fast.",[170,172,174,176,179,182,184,186,188,190,192,194,196,198,200],{"id":171,"source":35,"target":41,"sourceHandle":47,"targetHandle":47,"type":47},"conn_input_to_kb",{"id":173,"source":41,"target":53,"sourceHandle":47,"targetHandle":47,"type":47},"conn_kb_to_menu",{"id":175,"source":53,"target":84,"sourceHandle":47,"targetHandle":47,"type":47},"conn_menu_to_if_trust",{"id":177,"source":84,"target":93,"sourceHandle":178,"targetHandle":47,"type":47},"conn_if_trust_true_to_text","true",{"id":180,"source":84,"target":101,"sourceHandle":181,"targetHandle":47,"type":47},"conn_if_trust_false_to_if_dirty","false",{"id":183,"source":101,"target":106,"sourceHandle":178,"targetHandle":47,"type":47},"conn_if_dirty_true_to_text",{"id":185,"source":101,"target":112,"sourceHandle":181,"targetHandle":47,"type":47},"conn_if_dirty_false_to_if_auto",{"id":187,"source":112,"target":118,"sourceHandle":178,"targetHandle":47,"type":47},"conn_if_auto_true_to_text",{"id":189,"source":112,"target":124,"sourceHandle":181,"targetHandle":47,"type":47},"conn_if_auto_false_to_if_compare",{"id":191,"source":124,"target":130,"sourceHandle":178,"targetHandle":47,"type":47},"conn_if_compare_true_to_text",{"id":193,"source":124,"target":136,"sourceHandle":181,"targetHandle":47,"type":47},"conn_if_compare_false_to_if_culture",{"id":195,"source":136,"target":142,"sourceHandle":178,"targetHandle":47,"type":47},"conn_if_culture_true_to_text",{"id":197,"source":136,"target":148,"sourceHandle":181,"targetHandle":47,"type":47},"conn_if_culture_false_to_if_human",{"id":199,"source":148,"target":153,"sourceHandle":178,"targetHandle":47,"type":47},"conn_if_human_true_to_fallback",{"id":201,"source":148,"target":163,"sourceHandle":181,"targetHandle":47,"type":47},"conn_if_human_false_to_unknown","automation",[28,29,30,204,205,206],"attribution","data-quality","ops-coaching",[208],"Calypso Inbox","intermediate","Calypso","2026-06-21T11:03:10.476Z","/en/workflows/branch-signal-sensecheck-coach",{"en":212},{"title":9,"description":215,"ogDescription":216,"twitterDescription":217,"canonicalPath":212,"robots":218,"schemaType":219,"alternates":220},"Coach leaders to trust the right branch numbers, spot dirty signals early, and choose when automation is safe vs when judgment must lead.","A practical coaching workflow for branch metrics: separate trustworthy numbers from polished noise, catch dirty signal early, and avoid confident wrong decisions.","Turn messy branch signals into decision ready checks: what to trust, what to challenge, and when automation needs a human in the loop.","index,follow","HowTo",[221],{"hreflang":6,"href":212},1785947667850]