Create your first bot

The AskAnyDocs bot creation wizard helps you build a documentation assistant without configuring every setting manually. It collects the basic company details, lets you add knowledge sources, and gives you a preview before the bot becomes part of your workspace.

When to create a new bot

Create a separate bot when the audience, content, or website placement is different. For example, you might use one bot for public product documentation and another for internal onboarding documents. Keeping bots focused makes answers easier to test and reduces the chance that unrelated content affects a visitor response.

Good reasons to create a new bot include:

• launching support chat for a new website or product
• separating public documentation from internal documents
• testing a new knowledge base before replacing an existing assistant
• serving different brands, languages, or customer segments

Step 1: Basic information

The first step asks for company or bot information. You can either provide a company website or continue without one.

If you enter a website, AskAnyDocs tries to detect useful details automatically, including company name, language, description, brand color, starter question, and logo. This saves time and gives the widget a sensible first draft.

If you continue without a website, enter the company name manually. The wizard uses that as the initial bot name, and you can edit the name later in bot settings.

Use a descriptive bot name. A name such as AskAnyDocs Support Assistant or Product Docs Assistant is easier to recognize later than a generic name like New Bot.

Step 2: Resources

Resources are the content the assistant uses when answering questions. The wizard supports several resource flows:

• website discovery for public pages
• sitemap discovery for structured page lists
• URL lists for exact page selections
• file uploads for documents that are not published as web pages

Choose the cleanest source for each type of content. If your help center has a sitemap, start with that. If you only need five exact pages, use a URL list. If a policy exists only as a PDF, upload it as a file.

Do not add every source at once unless you already know the content is clean. A focused first index is easier to troubleshoot.

Step 3: Preview and settings

The final step shows the bot name, logo, starter question, and widget color. The live preview updates while you edit these fields, so you can check how the assistant will look before saving.

Review the starter question carefully. It should match the visitor intent you expect on your website, for example:

• How do I upload my documents?
• What can this product help me with?
• Can you explain the pricing plans?

Avoid vague starters such as How can I help? if your site has a more specific use case.

After completion

When you finish the wizard, the bot is finalized and you are redirected to the bot workspace. From there you can:

• add or remove resources
• review indexing status
• edit widget appearance
• configure allowed domains
• preview answers with real questions
• copy the embed snippet

Before publishing, ask the bot the same questions a customer would ask. If the answer is weak, update the source document or add a more specific page, then reindex the content.

Practical checklist

Before you embed the bot on a production website, confirm that:

1. the bot has a clear name and brand appearance
2. the main product or support content is indexed
3. the assistant answers your most common visitor questions
4. fallback or escalation behavior is configured if needed
5. the website domain is allowed
6. the widget snippet is copied from the current bot settings page

Related articles