How to connect free knowledge base help to a chat widget

The setup links two Chatref components: the knowledge base that holds your help content, and the website widget that visitors interact with. When a customer asks a question in the widget, the platform searches your knowledge base, finds the most relevant material, and generates an answer grounded in that source – all inside the chat window.

If you use a Knowledge Base Software to host your support docs, you can connect it directly without migrating content. Point Chatref at your existing URLs and sitemaps, or upload files directly. The widget then acts as a live front-end for that entire library, so every article you’ve written becomes a real-time answer engine on your site.

The widget bubble sits on every page where you place the snippet. It pulls its behavior – brand colors, welcome message, fallback rules – from the agent you configure. Behind the scenes, the platform keeps your knowledge base indexed and ready. No separate servers or caching layers to manage.

1. Create an account – Go to app.chatref.ai and sign up. Every new account receives $50 in free credit immediately; no credit card is required and the credit never expires. You can connect your knowledge base and go live entirely on that free balance.

2. Create an agent – From the dashboard, create a new AI agent (you can have as many as you need, even on the free credit). The agent is what the widget will talk through.

3. Feed it your knowledge base – Under the agent’s training section, upload the content that customers ask about: PDF manuals, help center URLs, sitemaps, or plain text. If your knowledge base already lives on a separate SaaS platform, just add its public URLs. The system crawls and indexes the text so answers stay true to your own documentation.

4. Configure the widget’s behavior – In the agent settings, set the primary color to match your brand and choose a greeting message. Turn on “Answer only from knowledge base” if you want to avoid any generic replies. Decide a fallback message for when no matching doc is found, such as “A team member will get back to you shortly.” You can also enable lead capture here.

5. Get the widget snippet – Navigate to the Embed tab. Copy the snippet (a couple of lines of JavaScript) that will place the chat bubble on your site.

6. Place the snippet on your website – Paste it just before the closing </body> tag on every page where you want the widget to appear, or use a global footer include. If your site uses a content security policy, add app.chatref.ai to the allowed origins so the widget loads correctly.

7. Test the connection – Open a page with the snippet, click the bubble, and type a question that matches your knowledge base content (for example, “How do I reset my password?”). The widget should return an answer drawn from your docs within a few seconds. The free credit covers the first few thousand responses, letting you validate the full flow at no cost.

Customers browsing your site see a small chat bubble in the bottom-right corner. Clicking it opens a conversation pane. The agent introduces itself with the greeting you set and waits for a question.

When a user asks something covered by your knowledge base, the response appears directly in the chat thread – often with a citation pointing to the source article. If multiple questions come in, the thread stays; it’s the same for every page on your domain because the snippet is site-wide.

If you’ve enabled human handoff, there’s a button or phrase users can use to request a live person. On your side, the chat appears in the shared inbox with the full conversation history, so your team can step in without asking the customer to repeat anything.

For visitors who don’t click the bubble, the widget stays unobtrusive. It doesn’t pop up automatically or interrupt unless you configure a proactive trigger (which the free credit plan fully supports).

Widget not appearing – Check that you pasted the snippet before </body> and that no ad-blocking extensions are blocking third-party scripts in your testing browser. Also verify the origin you’re testing (e.g., yourdomain.com) is in the agent’s allowed origins list.

Answers are off-topic or generic – The knowledge base may need better coverage. Re-upload the specific pages that address the question. If the agent is not restricted to knowledge base responses, turn on “Answer only from knowledge base” so it never pulls from a general model. Wait a few minutes after adding content for indexing to complete, then test again.

Blank or “I don’t know” responses – This often means the knowledge base has no document that matches the query closely enough. Check the fallback message you set. Consider rephrasing the same information in a dedicated FAQ upload, since the search works best when a clear, concise passage exists for the question. If you need multilingual answers, add versions of your content in those languages; the multilingual agent will route accordingly.

Widget loads but no agent replies – Confirm your account has a positive coin balance. Free credit starts at $50, but if all coins were consumed in testing, top up your balance through the billing page. The widget will continue to appear, but the agent only responds when the account has available coins.

What causes free knowledge base problems for Knowledge Base Software?

Free tiers often come with limits that break the knowledge base connection: expired trials, document-count caps, or content that gets deleted after inactivity. Even without those, a free knowledge base may not index quickly enough for real-time widget replies, leading to slow or irrelevant answers. When the knowledge base is stored in a separate, static tool and not natively integrated with the chat widget, customers get dead-end links instead of instant help – exactly what you’re trying to avoid.

How do I improve free knowledge base for Knowledge Base Software?

Keep your help content concise and action-oriented; long, unfocused pages make retrieval harder. Break documents into short FAQ entries. If your free knowledge base tool supports URL ingestion, point the widget directly at your live help center so it stays in sync as you edit articles. Finally, test the widget with real customer phrases – not the exact titles of your articles. Tune the fallback message and handoff rules so any gaps don’t leave users stranded.