Back to Workflows
automationintermediate

Branch Signal Decision Field Manual

A guided decision workflow that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and choose when automation should (and shouldn’t) drive decisions.

Calypso
1 integrations

Integrations

Calypso Inbox

Tags

signal-qualitybranch-metricsdecision-makingdata-hygieneattributiontriage

Workflow Visualization

Rendered directly from the published workflow JSON.

15 nodes13 connections
CWorkflow settingsFlow ConfigsConfigConfigDecision-focused guidance toseparate trustworthy branchsignals from...Trigger: inputDefines the graph defaultsIStartInputInputInputWhatsApp entry pointNew conversations begin hereKBKnowledge base: metri…Knowledge BotResponseResponseBefore we debate the number:what exactly is being counted,…Mode: defaultFallback enabledIMPick a decision…Interactive MessageResponseResponseChoose what you’re trying todecide. I’ll give you a quickfield guide—practical...5 options • Trust numbers •Dirty signalTip: If it fails a definition…IFIf: Which numbers to…IFLogicLogictrust_branch_number...TRUE -> next FALSE -> waitTTrust checks for…Simple MessageResponseResponseHere’s how to tell“decision-grade” branch numbersfrom polished noise: 1)…796 charsIFIf: Spot dirty signal…IFLogicLogicspot_dirty_signal =TRUE -> next FALSE -> waitTDirty signal detectorsSimple MessageResponseResponseDirty signal usually looks*reasonable*—that’s why it winsmeetings. Quick detectors: -…657 charsIFIf: Automation vs…IFLogicLogicautomation_vs_judgm...TRUE -> next FALSE -> waitTWhen to trust…Simple MessageResponseResponseAutomation is great at**consistency**, not**wisdom**. Use it when: - The…711 charsIFIf: Compare branches…IFLogicLogiccompare_branches_at...TRUE -> next FALSE -> waitTBranch comparison…Simple MessageResponseResponseMost branch comparisons failfor predictable reasons: 1)**Mix shift**: Branch A didn’t…753 charsIFIf: Build a signal…IFLogicLogicbuild_signal_cultur...TRUE -> next FALSE -> waitTSignal culture that…Simple MessageResponseResponseA healthy signal culture isn’tmore dashboards—it’s fewersurprises. - **Decision logs**…512 charsFHEscalate to analytics…Messenger HandoffHandoffHandoffAnalytics OpsThis looks like one of thosecases where the numbers behave…Routes the conversation to a…

Use the JSON view if you need to inspect or copy the exact structure.

Workflow guide

A practical operator-friendly explanation of how this automation works.

4 sections

How it works

This workflow turns “we have numbers” into “we can trust this decision.” It starts by offering a quick, practical signal check (via your knowledge base), then routes people into decision-shaped guidance: which branch metrics deserve trust, how to detect dirty signal before the meeting gets confident, and when human judgment should override automated conclusions.

It’s designed for operators and leaders who don’t need more dashboards—they need fewer wrong calls. The tone is intentionally plainspoken: most bad data looks impressively normal right up until it wins an argument.

Key features

  • Uses a Knowledge Base Policy first, so common “what does this metric mean?” questions get answered before opinions form.
  • Presents a menu of decision scenarios (trust, hygiene, automation vs judgment, comparison, culture) via an interactive button message.
  • Routes with explicit button-based branching so guidance stays focused and repeatable.
  • Provides field-tested checks for denominator problems, definition drift, mix shifts, and attribution traps.
  • Includes a fallback handoff for cases that need human review (analytics/ops) instead of more automated certainty.

Step-by-step

  1. Trigger: A user starts the workflow (Input).
  2. Answer basics first: The Knowledge Base Policy responds to straightforward questions and primes the conversation for consistent definitions.
  3. Choose the decision scenario: The user selects one of five buttons (Interactive Message).
  4. Route to the right playbook: Conditional checks (If nodes) detect the selected button and deliver targeted guidance (Text Message).
  5. Escalate when needed: If no option matches (or the situation is ambiguous), the workflow routes to a human handoff (Fallback).

Setup requirements

  • A Calypso Inbox/channel where interactive messages are supported.
  • (Recommended) A populated Calypso Knowledge Base with your branch metric definitions and calculation notes.
  • No external credentials are required for this workflow.

Ready to use this workflow?

Import this workflow into your Calypso account and start automating your processes.

Go to Calypso