Run the conversation

Your playbook. In plain English. Followed exactly.

Decision trees aren't flowchart diagrams — they're branch instructions attached to each question. The AI reads them as natural language and applies them. No code, no if-then builders, no visual editors required.

Plain Englishbranch instructions — no flowchart software required
Auto-generateddecision tree summary — updates on every change
4 tokensEND, REACH_BACK_OUT, BOOKED, or Q number
Freeformprose branch instructions also supported
How playbooks work

The AI reads your branch instructions as if you wrote them directly.

Each question in the campaign has an optional branch value — what the AI should do when a contact gives a negative answer. These are translated into plain English and injected into the system prompt alongside the question set. The AI applies them as part of its judgment — no runtime decision tree is traversed by code.

  • Branch values attached to each question — not to the campaign as a whole
  • Structured tokens translated to plain English: END → 'end the conversation'
  • Freeform prose passed through verbatim — 'suggest the starter plan if budget is under $10k'
  • Branch logic applied by AI judgment — not hardcoded conditional logic
  • Decision tree summary auto-generated and visible in campaign configuration
  • Summary matches exactly what the AI receives in the system prompt
Branch instruction flow
  1. 1
    Q2 branch configured
    Token: END or prose: 'suggest lite plan'
  2. 2
    Token translated
    END → 'if negative: end the conversation'
  3. 3
    Injected to prompt
    Branch instruction appears after Q2 in system prompt
  4. 4
    Contact answers Q2
    Negative answer received by AI
  5. 5
    AI applies branch
    Reads instruction, applies judgment, returns END
  6. 6
    Conversation closes
    Pipeline acts on END directive — no further messages
Visibility and testing

See exactly what the AI will do before it talks to anyone.

The decision tree summary gives operators a plain-English view of the full qualification logic. The Campaign Tester lets you verify every branch before launch.

Decision tree summary

Alongside the question list in campaign configuration, a structured plain-text summary shows the full decision tree: each question, its positive path, and its branch outcome. No database fields to interpret.

How it works: Summary regenerates automatically when questions or branch values change — always current, always accurate.

Freeform + structured in one view

The summary accurately represents both structured tokens (END → 'end conversation') and freeform prose instructions (shown verbatim as an Instruction line). What the operator reads is exactly what the AI receives.

How it works: Tested to confirm freeform branch instructions use Instruction prefix in summary — no loss of meaning in translation.

Campaign Tester branch shortcuts

The Campaign Tester includes branch shortcuts — buttons that let you simulate a negative answer to a specific question without manually walking through the full conversation from Q1. Test every branch path in minutes.

How it works: All test turns are flagged is_test=True — branch testing never contaminates learning engine analysis.

Version-tracked changes

Every change to the question set or branch values creates a new campaign version. You can compare what the AI received in any prior conversation to the current configuration — and revert to any prior version if a change made performance worse.

How it works: from_proposal_id is recorded on versions created by learning proposals — trace any version back to the evidence that justified it.

Want to build your first
decision tree in plain English?

We'll configure your question set, write the branch instructions, and test every path with you.