Skip to main content
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

If unauthenticated:
If the user mentions a named environment or account:

​
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:
For an existing chatbot, list before mutating:

​
3. Create or select the chatbot

For a new chatbot:
For an existing chatbot, use the provided or discovered <chatbot-id>. 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:
For an existing chatbot, list current knowledge first:
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.
For an existing chatbot, read current settings before changing them:
Preserve existing brand choices unless the user asked for a refresh. Upload local image files only:

​
7. Configure persona without clobbering existing behavior

For a new chatbot, create and activate one strong default persona:
For an existing chatbot, list current personas first:
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:
For an existing chatbot:
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.
For an existing chatbot, list current prompts first:
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:
For customer support:
For existing chatbots, read current lead/human-support settings before changing routing or notification emails.

​
11. Verify and handoff

Test with realistic visitor messages:
Final report should include chatbot ID, dashboard link, knowledge sources, persona/instructions changes, starters/followups, settings/icons, warnings, and install snippet if requested.