[{"data":1,"prerenderedAt":224},["ShallowReactive",2],{"/en/workflows/branch-signal-readiness-navigator":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":205,"tags":206,"integrations":209,"difficulty":211,"author":212,"verified":32,"featured":32,"date":213,"modified":213,"icon":7,"imageSrc":7,"path":214,"alternates":215,"seo":216},"2cf595a3-ff75-45e1-99d7-81732b27001f","branch-signal-readiness-navigator","en",null,true,"Branch Signal Readiness Navigator","A guided chat workflow that helps branch leaders pressure-test numbers, spot dirty signals early, and decide when to trust automation vs. escalate to human judgment.","## How it works\nThis workflow turns “looks-good-on-the-slide” branch reporting into decision-ready confidence. It starts with a short knowledge-based guidance layer (so the advice stays consistent), then lets a leader pick the decision they’re trying to make—trust branch numbers, detect dirty signal, compare branches fairly, or decide when to rely on automation.\n\nThe goal isn’t academic purity. It’s preventing the most common failure mode: clean-looking metrics that are quietly wrong, leading to a confident meeting and an expensive decision.\n\n## Key features\n- Knowledge-base guided coaching before routing, so guidance stays consistent across teams\n- Decision-shaped menu that routes leaders to practical checks (not generic “data best practices”)\n- “Chain of proof” prompts to spot polished noise vs. trustworthy branch numbers\n- Clear guardrails for when automation is reliable—and when a human still needs to look\n- One-click escalation to a human team via handoff when the risk is high or the signal is disputed\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a user enters the flow.\n2. **Knowledge guidance:** A knowledge-base policy node primes the interaction to keep the advice consistent and decision-oriented.\n3. **Choose a decision check:** An interactive menu asks what the user wants to pressure-test (numbers, dirty signal, automation vs. judgment, comparisons/attribution, culture).\n4. **Run the selected playbook:** The workflow routes to a short, concrete checklist tailored to that choice.\n5. **Escalate if needed:** If the user selects escalation, the workflow hands off to the **Business Analytics** department with a crisp handoff message.\n6. **Fallback safety net:** If the selection can’t be matched, the workflow routes to a default handoff so the user doesn’t get stuck.\n\n## Setup requirements\n- No external credentials are required.\n- Configure (or confirm) a **Business Analytics** department in Calypso to receive handoffs, and update the department ID in the workflow if needed.\n- Optional but recommended: maintain a short internal knowledge base article set on metric definitions (e.g., “Active customer”, “Qualified lead”, “Branch attribution rules”) to improve consistency of guidance.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":170,"routingEnabled":8,"active":32},"wf_branch_signal_readiness_navigator","calypso-public-library","1.0.0",1,[18,33,39,51,82,92,100,106,112,118,124,129,135,141,147,153,163],{"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},"Guided decision checks for branch numbers, dirty signal detection, and automation vs. human judgment. Includes escalation to Business Analytics.",[27,28,29],"signal-quality","branch-metrics","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","Start",[37,37],240,{},{"id":40,"name":41,"type":42,"typeVersion":16,"position":43,"parameters":45,"category":50,"deletable":8,"connectable":8},"node_kb_policy","Decision guidance policy","knowledge-base-policy",[44,37],460,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":46,"activationOpener":47,"personalization":49},"default",{"enabled":8,"instruction":48},"Be practical and decision-focused. Prefer quick checks over theory. Call out common failure modes where metrics look fine but are wrong. Keep a little wit, avoid jargon, and ask for the minimum context needed.",{"useContactName":8},"response",{"id":52,"name":53,"type":54,"typeVersion":16,"position":55,"parameters":57,"category":50,"deletable":8,"connectable":8},"node_menu","Choose a decision check","interactive-message",[56,37],700,{"messageType":58,"headerText":59,"bodyText":60,"footerText":61,"sectionTitle":62,"buttons":63,"ctaDisplayText":62,"ctaUrl":62},"button","Signal Readiness Navigator","What are you trying to decide right now? Pick the check that matches your meeting (or your worry).","Tip: if the number is “too smooth,” start with Dirty signal.","",[64,67,70,73,76,79],{"id":65,"title":66},"check_branch_numbers","Trust numbers",{"id":68,"title":69},"spot_dirty_signal","Spot dirty signal",{"id":71,"title":72},"automation_vs_judgment","Automation vs human",{"id":74,"title":75},"compare_branches_attribution","Compare branches",{"id":77,"title":78},"build_signal_culture","Build signal culture",{"id":80,"title":81},"handoff_analyst","Escalate to analyst",{"id":83,"name":84,"type":85,"typeVersion":16,"position":86,"parameters":89,"category":91,"deletable":8,"connectable":8},"node_if_1","If: trust numbers","if",[87,88],940,160,{"buttonId":65,"operator":90},"equals","routing",{"id":93,"name":94,"type":95,"typeVersion":16,"position":96,"parameters":98,"category":50,"deletable":8,"connectable":8},"node_msg_trust_numbers","Checklist: numbers worth trusting","text-message",[97,88],1180,{"text":99},"Here’s the fast way to tell a trustworthy branch number from polished noise:\n\n1) **Definition stability:** Has the definition stayed the same for 90 days? If not, you’re comparing edits, not performance.\n2) **Collection path:** Is it captured at the moment of truth (transaction, appointment, verified call), or inferred later (spreadsheets, “someone said”)?\n3) **Denominator sanity:** Ask “out of what?” If the denominator changes quietly (traffic, staffing, eligible customers), the rate can lie politely.\n4) **Lag and reversals:** What % of this metric gets corrected next week/month? High reversals = low decision value.\n5) **Gaming surface area:** If bonuses or attention depend on it, assume it gets optimized. Use a second, harder-to-game counter-metric.\n\nIf you share the metric name and branch comparison you’re making, I can tell you which of these checks matters most.",{"id":101,"name":102,"type":85,"typeVersion":16,"position":103,"parameters":105,"category":91,"deletable":8,"connectable":8},"node_if_2","If: dirty signal",[87,104],260,{"buttonId":68,"operator":90},{"id":107,"name":108,"type":95,"typeVersion":16,"position":109,"parameters":110,"category":50,"deletable":8,"connectable":8},"node_msg_dirty_signal","Checklist: spot dirty signal",[97,104],{"text":111},"Dirty signal usually shows up as *confidence without friction*. Quick red flags before the meeting goes off the rails:\n\n- **Too-clean trend lines:** Perfectly smooth growth often means batching, backfills, or a reporting change.\n- **One source only:** If a “truth” has no independent cross-check (payments, call logs, scheduling, inventory), treat it as a hypothesis.\n- **Sharp step-change with no story:** Real operations change with a narrative (staffing, hours, local event). No story = likely instrumentation.\n- **Outliers that only help:** If exceptions always make the branch look better, you’re seeing selective reporting.\n- **Last-touch miracles:** If attribution suddenly concentrates in one channel, check tracking changes and duplications.\n\nPractical move: pick **one** “hard” reality anchor (e.g., verified transactions, kept appointments) and reconcile it against the headline metric.",{"id":113,"name":114,"type":85,"typeVersion":16,"position":115,"parameters":117,"category":91,"deletable":8,"connectable":8},"node_if_3","If: automation vs judgment",[87,116],360,{"buttonId":71,"operator":90},{"id":119,"name":120,"type":95,"typeVersion":16,"position":121,"parameters":122,"category":50,"deletable":8,"connectable":8},"node_msg_automation","Guardrails: automation vs human judgment",[97,116],{"text":123},"When to trust automation (and when to pull a human into the loop):\n\nTrust automation when:\n- **The inputs are constrained** (clear rules, low ambiguity).\n- **Errors are cheap** (a wrong nudge, not a wrong territory redesign).\n- **You have feedback fast** (you’ll know within days if it’s working).\n\nRequire human judgment when:\n- **The cost of being wrong is high** (staffing, closures, major spend shifts).\n- **Incentives are involved** (metrics tied to bonuses get “creative”).\n- **The system is changing** (new tracking, new definitions, new process).\n\nRule of thumb: automate the *repeatable checks* (sanity tests, reconciliation), but keep humans responsible for *the decision* when downside risk is real.",{"id":125,"name":126,"type":85,"typeVersion":16,"position":127,"parameters":128,"category":91,"deletable":8,"connectable":8},"node_if_4","If: compare branches",[87,44],{"buttonId":74,"operator":90},{"id":130,"name":131,"type":95,"typeVersion":16,"position":132,"parameters":133,"category":50,"deletable":8,"connectable":8},"node_msg_compare","Checklist: compare branches & attribution",[97,44],{"text":134},"Branch comparisons fail in the same boring ways (which is great—because you can catch them fast):\n\n1) **Same opportunity set?** If branches have different foot traffic, eligibility, or hours, raw totals are a trap.\n2) **Same measurement?** Check staffing coverage for logging, missed calls, and system adoption.\n3) **Same mix?** Product mix, customer type, and seasonality can dominate “performance.”\n4) **Attribution honesty:** If you can’t explain the attribution model in one sentence, don’t use it to rank branches.\n5) **One fairness metric:** Pick a normalized metric (per eligible customer, per staff-hour) and a “hard” outcome metric. Use both.\n\nIf you tell me what you’re comparing (e.g., leads, revenue, appointments, conversions), I can suggest the least-misleading normalization.",{"id":136,"name":137,"type":85,"typeVersion":16,"position":138,"parameters":140,"category":91,"deletable":8,"connectable":8},"node_if_5","If: signal culture",[87,139],560,{"buttonId":77,"operator":90},{"id":142,"name":143,"type":95,"typeVersion":16,"position":144,"parameters":145,"category":50,"deletable":8,"connectable":8},"node_msg_culture","Playbook: build signal culture (no more slide theater)",[97,139],{"text":146},"Signal culture that actually helps decisions happen (not just slides):\n\n- **One owner per metric:** Not “the team.” A name. If no owner, it’s a rumor with a chart.\n- **Write the definition next to the number:** If the definition is missing, the debate will fill the vacuum.\n- **Default to ranges, not false precision:** “$98,432” is often cosplay. Use a range when uncertainty is real.\n- **Track revisions:** If numbers change after the fact, show the revision rate. It’s a trust metric.\n- **Decision log:** Every key metric should be tied to a decision it informs. No decision, no dashboard.\n\nSmall move with big impact: add a 60-second ‘How could this be wrong?’ round to every review.",{"id":148,"name":149,"type":85,"typeVersion":16,"position":150,"parameters":152,"category":91,"deletable":8,"connectable":8},"node_if_6","If: handoff to analyst",[87,151],660,{"buttonId":80,"operator":90},{"id":154,"name":155,"type":156,"typeVersion":16,"position":157,"parameters":158,"category":162,"deletable":8,"connectable":32},"node_fallback_analytics","Handoff: Business Analytics","fallback",[97,151],{"handoffMessage":159,"departmentId":160,"departmentName":161},"Looping in Business Analytics. Please share: (1) the metric(s), (2) timeframe, (3) which branches, and (4) the decision you’re about to make. If there’s a screenshot/table, include it.","dept_business_analytics","Business Analytics","terminal",{"id":164,"name":165,"type":156,"typeVersion":16,"position":166,"parameters":168,"category":162,"deletable":8,"connectable":32},"node_fallback_default","Default handoff (unmatched selection)",[97,167],780,{"handoffMessage":169,"departmentId":160,"departmentName":161},"I couldn’t match that selection cleanly—handing you to Business Analytics so you’re not stuck. Please share the metric and the decision you’re making.",[171,175,177,179,182,185,187,189,191,193,195,197,199,201,203],{"id":172,"source":34,"target":40,"sourceHandle":173,"targetHandle":174,"type":46},"conn_input_to_kb","out","in",{"id":176,"source":40,"target":52,"sourceHandle":173,"targetHandle":174,"type":46},"conn_kb_to_menu",{"id":178,"source":52,"target":83,"sourceHandle":173,"targetHandle":174,"type":46},"conn_menu_to_if1",{"id":180,"source":83,"target":93,"sourceHandle":181,"targetHandle":174,"type":46},"conn_if1_true_to_msg","true",{"id":183,"source":83,"target":101,"sourceHandle":184,"targetHandle":174,"type":46},"conn_if1_false_to_if2","false",{"id":186,"source":101,"target":107,"sourceHandle":181,"targetHandle":174,"type":46},"conn_if2_true_to_msg",{"id":188,"source":101,"target":113,"sourceHandle":184,"targetHandle":174,"type":46},"conn_if2_false_to_if3",{"id":190,"source":113,"target":119,"sourceHandle":181,"targetHandle":174,"type":46},"conn_if3_true_to_msg",{"id":192,"source":113,"target":125,"sourceHandle":184,"targetHandle":174,"type":46},"conn_if3_false_to_if4",{"id":194,"source":125,"target":130,"sourceHandle":181,"targetHandle":174,"type":46},"conn_if4_true_to_msg",{"id":196,"source":125,"target":136,"sourceHandle":184,"targetHandle":174,"type":46},"conn_if4_false_to_if5",{"id":198,"source":136,"target":142,"sourceHandle":181,"targetHandle":174,"type":46},"conn_if5_true_to_msg",{"id":200,"source":136,"target":148,"sourceHandle":184,"targetHandle":174,"type":46},"conn_if5_false_to_if6",{"id":202,"source":148,"target":154,"sourceHandle":181,"targetHandle":174,"type":46},"conn_if6_true_to_handoff",{"id":204,"source":148,"target":164,"sourceHandle":184,"targetHandle":174,"type":46},"conn_if6_false_to_default_handoff","automation",[27,28,29,207,208],"data-hygiene","automation-guardrails",[210],"Calypso Chat","intermediate","Calypso","2026-05-30T11:03:15.316Z","/en/workflows/branch-signal-readiness-navigator",{"en":214},{"title":9,"description":217,"ogDescription":218,"twitterDescription":219,"canonicalPath":214,"robots":220,"schemaType":221,"alternates":222},"Guide branch leaders to trust the right numbers, spot dirty signals, and escalate risky decisions to human review—before meetings go off track.","A practical decision navigator for branch metrics: detect polished noise, sanity check attribution, and know when automation is safe vs. when humans must review.","Stop clean looking wrong data. Route leaders through signal checks, branch comparisons, and automation guardrails—with an easy handoff for high risk calls.","index,follow","HowTo",[223],{"hreflang":6,"href":214},1780761213063]