[{"data":1,"prerenderedAt":248},["ShallowReactive",2],{"/en/workflows/meeting-proof-decision-signals":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":228,"tags":229,"integrations":232,"difficulty":234,"author":235,"verified":34,"featured":34,"date":236,"modified":236,"icon":7,"imageSrc":7,"path":237,"alternates":238,"seo":239},"d3091199-7bd2-4514-8cdc-ef5010beeb2f","meeting-proof-decision-signals","en",null,true,"Meeting-Proof Decision Signals","Guide operators through quick signal triage: trust checks for branch numbers, dirty-signal spotting, automation vs judgment, and decision-ready summaries—with a clean human handoff when needed.","## How it works\nThis workflow turns messy branch metrics, conversation notes, and attribution “facts” into decision-shaped guidance—fast. It starts by attempting a Knowledge Base answer (so repeat questions get consistent answers), then routes people through a set of practical checks when the situation is nuanced or the data looks suspiciously clean.\n\nIt’s designed for the moment right before a confident meeting goes off the rails: you get a short menu of common decision traps (trusting the wrong branch numbers, dirty signals, over-trusting automation, misreading comparisons), and each path returns a tight playbook you can act on immediately.\n\n## Key features\n- Knowledge Base-first responses for consistency on repeat questions\n- Button-driven routing into decision-shaped signal checks (no free-form wandering)\n- Dirty-signal prompts that flag what breaks first (definitions, denominators, timing, incentives)\n- Clear guidance on when to trust automation vs when to require human review\n- Built-in human handoff path for contentious or high-stakes calls\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow.\n2. **Knowledge Base policy:** Calypso attempts to answer using your Knowledge Base. If it can’t, the workflow continues to routing.\n3. **Decision menu:** The user picks what they need help with:\n   - Trusting branch numbers vs polished noise\n   - Spotting dirty signal before the meeting\n   - Automation vs human judgment\n   - Turning messy evidence into usable insight\n   - Comparing branches/conversations/attribution\n   - Building a signal culture (decisions, not slides)\n   - Talk to a human\n4. **Routing:** The workflow matches the selected button and sends the corresponding guidance message.\n5. **Human handoff (optional):** If the user selects **Talk to a human**, the workflow hands off to your configured team.\n6. **Default fallback:** If no selection matches, the workflow routes to a general handoff message.\n\n## Setup requirements\n- **Calypso Knowledge Base:** Recommended (this workflow uses a Knowledge Base policy first). No credentials are required in the workflow itself.\n- **Handoff department:** Configure an internal department (e.g., “Analytics Support”) to receive the handoff for escalation paths.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":189,"routingEnabled":8,"active":34},"wf_meeting_proof_decision_signals","calypso-public-library","1.0.0",1,[18,35,42,54,88,98,106,112,118,124,130,136,142,148,154,160,166,172,182],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":25,"category":33,"deletable":34,"connectable":34},"node_flow_configs","Workflow settings","flow-configs",[23,24],80,60,{"name":9,"description":26,"tags":27,"triggerType":32},"Decision-focused signal triage for branch metrics, conversations, and attribution. KB-first, then button routing to practical checks and escalation.",[28,29,30,31],"signal-quality","decision-making","branch-metrics","attribution","input","policy",false,{"id":36,"name":37,"type":32,"typeVersion":16,"position":38,"parameters":41,"category":32,"deletable":34,"connectable":8},"node_input","Start",[39,40],120,220,{},{"id":43,"name":44,"type":45,"typeVersion":16,"position":46,"parameters":48,"category":53,"deletable":8,"connectable":8},"node_kb_policy","Knowledge Base answer (if available)","knowledge-base-policy",[47,40],360,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":49,"activationOpener":50,"personalization":52},"ai_sticky_release",{"enabled":8,"instruction":51},"Use the Knowledge Base when it directly answers the question. If the user’s situation is ambiguous or decision-shaped, prefer the workflow’s menu so they get a structured signal check.",{"useContactName":34},"response",{"id":55,"name":56,"type":57,"typeVersion":16,"position":58,"parameters":60,"category":53,"deletable":8,"connectable":8},"node_menu","Choose a signal check","interactive-message",[59,40],620,{"messageType":61,"headerText":62,"bodyText":63,"footerText":64,"sectionTitle":65,"buttons":66,"ctaDisplayText":65,"ctaUrl":65},"button","Signal checks (pick one)","If your numbers look *beautiful*, take a breath. What decision are you trying to make right now?","Tip: Pick closest. Short playbook, no lecture.","",[67,70,73,76,79,82,85],{"id":68,"title":69},"trust_branch_numbers","Trust vs noise",{"id":71,"title":72},"spot_dirty_signal","Dirty signal",{"id":74,"title":75},"automation_vs_judgment","Auto vs judgment",{"id":77,"title":78},"messy_evidence_to_insight","Messy → insight",{"id":80,"title":81},"compare_branches_attribution","Compare & attrib",{"id":83,"title":84},"build_signal_culture","Signal culture",{"id":86,"title":87},"talk_to_human","Talk to human",{"id":89,"name":90,"type":91,"typeVersion":16,"position":92,"parameters":95,"category":97,"deletable":8,"connectable":8},"node_if_trust","If: Trust vs noise","if",[93,94],880,160,{"buttonId":68,"operator":96},"equals","routing",{"id":99,"name":100,"type":101,"typeVersion":16,"position":102,"parameters":104,"category":53,"deletable":8,"connectable":8},"node_text_trust","Trust checks for branch numbers","text-message",[103,94],1140,{"text":105},"Branch numbers deserve trust **when they survive these three tests**:\n\n1) **Definition test:** Is the metric defined the same way across branches (same inclusion/exclusion rules)? If you can’t say it in one sentence, it’s probably drifting.\n\n2) **Denominator test:** Ask “*out of what?*” A branch can ‘improve’ by shrinking the denominator (fewer eligible customers, fewer logged calls, fewer counted leads).\n\n3) **Timing test:** Are we comparing the same windows (weekday mix, promo periods, staffing changes)? A clean line chart can hide a calendar trick.\n\nWhat’s usually polished noise:\n- Any metric that moved right after someone’s bonus depended on it\n- Any branch ‘win’ that disappears when you normalize by volume, mix, or staffing\n- Attribution lifts that only show up in one reporting view\n\nIf you need one sentence for the meeting: **“Before we celebrate the number, confirm definition, denominator, and timing—then check if incentives could be writing the story.”**",{"id":107,"name":108,"type":91,"typeVersion":16,"position":109,"parameters":111,"category":97,"deletable":8,"connectable":8},"node_if_dirty","If: Spot dirty signal",[93,110],240,{"buttonId":71,"operator":96},{"id":113,"name":114,"type":101,"typeVersion":16,"position":115,"parameters":116,"category":53,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal checklist",[103,110],{"text":117},"Dirty signal usually looks *reasonable*—that’s the problem. Here are fast tells before a confident meeting:\n\n- **The ‘too smooth’ pattern:** If performance is suddenly stable after months of noise, check for a reporting change, filtering rule, or backfill.\n- **The ‘single-source miracle’:** The lift exists only in one dashboard/export. Cross-check at least one independent view.\n- **The ‘everyone improved’ week:** Great news across all branches often means a pipeline/definition change, not a behavioral change.\n- **The ‘missing messy’:** Fewer complaints, fewer returns, fewer escalations—sometimes that’s not improvement; it’s under-logging.\n\nTwo questions that save careers:\n1) **“What would make this number *wrong*?”** (force the team to name failure modes)\n2) **“What changed in the process, not the world?”** (definitions, routing, staffing, incentives, tooling)\n\nIf any of these trigger: treat the metric as **directional**, not decisive, until you reconcile the source and definition.",{"id":119,"name":120,"type":91,"typeVersion":16,"position":121,"parameters":123,"category":97,"deletable":8,"connectable":8},"node_if_auto","If: Automation vs judgment",[93,122],320,{"buttonId":74,"operator":96},{"id":125,"name":126,"type":101,"typeVersion":16,"position":127,"parameters":128,"category":53,"deletable":8,"connectable":8},"node_text_auto","When to trust automation",[103,122],{"text":129},"Trust automation when the decision is **reversible**, the inputs are **stable**, and the cost of being wrong is **contained**.\n\nUse automation for:\n- Routine routing/triage where “pretty good” beats “perfect but late”\n- High-volume decisions with clear guardrails (thresholds, caps, alerts)\n- Metrics that are hard to game and easy to audit\n\nRequire human judgment when:\n- The decision is **one-way** (policy shifts, branch staffing cuts, contract changes)\n- Incentives can shape the inputs (people will optimize the measurement)\n- The model is fed by **conversations** or messy notes (context matters, edge cases matter)\n\nPractical rule: **Automate the default, human-review the exceptions.**\nAnd set one non-negotiable: **Every automated decision needs an audit trail** (what inputs, what rule, what time window).",{"id":131,"name":132,"type":91,"typeVersion":16,"position":133,"parameters":135,"category":97,"deletable":8,"connectable":8},"node_if_messy","If: Messy evidence → insight",[93,134],400,{"buttonId":77,"operator":96},{"id":137,"name":138,"type":101,"typeVersion":16,"position":139,"parameters":140,"category":53,"deletable":8,"connectable":8},"node_text_messy","Messy evidence playbook",[103,134],{"text":141},"Turning messy evidence into usable insight isn’t about scrubbing away the truth—it’s about **preserving the weird parts** long enough to learn from them.\n\nDo this in order:\n1) **State the decision first:** “We’re deciding X by date Y.” If you can’t say that, you’re collecting vibes.\n2) **Separate facts from interpretations:** Quotes, timestamps, and counts on one side; theories on the other.\n3) **Keep the outliers visible:** Outliers are often process failures, not ‘bad customers.’ Tag them; don’t bury them.\n4) **Triangulate with one hard check:** Pick a single quantitative sanity check (volume, conversion, time-to-close) to anchor the story.\n\nWhat goes wrong first: teams ‘clean’ data by deleting ambiguity. That makes the deck prettier and the decision worse.\n\nDecision-ready output format:\n- **What we saw (3 bullets)**\n- **What it might mean (2 bullets)**\n- **What we’ll do next (1 action + 1 metric to watch)**",{"id":143,"name":144,"type":91,"typeVersion":16,"position":145,"parameters":147,"category":97,"deletable":8,"connectable":8},"node_if_compare","If: Compare branches & attribution",[93,146],480,{"buttonId":80,"operator":96},{"id":149,"name":150,"type":101,"typeVersion":16,"position":151,"parameters":152,"category":53,"deletable":8,"connectable":8},"node_text_compare","Comparison traps to avoid",[103,146],{"text":153},"Teams misread comparisons when they treat branches, conversations, and attribution like they’re the same kind of evidence. They’re not.\n\nCommon traps:\n- **Mix-shift amnesia:** Branch A ‘wins’ because it got easier customers, better staffing, or different channel mix.\n- **Conversation-count illusion:** More logged conversations can mean better logging—not better selling.\n- **Attribution overconfidence:** If the method can’t explain *non-events* (why a customer didn’t convert), it will over-claim credit.\n\nMake comparisons fair with three moves:\n1) **Normalize:** per eligible customer, per staffed hour, per comparable cohort.\n2) **Use ranges, not single ranks:** A #1 branch today can be #8 next week if volume is low.\n3) **Ask for a ‘could this be measurement?’ check:** what logging, routing, or tagging differences could create the gap?\n\nMeeting line that keeps you honest: **“Before we copy the top branch, confirm the top branch isn’t just measured differently.”**",{"id":155,"name":156,"type":91,"typeVersion":16,"position":157,"parameters":159,"category":97,"deletable":8,"connectable":8},"node_if_culture","If: Build a signal culture",[93,158],560,{"buttonId":83,"operator":96},{"id":161,"name":162,"type":101,"typeVersion":16,"position":163,"parameters":164,"category":53,"deletable":8,"connectable":8},"node_text_culture","Build a signal culture that decides",[103,158],{"text":165},"A healthy signal culture doesn’t produce more slides—it produces **faster, calmer decisions**.\n\nWhat works in practice:\n- **One owner per metric:** If nobody owns the definition, the definition will drift.\n- **Pre-meeting signal checks:** Start with “definition / denominator / timing” before debating strategy.\n- **Decision logs:** Write down the decision, the signals used, and what would change your mind. Future-you will thank you.\n- **Reward ‘found a flaw’ behavior:** The fastest way to bad data is punishing the person who points out the crack.\n\nA little wit, applied: if your dashboard can’t survive one skeptical question, it’s not a dashboard—it’s a confidence amplifier.\n\nSmall habit with big payoff: end meetings with **“What did we learn, and what will we measure next week to prove it?”**",{"id":167,"name":168,"type":91,"typeVersion":16,"position":169,"parameters":171,"category":97,"deletable":8,"connectable":8},"node_if_human","If: Talk to a human",[93,170],640,{"buttonId":86,"operator":96},{"id":173,"name":174,"type":175,"typeVersion":16,"position":176,"parameters":177,"category":181,"deletable":8,"connectable":8},"node_fallback_human","Handoff to Analytics Support","fallback",[103,170],{"handoffMessage":178,"departmentId":179,"departmentName":180},"Got it—looping in a human. Share the branch(es), time window, and the exact decision you’re trying to make, and we’ll sanity-check the signals with you.","analytics-support","Analytics Support","terminal",{"id":183,"name":184,"type":175,"typeVersion":16,"position":185,"parameters":187,"category":181,"deletable":8,"connectable":8},"node_fallback_default","Default handoff",[103,186],720,{"handoffMessage":188,"departmentId":179,"departmentName":180},"I can help, but I didn’t catch a selection. I’m handing this to a teammate—please include the branch, timeframe, and what decision is on the table.",[190,194,196,198,201,204,206,208,210,212,214,216,218,220,222,224,226],{"id":191,"source":36,"target":43,"sourceHandle":192,"targetHandle":192,"type":193},"conn_input_to_kb","default","edge",{"id":195,"source":43,"target":55,"sourceHandle":192,"targetHandle":192,"type":193},"conn_kb_to_menu",{"id":197,"source":55,"target":89,"sourceHandle":192,"targetHandle":192,"type":193},"conn_menu_to_if_trust",{"id":199,"source":89,"target":99,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_trust_true_to_text","true",{"id":202,"source":89,"target":107,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_trust_false_to_if_dirty","false",{"id":205,"source":107,"target":113,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_dirty_true_to_text",{"id":207,"source":107,"target":119,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_dirty_false_to_if_auto",{"id":209,"source":119,"target":125,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_auto_true_to_text",{"id":211,"source":119,"target":131,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_auto_false_to_if_messy",{"id":213,"source":131,"target":137,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_messy_true_to_text",{"id":215,"source":131,"target":143,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_messy_false_to_if_compare",{"id":217,"source":143,"target":149,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_compare_true_to_text",{"id":219,"source":143,"target":155,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_compare_false_to_if_culture",{"id":221,"source":155,"target":161,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_culture_true_to_text",{"id":223,"source":155,"target":167,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_culture_false_to_if_human",{"id":225,"source":167,"target":173,"sourceHandle":200,"targetHandle":192,"type":193},"conn_if_human_true_to_handoff",{"id":227,"source":167,"target":183,"sourceHandle":203,"targetHandle":192,"type":193},"conn_if_human_false_to_default_fallback","automation",[28,29,30,31,230,231],"research-triage","leadership",[233],"Calypso Knowledge Base","intermediate","Calypso","2026-04-22T11:03:17.700Z","/en/workflows/meeting-proof-decision-signals",{"en":237},{"title":240,"description":241,"ogDescription":242,"twitterDescription":243,"canonicalPath":237,"robots":244,"schemaType":245,"alternates":246},"Meeting Proof Decision Signals","Route teams through quick trust checks for branch numbers, dirty signals, and automation vs judgment—then hand off to humans when needed.","Help teams avoid confident wrong decisions with fast signal checks: what to trust, what’s noise, when automation is safe, and when to escalate.","A practical signal triage workflow: branch numbers, dirty data tells, automation vs judgment, and a clean human handoff for high stakes calls.","index,follow","HowTo",[247],{"hreflang":6,"href":237},1776877119125]