[{"data":1,"prerenderedAt":226},["ShallowReactive",2],{"/en/workflows/signal-checks-before-the-confident-meeting":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":206,"tags":207,"integrations":211,"difficulty":213,"author":214,"verified":33,"featured":33,"date":215,"modified":215,"icon":7,"imageSrc":7,"path":216,"alternates":217,"seo":218},"147c7567-4424-4b4a-a535-3cdeefa7fb04","signal-checks-before-the-confident-meeting","en",null,true,"Signal Checks Before the Confident Meeting","A decision-ready coaching flow that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and choose when to rely on automation vs human judgment.","## How it works\nThis workflow is a fast, practical “pre-meeting filter” for messy branch numbers, conversation notes, and attribution claims. It helps teams avoid the classic failure mode: data that looks tidy enough to defend in a meeting—right up until it drives a confident wrong decision.\n\nIt starts by checking your Knowledge Base for any existing guidance, then routes the user to one of five decision-shaped playbooks (or a human handoff). Each path delivers a short, operator-friendly checklist that makes it harder for dirty signal to sneak into slides, forecasts, or performance comparisons.\n\n## Key features\n- Uses a Knowledge Base policy first, so existing internal definitions (KPIs, attribution rules, branch event taxonomy) are honored before routing.\n- Button-based routing to five high-impact signal scenarios: trust checks, dirty-signal detection, automation vs judgment, comparisons/attribution, and signal culture.\n- Practical “what to trust vs what’s polished noise” guidance written for operators—not analysts.\n- Includes a human handoff option for cases where ambiguity is the point (and automation shouldn’t pretend otherwise).\n\n## Step-by-step\n1. **Trigger:** A user starts the flow in Calypso (Input).\n2. **Knowledge check:** The workflow applies the **Knowledge Base policy** to ground answers in your existing definitions and rules.\n3. **User chooses a scenario:** The workflow presents a **button menu**:\n   - Which branch numbers deserve trust?\n   - How to spot dirty signal early\n   - When to trust automation vs judgment\n   - Comparing branches & attribution (what teams misread)\n   - Building a signal culture (decisions > slides)\n   - Talk to a human\n4. **Routing and response:** Based on the selected button, the workflow delivers a targeted checklist message.\n5. **Human handoff (optional):** If the user selects **Talk to a human**, the workflow routes to a handoff with a short context-setting message.\n\n## Setup requirements\n- **No external credentials required.**\n- A configured **Calypso Inbox** channel where this workflow can be used.\n- Optional but recommended: populate your **Calypso Knowledge Base** with your KPI definitions, attribution rules, and branch event standards so the policy step can reinforce them.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":172,"routingEnabled":8,"active":33},"wf_signal_checks_confident_meeting_v1","calypso-public-library","1.0.0",1,[18,34,41,53,84,93,101,107,113,119,125,131,137,143,149,155,165],{"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],-240,-80,{"name":9,"description":26,"tags":27,"triggerType":31},"Decision-ready signal checks for branch metrics, conversations, and attribution—built to catch polished noise before it wins a meeting.",[28,29,30],"signal-quality","decision-making","branch-metrics","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":40,"category":31,"deletable":33,"connectable":8},"node_input","Start",[38,39],-200,120,{},{"id":42,"name":43,"type":44,"typeVersion":16,"position":45,"parameters":47,"category":52,"deletable":8,"connectable":8},"node_kb_policy","Knowledge base policy","knowledge-base-policy",[46,39],40,{"enabled":8,"fallbackToRouting":8,"sticky":8,"stickyMode":48,"activationOpener":49,"personalization":51},"ai_sticky_release",{"enabled":8,"instruction":50},"Use practical, decision-ready guidance. Prefer concrete checks over theory. If definitions or rules exist in the knowledge base (KPIs, attribution, branch event taxonomy), apply them consistently.",{"useContactName":33},"response",{"id":54,"name":55,"type":56,"typeVersion":16,"position":57,"parameters":59,"category":52,"deletable":8,"connectable":8},"node_menu","Choose what you’re deciding","interactive-message",[58,39],300,{"messageType":60,"headerText":61,"bodyText":62,"footerText":63,"sectionTitle":64,"buttons":65,"ctaDisplayText":64,"ctaUrl":64},"button","Signal check menu","Pick the situation. I’ll give you a tight checklist that protects you from polished noise (the kind that looks fine until it makes you confidently wrong).","Tip: for definitions, pick Compare & attribute.","",[66,69,72,75,78,81],{"id":67,"title":68},"trust_branch_numbers","Trust branch numbers",{"id":70,"title":71},"spot_dirty_signal","Spot dirty signal",{"id":73,"title":74},"automation_vs_judgment","Automation vs human",{"id":76,"title":77},"compare_branches_attribution","Compare & attribute",{"id":79,"title":80},"signal_culture","Build signal culture",{"id":82,"title":83},"human_handoff","Talk to a human",{"id":85,"name":86,"type":87,"typeVersion":16,"position":88,"parameters":90,"category":92,"deletable":8,"connectable":8},"node_if_trust","If: trust branch numbers","if",[89,46],560,{"buttonId":67,"operator":91},"equals","routing",{"id":94,"name":95,"type":96,"typeVersion":16,"position":97,"parameters":99,"category":52,"deletable":8,"connectable":8},"node_text_trust","Trust checks for branch numbers","text-message",[98,46],820,{"text":100},"Here’s how to tell which branch numbers deserve trust (and which are polished noise):\n\n1) **Traceability beats precision.** If you can’t explain where the number comes from in one breath (source → logic → refresh cadence), treat it as *decorative*.\n2) **Stability check:** Does it swing wildly when you change the time window by a day or two? Fragile numbers are usually definition problems, not performance.\n3) **Denominator honesty:** Any rate without a clean denominator (eligible traffic, staffed hours, qualified leads) is a confidence trap.\n4) **Operational friction test:** Numbers that improve while frontline reality gets harder (queues, rework, complaints) are often instrumentation drift.\n5) **Reconciliation:** If finance/ops and branch reporting can’t reconcile to within a sane band, you don’t have “two views”—you have an argument in progress.\n\nIf you tell me the metric name and branch context, I can suggest the *first* reconciliation to run.",{"id":102,"name":103,"type":87,"typeVersion":16,"position":104,"parameters":106,"category":92,"deletable":8,"connectable":8},"node_if_dirty","If: spot dirty signal",[89,105],140,{"buttonId":70,"operator":91},{"id":108,"name":109,"type":96,"typeVersion":16,"position":110,"parameters":111,"category":52,"deletable":8,"connectable":8},"node_text_dirty","Dirty signal early warnings",[98,105],{"text":112},"Dirty signal rarely announces itself. It shows up as *convenient certainty*. Watch for these early warnings before the meeting goes off the rails:\n\n- **Sudden smoothness:** A messy process starts producing perfectly clean charts. That’s usually filtering, not improvement.\n- **Definition drift:** The metric name stays the same while eligibility/attribution rules quietly change.\n- **Backfilled heroics:** Last month’s numbers “improve” after the month closes. If backfills aren’t tracked, you’re rewriting history.\n- **Conversation-to-outcome leaps:** Notes like “customer interested” get treated as intent, then as pipeline, then as revenue.\n- **One-branch miracles:** A single branch jumps without a corresponding operational explanation (staffing, hours, local campaign, constraint lifted).\n\nQuick move: ask, “What would make this number *wrong*?” If nobody can answer in under 30 seconds, you’re looking at brittle signal.",{"id":114,"name":115,"type":87,"typeVersion":16,"position":116,"parameters":118,"category":92,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[89,117],240,{"buttonId":73,"operator":91},{"id":120,"name":121,"type":96,"typeVersion":16,"position":122,"parameters":123,"category":52,"deletable":8,"connectable":8},"node_text_auto","Automation vs human judgment",[98,117],{"text":124},"When to trust automation (and when to keep a human in the loop):\n\n**Trust automation when:**\n- The rule is **stable** (same inputs mean the same decision week to week).\n- Errors are **cheap and reversible** (routing, reminders, low-risk prioritization).\n- You can measure **precision/recall** or at least a clear error rate.\n\n**Require human judgment when:**\n- The cost of a wrong call is **asymmetric** (losing a key customer, compliance risk, brand damage).\n- The input signal is **strategic or social** (branch context, relationship nuance, exceptions).\n- People are likely to **game** the metric once it becomes a target.\n\nRule of thumb: automate the *boring parts of consistency*; keep humans for the parts where context is the product.",{"id":126,"name":127,"type":87,"typeVersion":16,"position":128,"parameters":130,"category":92,"deletable":8,"connectable":8},"node_if_compare","If: compare branches & attribution",[89,129],340,{"buttonId":76,"operator":91},{"id":132,"name":133,"type":96,"typeVersion":16,"position":134,"parameters":135,"category":52,"deletable":8,"connectable":8},"node_text_compare","Comparison & attribution pitfalls",[98,129],{"text":136},"What teams repeatedly misread when comparing branches, conversations, and attribution:\n\n1) **Different opportunity sets.** Branches don’t get the same mix (walk-ins vs appointments, new vs existing customers, local constraints). Compare *like-for-like cohorts*.\n2) **Attribution isn’t truth; it’s a policy.** “Last touch” is a choice, not a fact. If the policy isn’t explicit, comparisons are theater.\n3) **Conversation volume ≠ conversation quality.** More logged notes can mean better service—or just better compliance.\n4) **Lag mismatch.** Some branches show results later (cycle time, follow-up capacity). If you compare on the wrong window, you punish the patient and reward the lucky.\n5) **Survivorship in the funnel.** If one branch disqualifies more aggressively, downstream rates look better. Check the disqualification rules.\n\nFast fix: before ranking branches, write down the eligibility rules and the time window. If you can’t, you’re not ranking performance—you’re ranking measurement artifacts.",{"id":138,"name":139,"type":87,"typeVersion":16,"position":140,"parameters":142,"category":92,"deletable":8,"connectable":8},"node_if_culture","If: build signal culture",[89,141],440,{"buttonId":79,"operator":91},{"id":144,"name":145,"type":96,"typeVersion":16,"position":146,"parameters":147,"category":52,"deletable":8,"connectable":8},"node_text_culture","Build a signal culture",[98,141],{"text":148},"How to build a signal culture that helps decisions happen (not just slides):\n\n- **Name the decision first.** If you can’t say what you’ll do differently based on the metric, it’s a vanity dashboard.\n- **Create a “definition of done” for numbers.** Source, owner, refresh cadence, and what it *doesn’t* include.\n- **Celebrate boring reconciliation.** Teams copy what gets rewarded; reward catching issues early.\n- **Keep a visible exception log.** The fastest way to lose trust is to pretend exceptions don’t exist.\n- **Separate learning metrics from target metrics.** The moment you target it, people will optimize it—often creatively.\n\nA little wit, a lot of rigor: if your best metric needs a motivational speech to be believed, it’s not a metric yet.",{"id":150,"name":151,"type":87,"typeVersion":16,"position":152,"parameters":154,"category":92,"deletable":8,"connectable":8},"node_if_handoff","If: talk to a human",[89,153],540,{"buttonId":82,"operator":91},{"id":156,"name":157,"type":158,"typeVersion":16,"position":159,"parameters":160,"category":164,"deletable":8,"connectable":8},"node_fallback","Handoff to analyst","fallback",[98,153],{"handoffMessage":161,"departmentId":162,"departmentName":163},"Got it—this sounds like a judgment call or a definition dispute, not a checklist problem. I’m handing you to a human so you can share the metric, branch context, and what decision is on the table.","signals-ops","Signals & Ops","terminal",{"id":166,"name":167,"type":96,"typeVersion":16,"position":168,"parameters":170,"category":52,"deletable":8,"connectable":8},"node_text_unknown","If no button matched",[98,169],640,{"text":171},"I didn’t catch a valid selection. Please pick one of the buttons so I can route you to the right signal checklist.",[173,176,178,180,183,186,188,190,192,194,196,198,200,202,204],{"id":174,"source":35,"target":42,"sourceHandle":175,"targetHandle":175,"type":175},"conn_input_to_kb","default",{"id":177,"source":42,"target":54,"sourceHandle":175,"targetHandle":175,"type":175},"conn_kb_to_menu",{"id":179,"source":54,"target":85,"sourceHandle":175,"targetHandle":175,"type":175},"conn_menu_to_if_trust",{"id":181,"source":85,"target":94,"sourceHandle":182,"targetHandle":175,"type":175},"conn_if_trust_true_to_text","true",{"id":184,"source":85,"target":102,"sourceHandle":185,"targetHandle":175,"type":175},"conn_if_trust_false_to_if_dirty","false",{"id":187,"source":102,"target":108,"sourceHandle":182,"targetHandle":175,"type":175},"conn_if_dirty_true_to_text",{"id":189,"source":102,"target":114,"sourceHandle":185,"targetHandle":175,"type":175},"conn_if_dirty_false_to_if_auto",{"id":191,"source":114,"target":120,"sourceHandle":182,"targetHandle":175,"type":175},"conn_if_auto_true_to_text",{"id":193,"source":114,"target":126,"sourceHandle":185,"targetHandle":175,"type":175},"conn_if_auto_false_to_if_compare",{"id":195,"source":126,"target":132,"sourceHandle":182,"targetHandle":175,"type":175},"conn_if_compare_true_to_text",{"id":197,"source":126,"target":138,"sourceHandle":185,"targetHandle":175,"type":175},"conn_if_compare_false_to_if_culture",{"id":199,"source":138,"target":144,"sourceHandle":182,"targetHandle":175,"type":175},"conn_if_culture_true_to_text",{"id":201,"source":138,"target":150,"sourceHandle":185,"targetHandle":175,"type":175},"conn_if_culture_false_to_if_handoff",{"id":203,"source":150,"target":156,"sourceHandle":182,"targetHandle":175,"type":175},"conn_if_handoff_true_to_fallback",{"id":205,"source":150,"target":166,"sourceHandle":185,"targetHandle":175,"type":175},"conn_if_handoff_false_to_unknown","automation",[28,29,30,208,209,210],"attribution","data-hygiene","automation-judgment",[212],"Calypso Inbox","intermediate","Calypso","2026-04-05T11:04:06.101Z","/en/workflows/signal-checks-before-the-confident-meeting",{"en":216},{"title":9,"description":219,"ogDescription":220,"twitterDescription":221,"canonicalPath":216,"robots":222,"schemaType":223,"alternates":224},"Route teams to decision ready checklists to spot dirty signals, trust the right branch numbers, and avoid confident wrong calls.","A practical signal quality coach: trust checks for branch metrics, dirty signal spotting, automation vs judgment, and comparison pitfalls—plus human handoff.","Turn messy branch signals into decision ready checks: what to trust, what’s noise, what breaks first, and when humans should override automation.","index,follow","HowTo",[225],{"hreflang":6,"href":216},1775503436511]