Bot Configuration Page Overview

Summary

This article explains page structure, bot selector behavior, and how the three tabs work together as one configuration pipeline. 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

• Navigate configuration quickly.
• Reduce wrong-bot edits.
• Understand where each setting category lives.

Before you start

• Connect at least one bot.
• Choose target bot before editing.
• Know whether you are tuning behavior, persona, or profile fields.

Step-by-step workflow

1. Open /dashboard/bot-configuration.
2. Select bot from the node selector.
3. Review top-level tabs: General, AI Persona, Creator Information.
4. Navigate to target tab and adjust only related fields.
5. Use Sync Changes to persist edits.
6. Validate in Fan Inbox after save.

Key states and error handling

• No bot state: 'Connect a bot to configure its identity.'
• No selected node state: 'Select a node to begin identity mapping'.
• Save action is explicit and not automatic.

Best practices

• Lock bot context before collaborative edits.
• Treat each tab as separate change set.
• Verify live behavior after each sync.

Troubleshooting

• If page blocked, connect a bot first.
• If wrong data appears, confirm selected bot.
• If changes not visible, sync again then test with new conversation.
• 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.