Calypso Logo
Back to Workflows
automationintermediate

Signal Reliability Navigator for Branch Decisions

A guided chat workflow that helps teams separate trustworthy branch signals from polished noise, spot dirty data early, and decide when automation needs human judgment.

Calypso
1 integrations

Integrations

Calypso Inbox

Tags

signal-qualitybranch-metricsdecision-makingdata-hygieneattributiontriage

Workflow Visualization

Rendered directly from the published workflow JSON.

19 nodes21 connections
CWorkflow settingsFlow ConfigsConfigConfigGuided triage for branchnumbers, dirty signals,automation judgment...Trigger: inputDefines the graph defaultsIInbound messageInputInputInputWhatsApp entry pointNew conversations begin hereKBKnowledge Base answer…Knowledge BotResponseResponseMode: defaultFallback enabledFallback enabledIMChoose what you're…Interactive MessageResponseResponsePick the check you need. Builtto catch clean-looking bad databefore it wins a m...5 options • Trust numbers •Dirty signalTip: Ask a metric name for a fast…IFIf: Trustworthy…IFLogicLogictrust_numbers =TRUE -> next FALSE -> waitTPlaybook: Which…Simple MessageResponseResponseTrust the branch number *onlyafter* it passes these sanitychecks: 1) **Definition…836 charsIFIf: Spot dirty signal…IFLogicLogicspot_dirty_signal =TRUE -> next FALSE -> waitTPlaybook: Spot dirty…Simple MessageResponseResponseDirty signal is polite: itrarely announces itself. Lookfor these early warnings: -…760 charsIFIf: Automation vs…IFLogicLogicauto_vs_judgment =TRUE -> next FALSE -> waitTPlaybook: When to…Simple MessageResponseResponseTrust automation when thedecision is **repeatable**, theinputs are…732 charsIFIf: Compare branches…IFLogicLogiccompare_branches =TRUE -> next FALSE -> waitTPlaybook: Comparisons…Simple MessageResponseResponseBranch comparisons fail in thesame predictable ways: 1)**Different denominators**:…787 charsIFIf: Build a signal…IFLogicLogicsignal_culture =TRUE -> next FALSE -> waitTPlaybook: Build a…Simple MessageResponseResponseA healthy signal culturedoesn’t produce moredashboards. It produces faster…755 charsIMWhat next?Interactive MessageResponseResponseWant to ask something else, orshould we loop in a human?2 options • New question • Talkto Data OpsIFIf: Talk to Data OpsIFLogicLogictalk_to_data_ops =TRUE -> next FALSE -> waitFHHandoff to Data…Messenger HandoffHandoffHandoffData OperationsLooping in Data Operations tohelp validate signals,…Routes the conversation to a…TStart a new questionSimple MessageResponseResponseSend a new message anytime tostart over. If you include themetric name, branches, and tim…139 charsFHFallback: No matching…Messenger HandoffHandoffHandoffData OperationsI couldn’t match that choice toa topic. I’ll route you to Data…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 have decisions.” When someone pings your Calypso Inbox with a messy branch question (metrics, conversations, attribution, operational events), the workflow first tries to answer from your Knowledge Base. If it can’t confidently resolve the question, it routes the person into a set of decision-shaped mini playbooks.

Each path is built to catch the failure mode that usually bites first: clean-looking data that’s quietly inconsistent, comparability traps across branches, and automation that’s technically correct while practically misleading. It’s designed to keep confident meetings from going confidently wrong.

Key features

  • Knowledge Base first, routing second: answers known questions fast, escalates the rest.
  • Button-based menu of practical decision checks (trustworthy numbers, dirty signals, automation vs judgment, comparisons, culture).
  • Consistent “next step” prompt after each playbook: return to topics or hand off to a human.
  • Single escalation point to a defined department (Data Operations) with a clear handoff message.

Step-by-step

  1. Input (New message) starts the workflow when someone asks a question in Calypso Inbox.
  2. Knowledge Base policy attempts to answer using your maintained guidance (definitions, metric rules, branch event taxonomy, attribution rules, etc.).
  3. If a direct answer isn’t available, the workflow shows “Choose what you’re deciding” with five buttons:
    1. Which branch numbers deserve trust (vs noise)
    2. Spot dirty signal before the meeting
    3. Automation vs human judgment
    4. Comparing branches & attribution traps
    5. Build a signal culture (decisions > slides)
  4. The workflow routes based on the selected button and sends a focused checklist as a text message.
  5. After the checklist, “What do you want to do next?” appears:
    • Back to topics returns to the main menu.
    • Talk to Data Ops escalates to the Data Operations department via fallback handoff.

Setup requirements

  • Calypso Knowledge Base: Add/maintain entries for metric definitions, branch comparability rules, attribution logic, and known caveats. No external credentials required.
  • Calypso Inbox channel that supports interactive buttons (where you deploy this workflow).
  • A configured handoff department named Data Operations (match the department ID/name used in the fallback node).

Ready to use this workflow?

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

Go to Calypso