Give every improvement a purpose.
Set a bot objective, record the starting point and compare the released candidate with its baseline. Connect repair decisions to observed outcomes.
Every improvement starts with a goal.

Choose the outcome before the change.
A support bot and a lead qualification bot should not be assessed in the same way. Choose an objective that matches the journey, then check whether the corresponding events are recorded. A goal cannot be measured reliably when its tracking is absent.
Per-bot objectives
Select the available completion, tracked goal or handoff objective appropriate to your flow. Read metric definitions before deciding what success means.
Frozen release baseline
Publication captures a starting snapshot for the candidate release. Later comparisons should refer to that release rather than combine unrelated versions.
Collect enough activity
Reports with insufficient conversations remain in collecting status. A handful of successful conversations cannot establish a reliable improvement.
Treat a benefit as a hypothesis until measured.
Clearer wording may help visitors continue. Validate the candidate’s behavior first, then observe its release. A before/after difference alone does not prove that the repair caused it.
Reviewed improvements
Prepare wording and controlled connection changes with readable diffs and baseline-versus-candidate scenario results.
Narrow automatic changes
Exact owner-approved replacements and supported whitespace cleanup may qualify under a saved policy. General AI rewrites and flow changes still need review.
Learn from the result
Use the comparison to decide whether to investigate again. Proposed lessons remain editable and require approval before becoming trusted memory.
How it works.
- 01
Set the objective
Select a bot in Optimization and check its tracking.
- 02
Release a tested candidate
Prepare, review and publish a specific improvement.
- 03
Compare the outcome
Inspect the exact release report after sufficient relevant activity.
From question to next action.
- 01Goal
- Simplify a lead question without changing qualification requirements.
- 02Evidence
- Illustrative evidence: one prompt combines several requests in a confusing sentence. Its commercial impact is still unknown.
- 03Action
- Prepare clearer wording, compare the scenario results and publish after review.
- 04Follow-through
- Compare tracked goals with the baseline. Review lead quality separately and account for traffic changes.
What to expect.
| Scope | Details |
|---|---|
| Available | Objectives, performance snapshots and post-release comparisons. |
| Conditional | Recurring work needs explicit bot enrollment and a functioning maintenance runner. |
| Separate roadmap | Broad knowledge optimization and actual AI model fine-tuning. |
Access depends on permissions, provider configuration and applicable AI allowance. Check current plans and pricing.

Start with a question.
Build toward better outcomes.
One bot. One clear goal. A teammate to help you move forward.
Compare plans and AI allowancesWithin your boundaries.Review first.
Expand when you’re ready.
