No. It reads the BetterDocs docs custom post type directly from WordPress, including the doc_category and doc_tag taxonomies. There is no CSV upload, no scheduled sync, and no separate dashboard. Articles, revisions, and FAQ blocks flow into vector storage on save, so the bot answers from your live library at all times.

Yes. Updates re-index on save so the bot answers from the current revision. Deletes drop the article from the vector store. If you publish a fix at 2pm, the bot is using the corrected content by 2:01pm. There is no manual re-import step, which is what makes a help-center bot worth running long-term rather than just at launch.

Yes. Display conditions and per-bot scoping let you bind a bot to a specific doc_category. A getting-started bot on /docs/setup/ never tries to answer billing questions, and a billing bot on /docs/pricing/ never invents a setup step. You can also combine category scoping with role and login state for finer control over who sees what.

Bring your own key for OpenAI, Anthropic, Google, or OpenRouter. SleekAI handles routing the request, attaches the retrieved doc context, and forwards to whichever model you pick. Vector storage runs on OpenAI Files. Mixing providers is fine, so a small team can use a fast, cheap model for chat and a stronger model for harder questions through routing rules.

Hundreds of thousands of words fit through OpenAI Files vector storage with up to 1GB per file. That comfortably covers most BetterDocs libraries up to several thousand articles. For larger sets, multibot lets you split by doc_category across several files. Practical retrieval quality usually matters more than raw size, so monitor citation accuracy as the library grows.

Yes. The bot can include the doc title and link in every answer, with citation behavior tunable through the prompt. Citations are essential for help-center deflection because they let users verify steps before trying them, which catches the rare bad reply before it becomes a support ticket. Disable citations only when you have a strong reason; defaults are on for good reason.

The bot falls back to the prompt's escalation path, which usually means linking to a contact form or live agent. SleekAI is grounded retrieval, not creative writing; if no relevant doc retrieves, it should not invent steps. The conversation log captures these moments, and that list is the cleanest gap-analysis your docs team will get for free.

Yes. They serve different needs. BetterDocs's instant answer search is excellent for users who already know the article title, while SleekAI handles full-question, conversational queries where the user describes a problem in their own words. Run both. Search owns navigation, the chatbot owns conversation, and visitors pick whichever feels right for the question they are trying to answer.