See the change before it goes live.
Turn a specific problem into a versioned proposal. Review the wording or connection change, compare tests and decide what reaches visitors.
A specific change. A visible decision.

Inspect a concrete repair candidate.
The supported repair workflow inspects the complete saved graph and prepares selected changes. Each proposal identifies the affected node, original value, candidate value and reason. Use this comparison to decide whether the proposal matches the problem you actually want to solve.
Visitor-facing wording
Clarify supported prompt text while preserving required steps and business meaning. Check that the candidate still asks for the information your team needs.
Controlled connections
Repair supported graph connections to permitted destinations. This capability does not redesign every node, integration or business rule without constraints.
Behavioral comparisons
Run scenarios against baseline and candidate. Results give evidence about the tested cases; they cannot certify every future conversation.
Keep draft approval and publication visible.
Applying a proposal changes a draft. Publishing changes the version served to visitors. These are separate decisions with their own checks, so a reviewed draft does not silently become a live release.
Exact-version approval
Approval is tied to the candidate and expected bot version. Changed drafts or policies can invalidate the operation and require another review.
Request a revision
Give clearer instructions and prepare a revised proposal while retaining earlier history. Reject a change that should not proceed.
Guarded recovery
Rollback checks the current version. A later edit or superseding release can block restoration rather than overwrite human work.
How it works.
- 01
Describe the repair
Choose a saved bot and AI wording & connection repair. State the problem and what must stay consistent.
- 02
Review the proposal
Read before/after values and scenario results. Revise, reject or approve the exact candidate.
- 03
Publish deliberately
Review publication separately, then test and monitor the released experience.
From question to next action.
- 01Goal
- Repair a dead end after a visitor selects support.
- 02Evidence
- Illustrative baseline scenario: the support option has no usable next step.
- 03Action
- Propose an appropriate existing destination and compare the same scenario against both versions.
- 04Follow-through
- Approve and publish the reviewed draft. Retain the prior version for guarded recovery.
What to expect.
| Scope | Details |
|---|---|
| Available | AI wording repair, supported connection repair, revision, draft approval and reviewed publication. |
| Manual review | Connection changes and broader AI rewrites remain outside automatic wording eligibility. |
| Validation limit | Tests cover defined cases and cannot guarantee factual or business correctness. |
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.
