[{"data":1,"prerenderedAt":247},["ShallowReactive",2],{"/en/workflows/decision-signal-reality-guide":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":226,"tags":227,"integrations":231,"difficulty":234,"author":235,"verified":33,"featured":33,"date":236,"modified":236,"icon":7,"imageSrc":7,"path":237,"alternates":238,"seo":239},"4ca56d49-ca6c-479d-be2d-2523b73bbd5d","decision-signal-reality-guide","en",null,true,"Decision Signal Reality Guide","A guided menu that helps leaders pressure-test branch numbers, spot dirty signals, and decide when automation is safe vs when human judgment should take the wheel.","## How it works\nThis workflow turns “we have data” into “we have a decision we can defend.” It starts with a knowledge-backed helper that can answer plain-English questions, then offers a short menu of decision-shaped prompts that stress-test branch numbers, conversation signals, and attribution claims.\n\nIt’s designed for the moment right before a confident meeting goes off the rails: when the dashboard looks clean, the story sounds plausible, and the underlying signal is quietly rotten. Operators can use it to coach leaders toward safer conclusions—without turning the conversation into an academic lecture.\n\n## Key features\n- Knowledge-base-first responses, then a guided menu for consistent decision coaching\n- Button-driven routing to targeted “reality check” playbooks (trust, hygiene, automation, attribution, culture)\n- Practical prompts that surface what usually breaks first (definitions, selection bias, lagging signals)\n- Human handoff option when the situation is sensitive or politically loaded\n- Re-prompt loop if a user sends an unexpected reply instead of choosing a menu option\n\n## Step-by-step\n1. **Input**: The workflow starts when a message arrives.\n2. **Knowledge Base Policy**: Calypso answers using your knowledge base when possible, and stays ready to route into the guided menu.\n3. **Decision menu (buttons)**: The user chooses what they need:\n   - *Which numbers deserve trust?*\n   - *Spot dirty signal before the meeting*\n   - *Automation vs human judgment*\n   - *Messy evidence → usable insight*\n   - *Comparing branches & attribution traps*\n   - *Build a signal culture (not just slides)*\n   - *Talk to a human*\n4. **Routing (IF checks)**: Calypso matches the selected button and sends the corresponding coaching message.\n5. **Human handoff (optional)**: If the user selects *Talk to a human*, the workflow hands off to a designated team.\n6. **Retry path**: If the reply doesn’t match a button selection, Calypso asks the user to pick an option and shows the menu again.\n\n## Setup requirements\n- No credentials required.\n- (Recommended) Connect this workflow to a Calypso Inbox or Web chat channel where leaders/operators ask decision-quality questions.\n- (Optional) Populate your Calypso knowledge base with your branch metric definitions, source-of-truth systems, and attribution rules so the Knowledge Base step can answer precisely.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":186,"routingEnabled":8,"active":33},"wf-decision-signal-reality-guide","calypso-public-library","1.0.0",1,[18,34,39,51,86,95,104,110,116,122,128,134,140,146,152,158,164,170,180],{"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],-200,0,{"name":9,"description":26,"tags":27,"triggerType":31},"Knowledge-base-first coaching menu to pressure-test branch metrics, spot dirty signal, and decide when to trust automation vs human judgment.",[28,29,30],"decision-systems","signal-quality","branch-metrics","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":38,"category":31,"deletable":33,"connectable":8},"node-input","Incoming message",[24,24],{},{"id":40,"name":41,"type":42,"typeVersion":16,"position":43,"parameters":45,"category":50,"deletable":8,"connectable":8},"node-kb-policy","Knowledge base helper","knowledge-base-policy",[44,24],220,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":46,"activationOpener":47,"personalization":49},"default",{"enabled":8,"instruction":48},"Answer plainly and practically. If the user is asking for a decision, steer toward the menu to run quick reality checks. Prefer concrete prompts over theory.",{"useContactName":33},"response",{"id":52,"name":53,"type":54,"typeVersion":16,"position":55,"parameters":57,"category":50,"deletable":8,"connectable":8},"node-menu","Decision check menu","interactive-message",[56,24],460,{"messageType":58,"headerText":59,"bodyText":60,"footerText":61,"sectionTitle":62,"buttons":63,"ctaDisplayText":85,"ctaUrl":85},"button","Make the signal earn your trust","Pick the decision check you need. (Clean charts can still be lying—usually by omission.)","Tip: Choose one path; you can run another check afterward.","Decision checks",[64,67,70,73,76,79,82],{"id":65,"title":66},"trust_numbers","Trust the numbers",{"id":68,"title":69},"dirty_signal","Spot dirty signal",{"id":71,"title":72},"automation_vs_human","Auto vs human",{"id":74,"title":75},"messy_evidence","Messy to insight",{"id":77,"title":78},"compare_branches","Compare branches",{"id":80,"title":81},"signal_culture","Signal culture",{"id":83,"title":84},"handoff_human","Talk to a human","",{"id":87,"name":88,"type":89,"typeVersion":16,"position":90,"parameters":92,"category":94,"deletable":8,"connectable":8},"node-if-trust","If: trust_numbers","if",[91,24],700,{"buttonId":65,"operator":93},"equals","routing",{"id":96,"name":97,"type":98,"typeVersion":16,"position":99,"parameters":102,"category":50,"deletable":8,"connectable":8},"node-txt-trust","Trustworthy numbers checklist","text-message",[100,101],940,-120,{"text":103},"Here’s how to tell a trustworthy branch number from polished noise:\n\n1) **Definition survives a hostile reading.** Ask: “What *exactly* counts—and what’s excluded?” If two people answer differently, the metric isn’t ready.\n2) **Denominator is stable.** Branch totals often ‘improve’ because the pool shrank or changed (hours, staffing, lead mix). Always check the base.\n3) **Timestamp matches the decision.** If the metric lags the decision window, it will look calm right before it breaks.\n4) **The ‘why’ can be falsified.** A good story names what would prove it wrong (e.g., ‘If callbacks didn’t rise, this wasn’t service quality’).\n5) **One boring source of truth.** When a number needs three exports and a prayer, treat it as a hypothesis.\n\nIf you tell me the metric and the decision it’s being used for, I’ll suggest the 2–3 quickest stress tests.",{"id":105,"name":106,"type":89,"typeVersion":16,"position":107,"parameters":109,"category":94,"deletable":8,"connectable":8},"node-if-dirty","If: dirty_signal",[91,108],120,{"buttonId":68,"operator":93},{"id":111,"name":112,"type":98,"typeVersion":16,"position":113,"parameters":114,"category":50,"deletable":8,"connectable":8},"node-txt-dirty","Dirty signal early warnings",[100,24],{"text":115},"Dirty signal usually looks *reasonable*—that’s the danger. Quick tells before the meeting:\n\n- **Sudden smoothness.** If variance disappears overnight, something got filtered, capped, deduped, or redefined.\n- **Perfect alignment across branches.** Real operations are messy. Too much uniformity often means a shared logging/default issue.\n- **Great outcome, no intermediate movement.** If ‘conversion’ improved but nothing upstream budged (contacts, quotes, follow-ups), suspect attribution or counting.\n- **Changes that coincide with tooling/process shifts.** New scripts, new tags, new dashboards: assume measurement drift until proven otherwise.\n\nTwo meeting-saving questions:\n1) “What would we see if this were a tracking bug?”\n2) “What’s the simplest operational explanation that doesn’t require a miracle?”",{"id":117,"name":118,"type":89,"typeVersion":16,"position":119,"parameters":121,"category":94,"deletable":8,"connectable":8},"node-if-auto","If: automation_vs_human",[91,120],240,{"buttonId":71,"operator":93},{"id":123,"name":124,"type":98,"typeVersion":16,"position":125,"parameters":126,"category":50,"deletable":8,"connectable":8},"node-txt-auto","Automation vs judgment guidance",[100,108],{"text":127},"When to trust automation (and when to keep a human in the loop):\n\n**Let automation decide** when:\n- The cost of being wrong is low and reversible.\n- The inputs are well-defined and routinely audited.\n- The system has seen enough similar cases (no novelty).\n- You can monitor failures quickly (tight feedback loop).\n\n**Keep human judgment** when:\n- The decision is one-way (policy, staffing, branch closures).\n- The data can be gamed (incentives, tags, self-reported fields).\n- Edge cases matter (high-value customers, compliance, safety).\n- You *can’t* explain the decision in one paragraph to the people affected.\n\nRule of thumb: automate the **sorting**, not the **meaning**—until your signal earns the right to drive consequences.",{"id":129,"name":130,"type":89,"typeVersion":16,"position":131,"parameters":133,"category":94,"deletable":8,"connectable":8},"node-if-messy","If: messy_evidence",[91,132],360,{"buttonId":74,"operator":93},{"id":135,"name":136,"type":98,"typeVersion":16,"position":137,"parameters":138,"category":50,"deletable":8,"connectable":8},"node-txt-messy","Messy evidence to usable insight",[100,120],{"text":139},"Don’t ‘clean’ away the truth. Make mess useful without making it fake:\n\n1) **Separate unknown from zero.** Most bad decisions start when missing becomes ‘none.’\n2) **Preserve the raw story.** Keep a raw view alongside the curated view so you can audit what got dropped.\n3) **Use tiers, not a single number.** Example: confirmed / likely / speculative. Leaders can decide how much uncertainty they’ll pay for.\n4) **Track the reason codes for exclusions.** If you exclude 12% of records, you need to know *why*—and whether it’s clustered by branch.\n\nIf you share what evidence you have (calls, chats, forms, footfall, etc.), I’ll suggest a simple tiering scheme that keeps the signal honest.",{"id":141,"name":142,"type":89,"typeVersion":16,"position":143,"parameters":145,"category":94,"deletable":8,"connectable":8},"node-if-compare","If: compare_branches",[91,144],480,{"buttonId":77,"operator":93},{"id":147,"name":148,"type":98,"typeVersion":16,"position":149,"parameters":150,"category":50,"deletable":8,"connectable":8},"node-txt-compare","Branch comparison & attribution traps",[100,132],{"text":151},"Branch comparisons go wrong in the same predictable ways:\n\n- **Mix shift pretending to be performance.** Different lead sources, product mix, seasonality, staffing experience.\n- **Capacity constraints masked as demand.** A busy branch can look ‘worse’ because it can’t respond fast enough.\n- **Attribution that rewards the last touch.** The branch that closes gets credit; the branch that did the hard early work gets forgotten.\n- **Small numbers, loud confidence.** A few wins/losses swing rates wildly; show counts, not just percentages.\n\nSafer comparison moves:\n1) Compare **like-with-like cohorts** (same lead type/time window).\n2) Look at a **chain of signals** (contact → appointment → show → close), not one headline metric.\n3) If comp drives incentives, assume **gaming pressure** and audit tags/notes.",{"id":153,"name":154,"type":89,"typeVersion":16,"position":155,"parameters":157,"category":94,"deletable":8,"connectable":8},"node-if-culture","If: signal_culture",[91,156],600,{"buttonId":80,"operator":93},{"id":159,"name":160,"type":98,"typeVersion":16,"position":161,"parameters":162,"category":50,"deletable":8,"connectable":8},"node-txt-culture","Build a signal culture",[100,144],{"text":163},"A healthy signal culture helps decisions happen—not just slides.\n\nWhat works in practice:\n- **One owner per metric, one sentence definition.** If it can’t fit in one sentence, it’s not operational.\n- **A ‘disconfirming evidence’ habit.** In reviews, require one chart or anecdote that could prove the main story wrong.\n- **Make uncertainty speakable.** Reward ‘we don’t know yet’ when it’s paired with the next best test.\n- **Default to decision memos, not dashboards.** Dashboards inform; memos commit: *what we’ll do, what we’ll watch, what would change our mind.*\n\nIf you tell me the decision cadence (weekly ops, monthly performance, quarterly planning), I’ll suggest a lightweight signal review ritual that won’t metastasize into bureaucracy.",{"id":165,"name":166,"type":89,"typeVersion":16,"position":167,"parameters":169,"category":94,"deletable":8,"connectable":8},"node-if-handoff","If: handoff_human",[91,168],720,{"buttonId":83,"operator":93},{"id":171,"name":172,"type":173,"typeVersion":16,"position":174,"parameters":175,"category":179,"deletable":8,"connectable":8},"node-fallback","Handoff to decision support","fallback",[100,156],{"handoffMessage":176,"departmentId":177,"departmentName":178},"Got it—looping in a human. Share the metric/dashboard link, the decision being made, and what would be most costly to get wrong.","decision-support","Decision Support","terminal",{"id":181,"name":182,"type":98,"typeVersion":16,"position":183,"parameters":184,"category":50,"deletable":8,"connectable":8},"node-txt-retry","Retry: choose a menu option",[100,168],{"text":185},"I can help—please choose one option from the buttons so I route you to the right reality check.\n\nIf you don’t see the buttons, send another message and I’ll show the menu again. If this is sensitive, choose **Talk to a human** and include the decision + the metric in question.",[187,192,194,196,199,202,204,206,208,210,212,214,216,218,220,222,224],{"id":188,"source":35,"target":40,"sourceHandle":189,"targetHandle":190,"type":191},"conn-input-kb","out","in","smoothstep",{"id":193,"source":40,"target":52,"sourceHandle":189,"targetHandle":190,"type":191},"conn-kb-menu",{"id":195,"source":52,"target":87,"sourceHandle":189,"targetHandle":190,"type":191},"conn-menu-if-trust",{"id":197,"source":87,"target":96,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-trust-true","true",{"id":200,"source":87,"target":105,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-trust-false","false",{"id":203,"source":105,"target":111,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-dirty-true",{"id":205,"source":105,"target":117,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-dirty-false",{"id":207,"source":117,"target":123,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-auto-true",{"id":209,"source":117,"target":129,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-auto-false",{"id":211,"source":129,"target":135,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-messy-true",{"id":213,"source":129,"target":141,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-messy-false",{"id":215,"source":141,"target":147,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-compare-true",{"id":217,"source":141,"target":153,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-compare-false",{"id":219,"source":153,"target":159,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-culture-true",{"id":221,"source":153,"target":165,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-culture-false",{"id":223,"source":165,"target":171,"sourceHandle":198,"targetHandle":190,"type":191},"conn-if-handoff-true",{"id":225,"source":165,"target":181,"sourceHandle":201,"targetHandle":190,"type":191},"conn-if-handoff-false","automation",[28,29,30,228,229,230],"dirty-data","attribution","leadership-ops",[232,233],"Calypso Inbox","Web chat","intermediate","Calypso","2026-05-10T11:03:37.942Z","/en/workflows/decision-signal-reality-guide",{"en":237},{"title":9,"description":240,"ogDescription":241,"twitterDescription":242,"canonicalPath":237,"robots":243,"schemaType":244,"alternates":245},"Guide leaders to trust the right branch numbers, spot dirty signals, and choose automation vs judgment using a menu driven decision workflow.","Turn messy branch signals into defensible decisions: trust checks, dirty signal spotting, automation vs judgment prompts, attribution traps, and a human handoff.","A practical workflow to pressure test branch metrics, spot dirty signal early, and choose when automation is safe vs when humans must decide.","index,follow","HowTo",[246],{"hreflang":6,"href":237},1778614429913]