[{"data":1,"prerenderedAt":293},["ShallowReactive",2],{"/en/workflows/branch-signal-reality-checks-decision-prompts":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":274,"tags":275,"integrations":279,"difficulty":280,"author":281,"verified":33,"featured":33,"date":282,"modified":282,"icon":7,"imageSrc":7,"path":283,"alternates":284,"seo":285},"0fb27888-cf8a-4832-8c1b-6bb1450bb445","branch-signal-reality-checks-decision-prompts","en",null,true,"Branch Signal Reality Checks & Decision Prompts","A guided decision-support flow that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and choose when to lean on automation versus human judgment.","## How it works\nThis workflow is a fast, operator-friendly “signal coach” you can run inside Calypso conversations. It turns the vague, messy stuff—branch numbers, call notes, attribution debates, and “we all feel it’s working” energy—into concrete checks you can use before a confident meeting makes a confidently wrong decision.\n\nIt starts with a knowledge-base guided mode (so answers stay consistent with your internal definitions), then routes users through decision-shaped prompts: what to trust, how to spot dirty signal, when automation is safe, and what teams routinely misread when comparing branches and channels.\n\n## Key features\n- Knowledge-base guided answers first, then structured routing for consistent guidance\n- A menu of practical “reality checks” tied to common branch decision moments\n- Built-in dirty-signal detection prompts to catch problems before leadership meetings\n- Clear guidance on when automation is reliable and when judgment should override\n- Optional human handoff path for edge cases and contentious debates\n\n## Step-by-step\n1. **Trigger:** The workflow starts when a conversation hits the **Input** node.\n2. **Knowledge base guidance:** **Signal Coach (KB mode)** activates to keep terminology and definitions aligned.\n3. **Choose a decision prompt:** Users get **Signal menu: pick a reality check** with common options (trust, dirty signal, automation vs judgment, messy evidence, comparisons, culture).\n4. **Routing:** The workflow routes based on the selected button and sends a tailored **text checklist** for that scenario.\n5. **Next action:** After the checklist, **Next step** offers two buttons: go back to the menu or request a human handoff.\n6. **Handoff (optional):** If requested, the workflow sends the configured handoff message and routes to the **Insights & Ops** department.\n\n## Setup requirements\n- No external credentials required.\n- (Optional) Populate your Calypso knowledge base with your definitions for branch KPIs, attribution rules, and “source of truth” systems so the KB-guided node stays consistent with your operating model.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":219,"routingEnabled":8,"active":33},"wf_branch_signal_reality_checks_v1","calypso-public-library","1.0.0",1,[18,34,40,52,83,93,98,104,110,116,122,130,136,142,148,154,160,176,183,189,196,203,213],{"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},"Guided menu that turns messy branch signals into decision-ready checks (trust vs noise, dirty signal detection, automation vs judgment).",[28,29,30],"signal-quality","decision-support","branch-analytics","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":39,"category":31,"deletable":33,"connectable":8},"node_input","Input",[23,38],220,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node_kb_policy","Signal Coach (KB mode)","knowledge-base-policy",[45,38],120,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"You’re in Signal Coach mode. Keep answers practical and decision-shaped. Prefer quick checks, definitions, and what usually goes wrong first. Avoid academic framing. If the user’s question is ambiguous, ask one clarifying question, then provide a checklist.",{"useContactName":8},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_main_menu","Signal menu: pick a reality check","interactive-message",[57,38],360,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Signal reality checks","Pick what you’re deciding. I’ll give you a quick checklist to separate trustworthy signal from polished noise.","If a number looks perfect, ask how it was made.","",[65,68,71,74,77,80],{"id":66,"title":67},"trust_branch_numbers","Trust branch KPIs",{"id":69,"title":70},"spot_dirty_signal","Spot dirty signal",{"id":72,"title":73},"automation_vs_judgment","Automation vs human",{"id":75,"title":76},"messy_evidence_insight","Messy → insight",{"id":78,"title":79},"compare_branches_attribution","Compare & attribute",{"id":81,"title":82},"build_signal_culture","Build signal culture",{"id":84,"name":85,"type":86,"typeVersion":16,"position":87,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_trust","If: trust_branch_numbers","if",[88,89],620,140,{"buttonId":66,"operator":91},"equals","routing",{"id":94,"name":95,"type":86,"typeVersion":16,"position":96,"parameters":97,"category":92,"deletable":8,"connectable":8},"node_if_dirty","If: spot_dirty_signal",[88,38],{"buttonId":69,"operator":91},{"id":99,"name":100,"type":86,"typeVersion":16,"position":101,"parameters":103,"category":92,"deletable":8,"connectable":8},"node_if_auto","If: automation_vs_judgment",[88,102],300,{"buttonId":72,"operator":91},{"id":105,"name":106,"type":86,"typeVersion":16,"position":107,"parameters":109,"category":92,"deletable":8,"connectable":8},"node_if_messy","If: messy_evidence_insight",[88,108],380,{"buttonId":75,"operator":91},{"id":111,"name":112,"type":86,"typeVersion":16,"position":113,"parameters":115,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: compare_branches_attribution",[88,114],460,{"buttonId":78,"operator":91},{"id":117,"name":118,"type":86,"typeVersion":16,"position":119,"parameters":121,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: build_signal_culture",[88,120],540,{"buttonId":81,"operator":91},{"id":123,"name":124,"type":125,"typeVersion":16,"position":126,"parameters":128,"category":51,"deletable":8,"connectable":8},"node_msg_trust","Checklist: numbers you can trust","text-message",[127,89],900,{"text":129},"**Which branch numbers deserve trust (and which are polished noise)**\n\nUse this quick trust test before you repeat a KPI in a meeting:\n\n1) **Lineage:** Can you name the system-of-record in one sentence? If it’s “a sheet fed by exports,” treat it as *draft*.\n2) **Definition stability:** Has the metric definition changed in the last 30 days? If yes, trend comparisons are mostly theater.\n3) **Denominator check:** What’s the denominator doing? A ‘conversion jump’ with a shrinking denominator is often a mirage.\n4) **Lag & backfill:** Does the number settle over time? If it backfills, today’s ‘win’ may be next week’s correction.\n5) **Incentive pressure:** If a branch is rewarded on it, assume it will be gamed—usually unintentionally at first.\n\nRule of thumb: **trust boring numbers with boring plumbing**. The flashy ones need a chaperone.",{"id":131,"name":132,"type":125,"typeVersion":16,"position":133,"parameters":134,"category":51,"deletable":8,"connectable":8},"node_msg_dirty","Checklist: spot dirty signal",[127,38],{"text":135},"**How to spot dirty signal before the confident meeting**\n\nDirty data rarely looks dirty. It looks *clean and decisive*. Watch for these tells:\n\n- **Too smooth:** A chart with no noise in a noisy world often means over-filtering or missing data.\n- **Perfect alignment:** Every branch ‘improves’ at the same time after a policy change? That’s often instrumentation, not performance.\n- **One-field miracles:** A single field (lead source, outcome code) explains everything. That field is probably being overused.\n- **Sudden precision:** Someone starts quoting to two decimals. That’s a confidence costume.\n\nFast fix: ask for **3 raw examples** (calls, forms, events) behind the metric. If reality doesn’t match the dashboard story, pause the decision—not the questions.",{"id":137,"name":138,"type":125,"typeVersion":16,"position":139,"parameters":140,"category":51,"deletable":8,"connectable":8},"node_msg_auto","Checklist: automation vs judgment",[127,102],{"text":141},"**When to trust automation (and when you still need humans)**\n\nTrust automation when:\n- The decision is **reversible** (you can roll back without reputational or customer damage).\n- The input signals are **well-instrumented** and stable (definitions don’t change weekly).\n- The failure mode is **obvious** (you’ll notice quickly when it’s wrong).\n\nRequire human judgment when:\n- The decision is **high-stakes** or one-way (pricing, staffing cuts, compliance).\n- The signal can be **gamed** by normal behavior (branch incentives, attribution rules).\n- The model is fed by **proxies** (e.g., “interest” inferred from weak events).\n\nPractical policy: automate the **recommendation**, not the **commitment**. Humans should own the exceptions—because that’s where the money leaks.",{"id":143,"name":144,"type":125,"typeVersion":16,"position":145,"parameters":146,"category":51,"deletable":8,"connectable":8},"node_msg_messy","Checklist: messy evidence to insight",[127,108],{"text":147},"**Turning messy evidence into usable insight (without cleaning away the truth)**\n\nThe goal isn’t ‘clean data.’ It’s **honest data you can decide with**. Try this sequence:\n\n1) **Keep the mess in view:** Don’t delete outliers first—label them. Outliers often are the story.\n2) **Segment before you average:** Branch, channel, time-of-day, new vs repeat. Averages hide the knife.\n3) **Write a decision question:** ‘Should we expand X to 10 branches next month?’ beats ‘How are we doing?’\n4) **Use a minimum evidence bar:** e.g., “We need 30+ cases and stable tracking for 2 weeks.”\n5) **Preserve context:** Store 5–10 annotated examples (calls, notes). Numbers without examples breed fiction.\n\nIf you can’t explain the insight with one concrete example, you probably don’t have insight yet—just formatting.",{"id":149,"name":150,"type":125,"typeVersion":16,"position":151,"parameters":152,"category":51,"deletable":8,"connectable":8},"node_msg_compare","Checklist: comparing branches & attribution",[127,114],{"text":153},"**What teams misread when comparing branches, conversations, and attribution**\n\nComparisons fail in predictable ways. Check these before declaring winners/losers:\n\n- **Mix shift:** Branch A isn’t ‘better’—it just got easier customers this month. Control for customer mix where possible.\n- **Capacity & constraints:** A high conversion rate with low volume can be a capacity ceiling, not excellence.\n- **Conversation coding drift:** If disposition/outcome codes aren’t audited, branches ‘improve’ by relabeling.\n- **Attribution gravity:** The channel that gets logged last often gets the credit. That’s not truth; it’s bookkeeping.\n\nBetter practice: compare **within branch over time** first, then across branches only after you confirm definitions and logging behavior are consistent.",{"id":155,"name":156,"type":125,"typeVersion":16,"position":157,"parameters":158,"category":51,"deletable":8,"connectable":8},"node_msg_culture","Checklist: build a signal culture",[127,120],{"text":159},"**Build a signal culture that helps decisions happen (not just slides)**\n\nCulture is what people do when the dashboard disagrees with their favorite story. A few habits that work:\n\n- **One metric, one owner, one definition.** Ambiguity is a tax you pay forever.\n- **Decision logs:** Record the decision, the signals used, and what you expected. Review later. This is how teams get smarter.\n- **Red-team the signal:** Assign someone to ask “How could this be wrong?” in five minutes. Cheap insurance.\n- **Examples over slogans:** Require 3 real cases behind any key chart.\n- **Reward truth-telling:** If people get punished for bad news, you’ll only get good-looking noise.\n\nWit-sized reminder: a metric is a *measurement*, not a verdict. Treat it like a witness—useful, fallible, and occasionally dramatic.",{"id":161,"name":162,"type":55,"typeVersion":16,"position":163,"parameters":166,"category":51,"deletable":8,"connectable":8},"node_next_menu","Next step",[164,165],1160,340,{"messageType":59,"headerText":167,"bodyText":168,"footerText":63,"sectionTitle":63,"buttons":169,"ctaDisplayText":63,"ctaUrl":63},"What now?","Finish here, or should I route this to a person?",[170,173],{"id":171,"title":172},"finish","Finish",{"id":174,"title":175},"request_handoff","Route to a human",{"id":177,"name":178,"type":86,"typeVersion":16,"position":179,"parameters":182,"category":92,"deletable":8,"connectable":8},"node_if_back","If: finish",[180,181],1410,320,{"buttonId":171,"operator":91},{"id":184,"name":185,"type":86,"typeVersion":16,"position":186,"parameters":188,"category":92,"deletable":8,"connectable":8},"node_if_handoff","If: request_handoff",[180,187],400,{"buttonId":174,"operator":91},{"id":190,"name":191,"type":125,"typeVersion":16,"position":192,"parameters":194,"category":51,"deletable":8,"connectable":8},"node_done","Message: done",[193,181],1660,{"text":195},"Done. If you need another reality check, start a new run from the workflow entry (Input) and pick a new topic from the menu.",{"id":197,"name":198,"type":125,"typeVersion":16,"position":199,"parameters":201,"category":51,"deletable":8,"connectable":8},"node_unknown_next","Message: choose a button",[193,200],480,{"text":202},"I didn’t catch that—please use one of the buttons so I route you correctly.",{"id":204,"name":205,"type":206,"typeVersion":16,"position":207,"parameters":208,"category":212,"deletable":8,"connectable":8},"node_handoff","Handoff: Insights & Ops","fallback",[193,187],{"handoffMessage":209,"departmentId":210,"departmentName":211},"Got it. I’m routing this to **Insights & Ops**. Please share: (1) the decision you’re trying to make, (2) the metric(s) in question, and (3) 2–3 raw examples behind the number.","insights_ops","Insights & Ops","terminal",{"id":214,"name":215,"type":125,"typeVersion":16,"position":216,"parameters":217,"category":51,"deletable":8,"connectable":8},"node_unknown_main","Message: re-open menu",[127,88],{"text":218},"I didn’t recognize that selection. Please use one of the menu buttons so I can route you to the right checklist.",[220,222,224,226,229,232,234,236,238,240,242,244,246,248,250,252,254,256,258,260,262,264,266,268,270,272],{"id":221,"source":35,"target":41,"sourceHandle":47,"targetHandle":47,"type":47},"conn_input_to_kb",{"id":223,"source":41,"target":53,"sourceHandle":47,"targetHandle":47,"type":47},"conn_kb_to_menu",{"id":225,"source":53,"target":84,"sourceHandle":47,"targetHandle":47,"type":47},"conn_menu_to_if_trust",{"id":227,"source":84,"target":123,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_trust_true_to_msg","true",{"id":230,"source":84,"target":94,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_trust_false_to_if_dirty","false",{"id":233,"source":94,"target":131,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_dirty_true_to_msg",{"id":235,"source":94,"target":99,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_dirty_false_to_if_auto",{"id":237,"source":99,"target":137,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_auto_true_to_msg",{"id":239,"source":99,"target":105,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_auto_false_to_if_messy",{"id":241,"source":105,"target":143,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_messy_true_to_msg",{"id":243,"source":105,"target":111,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_messy_false_to_if_compare",{"id":245,"source":111,"target":149,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_compare_true_to_msg",{"id":247,"source":111,"target":117,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_compare_false_to_if_culture",{"id":249,"source":117,"target":155,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_culture_true_to_msg",{"id":251,"source":117,"target":214,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_culture_false_to_unknown_main",{"id":253,"source":123,"target":161,"sourceHandle":47,"targetHandle":47,"type":47},"conn_msg_trust_to_next",{"id":255,"source":131,"target":161,"sourceHandle":47,"targetHandle":47,"type":47},"conn_msg_dirty_to_next",{"id":257,"source":137,"target":161,"sourceHandle":47,"targetHandle":47,"type":47},"conn_msg_auto_to_next",{"id":259,"source":143,"target":161,"sourceHandle":47,"targetHandle":47,"type":47},"conn_msg_messy_to_next",{"id":261,"source":149,"target":161,"sourceHandle":47,"targetHandle":47,"type":47},"conn_msg_compare_to_next",{"id":263,"source":155,"target":161,"sourceHandle":47,"targetHandle":47,"type":47},"conn_msg_culture_to_next",{"id":265,"source":161,"target":177,"sourceHandle":47,"targetHandle":47,"type":47},"conn_next_to_if_back",{"id":267,"source":177,"target":190,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_back_true_to_done",{"id":269,"source":177,"target":184,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_back_false_to_if_handoff",{"id":271,"source":184,"target":204,"sourceHandle":228,"targetHandle":47,"type":47},"conn_if_handoff_true_to_fallback",{"id":273,"source":184,"target":197,"sourceHandle":231,"targetHandle":47,"type":47},"conn_if_handoff_false_to_unknown_next","automation",[28,29,30,276,277,278],"attribution","research-practice","data-hygiene",[],"intermediate","Calypso","2026-04-19T11:03:03.313Z","/en/workflows/branch-signal-reality-checks-decision-prompts",{"en":283},{"title":9,"description":286,"ogDescription":287,"twitterDescription":288,"canonicalPath":283,"robots":289,"schemaType":290,"alternates":291},"Guide teams to trust the right branch numbers, spot dirty signals early, and choose when automation vs judgment should decide.","A practical signal coach for branch teams: reality checks for KPI trust, dirty data detection, attribution comparisons, and when humans should override automation.","Turn messy branch signals into decision ready checks: what to trust, what’s noise, dirty signal tells, and when to rely on automation vs judgment.","index,follow","HowTo",[292],{"hreflang":6,"href":283},1776877119137]