Chatbot Builder Guide: Launch a Custom AI Chatbot Trained on Your Content

# Chatbot Builder Guide: Launch a Custom AI Chatbot Trained on Your Content

Most website chatbots fall into one of two traps: they are too generic to be useful, or they require a developer and three weeks of setup time. Vincony's Chatbot Builder sidesteps both problems. You define the bot's personality, feed it your knowledge sources, customise the widget to match your brand, and get an embed snippet ready to paste into any page — all without writing a single line of code.

This guide is a concrete walkthrough of the builder UI at /os/chatbots. If you want the conceptual background on why AI chatbots matter for your business, our companion article covers that ground. Here we focus entirely on what you click, what you type, and what you get at the end.

---

How the Chatbot Builder Works

Every chatbot you create in Vincony lives in the chatbots table tied to your account. When a visitor on your site sends a message, the widget calls the chatbot-respond edge function, which combines your system instructions, your data sources, and the ongoing conversation history to generate a contextual reply.

You can have multiple bots — one per product line, one per language, one for support and one for sales — and each is independently configured, deployed, and tracked.

The full lifecycle has four stages:

• Create — name the bot, write its persona and rules
• Train — add URLs or file references as knowledge sources
• Customise — set the widget colour, header text, and greeting
• Deploy — copy a Script or Iframe snippet and paste it into your site

---

Step 1 — Create a New Chatbot

Open the Chatbot Builder from the left nav inside your Vincony workspace. If you have no bots yet, you will see an empty state card with a Create Your First Chatbot button. Click it — or click the New Chatbot button in the top-left corner — to open the creation dialog.

Fill in the following fields:

• Name (required) — the internal label you will see in your bot list. Something like "Support Bot" or "Product FAQ" works well. Visitors never see this name.
• Description (optional) — a one-line reminder of what the bot is for. Useful when you have five or more bots and need to tell them apart at a glance.

Click Create to save and immediately move on to configuration, or set everything up in the dialog before saving — either workflow works.

---

Step 2 — Write Your System Instructions

The System Instructions field is the most important part of the whole setup. This is the "system prompt" that shapes every single reply the bot gives. The field accepts up to 4,000 characters, and the character counter at the bottom right lets you keep track.

Good system instructions typically include:

• Role and persona — "You are a friendly support agent for AcmeCo. You are helpful, concise, and professional."
• Topic boundaries — "Only answer questions about our SaaS product. If asked about competitors, politely decline."
• Tone rules — "Avoid jargon. Use plain English. Keep responses under four sentences unless a detailed explanation is genuinely needed."
• Escalation cues — "If the user asks to speak to a human, respond with: 'I will connect you with our team — please email support@acmeco.com.'"

Invest real time here. A well-written 300-word system prompt will make your bot noticeably more reliable than a one-sentence placeholder.

---

Step 3 — Add Knowledge Sources (Data Sources)

Below the system instructions you will find the Data Sources field. This is where you point the bot at the content it should draw on when answering questions.

Each line is one source. The builder auto-detects the type:

• Lines starting with http are treated as URL sources (your docs, your FAQ page, a public knowledge base article).
• Anything else is treated as a file reference (a filename or path you have stored elsewhere).

Practical examples of what to paste here:

• https://yourdomain.com/faq
• https://yourdomain.com/docs/getting-started
• https://yourdomain.com/pricing
• product-manual-v3.pdf

You can edit data sources at any time from the Edit dialog, so there is no pressure to get this perfect on the first pass. Start with your three or four most important pages and expand from there.

Pro tip: For Starter and higher plans, combining the Chatbot Builder with Second Brain gives you a structured way to curate and maintain the knowledge your bots draw from, rather than managing scattered URL lists.

---

Step 4 — Customise the Widget Appearance

Inside the same create or edit dialog, scroll down to the Widget Appearance section. Three controls let you match the chat widget to your brand without touching CSS:

These three fields handle the majority of visual customisation for most use cases. If you need deeper styling, you can wrap the Iframe snippet in a container div and apply your own CSS.

---

Step 5 — Test Before You Deploy

Once your bot is created, its card appears in the grid. In the top-right corner of each card you will see a row of icon buttons. Click the play icon (Test Chat) to open a live test panel on the right side of the screen.

The panel shows a real conversation thread — your bot's greeting appears first, then you can type any message and see how it responds. This calls the actual chatbot-respond function with your real configuration, so you are testing exactly what visitors will experience.

Run through your most common scenarios:

• Ask a question the bot should know from your data sources.
• Ask something off-topic and confirm it stays within its boundaries.
• Try an ambiguous question and check whether the answer makes sense.

If the replies are off, click the pencil icon (Edit) on the card, refine your system instructions or data sources, save, and test again. The iteration loop is fast — changes take effect immediately.

---

Step 6 — Copy the Embed Snippet and Go Live

When you are satisfied with the bot's behaviour, find its card and look at the Script / Iframe tab toggle near the bottom of the card.

• Script tab — click Copy Script to copy a one-line script tag. Paste it just before the closing body tag on your website. The bot widget will appear as a floating chat button in the corner of every page it is installed on.
• Iframe tab — click Copy Iframe to get an iframe tag instead. This is better when you want to embed the chatbot inline within a specific section of a page rather than as a floating overlay.

Both snippets reference your bot's unique ID and the hosted chatbot-respond endpoint, so there is nothing else to configure. Paste, save, publish — done.

You can also click the link icon on the card to copy the raw widget URL if you want to preview the widget in isolation or share it for review.

---

Step 7 — Monitor with Analytics and Conversation Logs

After the bot goes live, two feedback tools help you understand how it is performing.

Analytics badges on each card show the total message count and the last time the bot was active. This updates automatically as visitors interact with the widget.

Conversation Logs give you the full picture. Click View Logs on any card to open the logs dialog, which shows up to the 20 most recent conversations in reverse chronological order. Expand any conversation to read the full exchange — every user message and every bot reply is stored. This is invaluable for:

• Spotting recurring questions your system instructions do not handle well
• Identifying topics you should add to your data sources
• Catching edge cases before they frustrate a real customer

Check your logs weekly when a bot is new, then monthly once it has stabilised.

---

Managing Multiple Bots

As your library grows, a few management actions keep things tidy:

• Toggle active/inactive — the toggle icon on each card enables or disables the bot. An inactive bot still exists with all its configuration intact, but the embed endpoint returns no response. Use this to pause a bot without deleting it.
• Duplicate — the copy-plus icon creates an identical copy named "Bot Name (Copy)". This is the fastest way to create a variant — for example, a Spanish-language version of an existing bot — without starting from scratch.
• Delete — the trash icon opens a confirmation dialog before permanently removing the bot and all its configuration. Deletion cannot be undone.

---

Tips for Better Chatbot Performance

Keep system instructions focused. A bot that does one thing well beats a bot that tries to do everything. If you serve different audiences, create separate bots rather than cramming all the logic into one set of instructions.

Refresh your data sources after content updates. The bot uses the URLs you provided at configuration time. If your FAQ page changes significantly, open the Edit dialog and verify the listed URLs still reflect current content. For teams managing large knowledge bases, Connected Apps can help automate how fresh content reaches your workspace.

Use the greeting message to set expectations. Visitors make a snap judgment about whether the bot is worth engaging with based on the first message. Be specific: "I can answer questions about shipping, returns, and account setup" is far more inviting than a generic "Hello! How can I help?"

Match the accent color exactly. Pull the hex value directly from your brand guidelines or your website's CSS. A widget that looks like it belongs to the page gets significantly higher engagement than one that looks bolted on.

Plan for human handoff from day one. Add a line to your system instructions like "If the user wants to speak to a human or has a complaint, direct them to [your email or support URL]." The builder's config schema supports a humanHandoff flag — tell your bot when to use it.

---

Plan Availability

The Chatbot Builder is available on all paid plans. The number of bots you can create and the volume of messages they can handle scales with your plan tier. Free accounts can explore the builder interface but need at least a Starter plan to deploy an active embed. Pro and above unlock higher message volumes and priority response times, while Power and Business plans are suited to high-traffic sites and team workspace deployments where multiple collaborators need access to the same bot library.

Check the pricing page for current limits by tier.

---

What to Build Next

With your first chatbot live, consider these natural next steps:

• Connect it to a richer knowledge base via Second Brain, so the bot always draws from your curated, up-to-date content rather than raw URLs.
• Use Connected Apps to pipe in live data — product feeds, CRM updates, or support ticket context — that keeps bot answers current without manual maintenance.
• Build a second bot variant for a different audience segment or language and compare engagement across the two.

The Chatbot Builder is designed to grow with you. Start simple, test fast, and iterate based on the conversation logs. Your visitors will notice the difference.