Test specific changes
An experiment tests one specific change against the current configuration — a rephrased question, a different branch instruction, a tone adjustment. Isolating one variable means the result is attributable.
How it works: EXPERIMENT_PROPOSAL includes the proposed_changes diff — exactly what differs between control and variant is visible before you approve the experiment.
No disruption to live campaigns
During an experiment, both versions are active. The learning engine continues to analyse conversations from both. If the variant performs significantly worse, you can stop the experiment and revert to the control at any time.
How it works: Every version is revertable — including experiment versions. Revert creates a new version record so the action itself is auditable.
Results feed future proposals
Completed experiment results are fed back into the learning engine as evidence. If one version significantly outperforms the other, the pattern detector can generate a STATISTICALLY_SUPPORTED proposal to adopt the winning configuration.
How it works: Experiment results become the highest-confidence evidence class — statistical confidence from a controlled split is better than observational correlation.
Sample size enforcement
Experiment results aren't surfaced until the sample size is sufficient for statistical confidence. Running an experiment to 5 conversations and adopting the winner is a common mistake — the platform prevents it.
How it works: Minimum sample threshold applies to experiment results as well as pattern detection — no premature conclusions.