Sync and Validation Playbook

Summary

Configuration changes are only useful if validated under live-like conditions. This article gives a repeatable rollout loop. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Prevent silent misconfiguration.
• Detect regressions quickly after edits.
• Standardize QA across operators.

Before you start

• Define success criteria for the change.
• Pick one test scenario in Fan Inbox.
• Capture baseline response samples.

Step-by-step workflow

1. Apply a small coherent config change.
2. Click Sync Changes.
3. Open Fan Inbox and run prepared test scenario.
4. Compare output with baseline.
5. If good, record result and continue next change.
6. If bad, rollback immediately and note root cause.

Key states and error handling

• Saved does not mean optimal; validation is mandatory.
• Multiple simultaneous edits complicate root-cause analysis.
• Regression risk rises with broad ungrouped edits.

Best practices

• Batch by intent (persona vs behavior vs profile).
• Use same prompts for A/B comparison.
• Keep concise change logs.

Troubleshooting

• If no impact is observed, verify bot context and sync completion.
• If quality drops, rollback most recent batch first.
• If issue persists, isolate tab-level changes and test separately.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Bot selector defines the full configuration scope; wrong selection causes false diagnostics.
• General tab contains baseline behavior and voice mode controls used in most conversations.
• AI Persona tab configures stylistic identity and voice consistency across long threads.
• Creator Information tab enriches factual context and coherence in responses.
• Sync Changes is the commit action; unsynced edits should not be considered deployed.
• Profile completion is a quality signal, not a guarantee of conversion quality.
• No-bot and no-node states are explicit and should be resolved before tuning.
• Every major change must be validated in live-like Fan Inbox scenarios.

Operator checklist (before shipping changes)

• Freeze target bot selection before editing any field.
• Batch changes by intent (behavior, persona, profile) to simplify rollback.
• Sync after each coherent batch rather than one massive final save.
• Run controlled test prompts after each sync cycle.
• Capture before/after examples for quality comparison.
• Rollback immediately if tone or negotiation quality degrades.

Real-world scenario

Conversion quality drops after persona edits. The operator identifies the exact sync batch, rolls back conflicting persona instructions, re-syncs, and validates improvement with a controlled fan-style test sequence.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.