General Tab (Behavior and Voice Mode)

Summary

General tab settings influence baseline conversation style and operational AI behavior. Use structured edits to avoid unintended tone shifts. 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

• Tune global AI behavior.
• Set voice mode controls for message generation context.
• Stabilize baseline responses before advanced tuning.

Before you start

• Select correct bot.
• Review recent conversation quality baseline.
• Avoid editing Persona and General simultaneously on first pass.

Step-by-step workflow

1. Open General tab in /dashboard/bot-configuration.
2. Adjust behavior settings deliberately.
3. Review voice mode section values.
4. Save with Sync Changes.
5. Send test prompts in Fan Inbox.
6. Compare outputs with previous baseline.

Key states and error handling

• General tab changes affect broad conversation behavior.
• Unsynced changes are not guaranteed live.
• Quality drift can appear if multiple knobs are changed together.

Best practices

• Change one major behavior parameter at a time.
• Keep a before/after note for each sync batch.
• Rollback quickly if conversion quality drops.

Troubleshooting

• If outputs become unstable, revert last behavior batch.
• If voice behavior looks inconsistent, review voice mode controls.
• If no visible effect, ensure sync completed and test thread is fresh.
• 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.