> ## Documentation Index > Fetch the complete documentation index at: https://sitegpt.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Playbook: Existing account chatbot setup > Create or update a SiteGPT chatbot inside an authenticated SiteGPT account. Use this playbook when the human provides a SiteGPT token/profile, says they already use SiteGPT, or asks to create/update a chatbot inside their current account. The goal is to configure a production account safely. Read existing state before overwriting behavior. ## 1. Verify account context ```bash theme={null} sitegpt whoami --json ``` If unauthenticated: ```bash theme={null} sitegpt login ``` If the user mentions a named environment or account: ```bash theme={null} sitegpt profiles list sitegpt profiles use ``` ## 2. Clarify purpose and scope Before configuring, know whether this is: * A new chatbot in the account. * An update to an existing chatbot. * A full rebuild. * A narrow change, such as adding knowledge or updating instructions. Ask or infer purpose: ```text theme={null} What should this SiteGPT chatbot optimize for: customer support, marketing/site guide, lead generation, docs/help, onboarding, or a mix? ``` For an existing chatbot, list before mutating: ```bash theme={null} sitegpt chatbots list --json sitegpt chatbots get --json ``` ## 3. Create or select the chatbot For a new chatbot: ```bash theme={null} sitegpt chatbots create " Support" \ --description "Answers questions about products, pricing, docs, and support." \ --json ``` For an existing chatbot, use the provided or discovered ``. Do not create a duplicate unless the user asked for a new chatbot. ## 4. Inspect the website Use raw HTML for structured signals and browser/fetch tools for prose. Capture brand/product name, value proposition, important URLs, support/sales email, sitemap, tone, brand colors, and icons. Do not invent company facts, pricing, policies, emails, or guarantees. ## 5. Add or update knowledge carefully For a new chatbot, add the best source, usually sitemap: ```bash theme={null} sitegpt knowledge sitemap add \ --chatbot \ https://example.com/sitemap.xml \ --only-main-content true \ --json ``` For an existing chatbot, list current knowledge first: ```bash theme={null} sitegpt knowledge documents list --chatbot --json sitegpt knowledge sync-jobs list --chatbot --json ``` Then add missing sources. Do not delete, disable, resync all, or bulk update existing knowledge unless the user asked. Plan-gated sync/scan frequencies may be downgraded by the API. Surface warnings to the user. ## 6. Update brand settings safely For a new chatbot, apply extracted brand colors and upload icons. ```bash theme={null} sitegpt settings appearance update \ --chatbot \ --title " Support" \ --welcome "Hi! I can help with questions." \ --placeholder "Ask about ..." \ --brand-color "#0F766E" \ --brand-text-color "#FFFFFF" \ --link-color "#0F766E" \ --icon-position RIGHT ``` For an existing chatbot, read current settings before changing them: ```bash theme={null} sitegpt settings appearance get --chatbot --json sitegpt settings general get --chatbot --json ``` Preserve existing brand choices unless the user asked for a refresh. Upload local image files only: ```bash theme={null} sitegpt icons upload --chatbot bot /tmp/sitegpt-logo.png sitegpt icons upload --chatbot chat-bubble /tmp/sitegpt-logo.png ``` ## 7. Configure persona without clobbering existing behavior For a new chatbot, create and activate one strong default persona: ```bash theme={null} sitegpt personas add --chatbot --title " support specialist" --file /tmp/sitegpt-persona.md --json sitegpt personas use --chatbot ``` For an existing chatbot, list current personas first: ```bash theme={null} sitegpt personas list --chatbot --json ``` Add a new persona or update only with approval. Do not silently replace a carefully tuned production persona. ## 8. Configure instructions deliberately For a new chatbot: ```bash theme={null} sitegpt instructions add \ --chatbot \ --title "Grounded assistant" \ --file /tmp/sitegpt-instructions.md \ --temperature 0.3 \ --json sitegpt instructions use --chatbot ``` For an existing chatbot: ```bash theme={null} sitegpt instructions list --chatbot --json ``` Preserve active instructions unless the task is to improve or replace them. ## 9. Add or refine starters and followups For a new chatbot, add 3-5 visitor-focused starters and followups. ```bash theme={null} sitegpt starters add --chatbot --title "What does do?" --message "What does do?" --json sitegpt starters add --chatbot --title "Pricing" --message "Tell me about pricing and plans." --json sitegpt followups add --chatbot --title "Contact support" --message "How can I contact support?" --json ``` For an existing chatbot, list current prompts first: ```bash theme={null} sitegpt starters list --chatbot --json sitegpt followups list --chatbot --json ``` Add missing prompts or improve stale ones. Do not remove existing prompts without approval. ## 10. Configure lead and support settings with care For lead generation: ```bash theme={null} sitegpt settings lead-form update \ --chatbot \ --enabled true \ --collect-name true \ --collect-email true \ --notification-email sales@example.com ``` For customer support: ```bash theme={null} sitegpt settings general update \ --chatbot \ --support-email support@example.com ``` For existing chatbots, read current lead/human-support settings before changing routing or notification emails. ## 11. Verify and handoff ```bash theme={null} sitegpt chatbots get --json sitegpt knowledge documents list --chatbot --json sitegpt personas list --chatbot --json sitegpt instructions list --chatbot --json sitegpt starters list --chatbot --json sitegpt followups list --chatbot --json sitegpt dashboard --chatbot ``` Test with realistic visitor messages: ```bash theme={null} sitegpt messages send --chatbot "What does this company do?" --json sitegpt messages send --chatbot "How much does it cost?" --json sitegpt messages send --chatbot "How can I contact support?" --json ``` Final report should include chatbot ID, dashboard link, knowledge sources, persona/instructions changes, starters/followups, settings/icons, warnings, and install snippet if requested.