How to Add an AI Chatbot for WordPress Website Using Repligram (Step-by-Step)

I'll be honest — when I first started looking for an AI chatbot for WordPress, I expected the process to be a nightmare. Like, either you're paying a developer $2,000 to build something custom, or you're installing some janky plugin that breaks every time WordPress updates.

Repligram is neither of those things. It’s a platform where you build a chatbot, train it on your actual content, and drop it onto your site with literally one script tag. I've been through the whole setup and I want to walk you through it properly — not just the steps but the logic behind them, because once you understand how Repligram thinks about things, the whole process makes way more sense.

Grab a coffee, this is going to be a thorough one.

First, Let's Talk About Why This Actually Matters

Most WordPress sites have a problem that nobody talks about enough. Visitors land on your site, they have a question — could be about pricing, could be about how something works, could be the simplest thing in the world — and there's no good way for them to get a fast answer.

Your contact form takes 24 hours. Your FAQ page requires them to know what to search for. Live chat only works if someone's manning it. And honestly? If a visitor can't get an answer in like 30 seconds, a huge portion of them just leave. They're not being impatient, thats just the reality of how people use the web now.

An AI chatbot for WordPress solves this in a pretty elegant way. It’s there 24/7, it understands natural language (so people can just ask the question the way they'd normally phrase it), and if you set it up right, it pulls answers from your actual content instead of just making stuff up.

That last part is the whole ballgame, honestly. A chatbot that hallucinates answers is worse than no chatbot at all. Repligram handles this with something called RAG — Retrieval Augmented Generation — which is a fancy way of saying it searches your uploaded documents and web pages first, then uses that to formulate an answer. We'll get into how to set that up properly.

What Repligram Actually Is (Quick Overview Before We Dive In)

Before jumping into setup steps, let me explain how Repligram is structured because it honestly helps everything else click.

There are three layers. Your account is at the top — thats your login, your billing, your subscription plan. Inside your account you create teams, which are basically workspaces. And inside each team you create chatbots.

Each bot is its own thing with its own settings, its own knowledge base, its own appearance, and its own embed code. You can have multiple bots per team which is useful if you, say, run an ecommerce site and want one bot for product questions and another for shipping and returns. Or if you manage WordPress sites for multiple clients — each client gets their own team, clean and separate.

The structure sounds more complicated than it is. In practice you'll probably create one team, one bot, and you're done. But knowing the structure means you won't be confused when you see the word "team" scattered all over the dashboard.

Okay, lets actually do this.

Step 1: Sign Up and Get Into the Dashboard

Go to repligram.com, hit Sign Up, and create your account. Standard stuff — email, password, confirm your email if it asks. Once you're logged in you land on the main dashboard.

One small suggestion: use an email address you actually check. Repligram sends notifications when conversations happen and when you're getting close to plan limits, and those are actually useful to see in real time.

Step 2: Create a Team

You'll need a team before you can do anything else. Think of it as a folder or a workspace that holds everything together — your bots, your conversations, the colleagues you want to give access to.

Look for the team switcher in the sidebar, usually near the bottom. If you don't have a team yet, there'll be an option to create one. Give it a name — your business name, your website name, whatever makes sense to you.

Here's the thing about teams that's worth understanding: all the navigation items in the app — chatbots, conversations, members — are scoped to whatever team you have active. So if you switch teams, you're essentially in a completely different workspace. For most people this doesn't matter much because they only have one team. But if you do end up managing multiple sites through Repligram, you'll appreciate that things don't bleed across into each other.

Step 3: Create Your Chatbot

Inside your team, go to the Chatbots section and create a new one. Three things to fill out here and none of them should be treated as throwaway fields.

The first is your business name. Use your actual brand name. This is part of how the AI understands whose voice its supposed to be speaking in.

The second is category — pick whichever option best describes your business type. E-commerce, SaaS, professional services, whatever. It helps the model understand what kind of questions are likely to come in.

The third is the description, and this one genuinely matters more than people give it credit for. Don't write two words and move on. Write a real description of what your business does and what you actually want the chatbot to help visitors with. Something like: "We make accounting software for small businesses. This chatbot helps users understand our pricing tiers, troubleshoot common login and billing issues, and navigate our features."

The more specific that description is, the better the AI calibrates itself to your use case right from the start. You can tweak it later but starting with a good description saves you a lot of "why is the bot being weird" troubleshooting down the line.

After creation you'll see a bunch of tabs — Settings, Knowledge, Customize, FAQs, Install, and Conversations. We're going to touch each of the important ones.

Step 4: The Knowledge Base (Don't Skip This, Seriously)

This is genuinely the most important part of the whole setup, and its where most people either really nail it or kind of phone it in and then wonder why their bot isn't that useful.

Click into the Knowledge tab. This is where you add the content the bot draws from when answering questions.

Here's the quick explanation of how it works: Repligram uses RAG, which means when somebody asks your chatbot a question, the system searches your uploaded documents and URLs for the most relevant pieces of information, pulls those chunks, and feeds them to the AI to construct an answer. This is fundamentally different from just asking ChatGPT something — instead of the model improvising from its training data, it's working from your specific material.

Why does that matter? Because it means your bot will quote your actual pricing, reference your actual policies, explain your actual product features. It won't make things up or answer with generic information that has nothing to do with your business.

Uploading files

Repligram accepts PDFs and Word documents (DOC/DOCX). Good things to upload: product manuals, onboarding guides, your terms of service, pricing breakdowns, internal support documentation, anything that has information a visitor might need.

The size limit for uploads depends on your plan. Check Billing & Plans in your dashboard if you're not sure what your limit is. Starter, Pro, and Enterprise tiers have different limits on both the number of sources you can add and how large each file can be.

The one piece of advice I'll hammer on here: do not just bulk upload everything you've got. A focused, well-organized 20 page document will outperform a 400 page monster PDF where half the content is outdated or irrelevant. The bot learns from what you give it — garbage in, garbage out basically. Take an hour to audit what you're uploading and you'll have a much better bot.

Adding URLs

You can also point the bot at specific pages on your website. Your help center, your features pages, your "how it works" section — these are all fair game. Add URLs that actually contain useful answers, not just navigation pages or contact forms.

One thing I've seen people do is add their homepage URL thinking that covers everything. It doesn't. The homepage is usually just marketing copy. What you want are the pages that actually explain things — the deep-dive feature pages, the support articles, the detailed FAQ sections. Be intentional about which URLs you add.

Once your sources are in, the system indexes them automatically. You don't have to do anything to trigger that — just add them and give it a few minutes.

Step 5: Make It Look Like Your Site

Open the Customize tab. You'll find options to change the widget colors, set the launcher position (bottom-right or bottom-left corner), and depending on your plan, adjust the bot's name and avatar.

Honestly don't skip this step. A chat widget that looks completely out of place on your site creates a subtle sense of distrust in visitors — like the whole thing feels bolted on. Spend ten minutes matching your brand colors and it instantly feels more native.

One thing thats actually nice: when you save changes here, they apply to your live embed automatically. You don't have to update any code. Just save, refresh the page on your site, and the changes are there.

Step 6: Installing the Widget on WordPress

Okay this is the part everyone wants to get to. Head over to the Install tab inside your chatbot. You'll see a script tag already populated with your bot's specific ID and your site's origin. It looks something like this (yours will have real values, not placeholders):

<script
src="https://repligram.com/widget.js"
data-bot-id="your-bot-id-here"
data-origin="https://yourwebsite.com"
async>
</script>

Copy that exactly as it appears in your dashboard. Don't retype it, don't edit the values — just copy the whole thing.

Now you need to get this into WordPress. Three ways to do it depending on your comfort level.

The plugin method (recommended for most people)

Install a plugin called Insert Headers and Footers — its free and its basically the standard tool for this kind of thing. After installing it, go to Settings → Insert Headers and Footers in your WordPress admin. Paste the Repligram script into the Footer Scripts box and save.

Thats it. The widget now loads on every page of your site. This method is my recommendation because it doesn't touch your theme files, it survives theme updates, and any non-developer on your team can manage it.

The functions.php method

If you prefer to handle things in code, go to Appearance → Theme File Editor and open functions.php. Add this at the bottom:

function add_repligram_widget() {
// Paste your exact Repligram script tag here
// Replace bot ID and origin with your actual values from the Install tab
?>
<script
src="https://repligram.com/widget.js"
data-bot-id="your-bot-id-here"
data-origin="https://yourwebsite.com"
async>
</script>
<?php
}
// Hooks into wp_footer so it loads on every page, right before </body>
add_action( 'wp_footer', 'add_repligram_widget' );

This is clean and works well. The downside is if you switch themes you'll need to re-add this to the new theme's functions.php. If you're using a child theme (which you should be) then its fine — child theme files survive parent theme updates.

Directly in footer.php

You can also open your theme's footer.php file and paste the script just before the </body> closing tag. Works fine but it'll disappear if you ever update or change your theme, so its the least future-proof option of the three.

One thing that trips people up: the data-origin value

The data-origin in your embed script needs to exactly match the domain where your WordPress site runs. So if your site is https://mywebsite.com, that's what goes in data-origin — not http://mywebsite.com without the S, not https://www.mywebsite.com unless thats actually your canonical URL. A mismatch here will cause the widget to not connect properly and you'll sit there thinking the installation is broken when really its just a URL formatting thing. Double check this before troubleshooting anything else.

For local development, use your localhost address including the port number, like http://localhost:8080.

Step 7: FAQs — the Consistency Layer

The FAQs tab is something a lot of people gloss over and they're missing out. Here's the difference between FAQs and the knowledge base: the knowledge base is for depth and detail, long answers pulled from documents. FAQs are for precision and consistency, short answers that need to be stated the exact same way every time.

Pricing is the perfect FAQ entry. You don't want the bot sometimes saying "around $29" and sometimes saying "starts from $25 per month" because it found slightly different wording in two different documents. Write a FAQ entry for your exact pricing and it'll always say that, word for word.

Same for refund policies, key feature descriptions, anything where the specific wording matters. FAQs are also really easy for non-technical people on your team to maintain. Your support manager doesn't need to mess with PDF uploads — they can just open the FAQ section and update an answer directly. That's a big deal once more people are involved in keeping the bot accurate.

Step 8: Visitor Authentication Settings

In the Settings tab, there's an option for how visitors identify themselves before chatting. You've got a few modes, and which ones are available depends on your plan.

Anonymous lets people start chatting instantly — no name, no email, nothing. Zero friction, maximum engagement. Good for sites where your priority is getting visitors to interact.

Email collection means the widget asks for an email address before the conversation starts. I actually really like this option for most business sites. Your visitor gets help, you get a contact. Its essentially lead generation that happens automatically as a side effect of providing support. The visitor doesn't see it as annoying because they're getting value immediately — they ask their question, they get their answer, and you have their email.

Login-required means the visitor must already be authenticated on your site to access the chat. This makes sense for member areas, customer portals, SaaS app dashboards — places where the conversation might involve account-specific information.

Step 9: Review Conversations (the Part That Makes It Actually Good Over Time)

Once your widget is live, visitor conversations start appearing in the Conversations section — you can see all of them at the team level, or filter to a specific bot inside that bot's own tab.

Check this regularly. Weekly at minimum when you're starting out. Here's what you're looking for specifically.

Questions the bot fumbled or gave a weak answer to — these are your knowledge base gaps. Find the document or page that covers that topic and add it. If you don't have that content written anywhere, thats a signal you need to create it.

Questions that keep appearing over and over — turn these into FAQ entries. The bot will handle them more reliably with a dedicated answer than by hunting through the knowledge base every time.

Anything where the bot seemed to misunderstand the intent of the question — this might mean your bot description needs tightening. Go back to Settings and make the description more specific about what kinds of questions the bot is there to handle.

The bots that actually serve visitors well aren't the ones set up most perfectly on day one — they're the ones whose owners kept checking conversations and closing the gaps. Give it 20 minutes a week and you'll have a measurably better bot within a month.

Running Multiple Bots (If You Need It)

Worth mentioning quickly: you can have multiple chatbots per team, each with its own knowledge base and embed code. Useful for larger sites with genuinely different content areas — like a WooCommerce store with one bot for product questions and another for order and delivery support — or for multilingual sites where you want each bot trained on content in the right language.

Each bot has its own script tag from its own Install tab, so you control exactly which pages show which bot. Just install the relevant script on the relevant pages, or use conditional logic in your functions.php to load different scripts on different page templates.

Voice Support

If your plan includes it, visitors can speak their questions and get spoken replies back. When its enabled the voice controls show up in the widget automatically — you don't have to configure anything extra. If you're not seeing voice options in your dashboard, that feature isn't in your current plan.

The browser will ask visitors for microphone permission the first time they try to use voice. Worth knowing so you're not surprised if visitors mention seeing a permission popup.

The Stuff That'll Bite You If You're Not Careful

Let me quickly flag the mistakes I see people make, because they're all avoidable.

Uploading stale documentation is probably number one. Your bot answers based on whatever is in its knowledge base — if that information is outdated, the answers will be outdated too. Build in a quarterly review of your knowledge sources.

Being lazy with the bot description during setup. I said it earlier and I'll say it again: that description field actively shapes how the bot behaves. Write a real one.

Not checking Conversations at all. You're flying blind if you never look at what visitors are actually asking. The data is sitting right there.

And the data-origin mismatch thing. Its a small thing that causes a disproportionate amount of "why isn't this working" frustration. Always check it first.

That's Pretty Much It

Setting up an AI chatbot for WordPress used to be a real engineering project. With Repligram its genuinely a one-afternoon job for most sites. The technical lift is low — one script tag, no backend to manage, no API keys to wrangle.

The real work is in the content. Getting your knowledge base right, writing solid FAQ entries, and spending a little time each week reviewing what visitors are actually asking. Thats where the quality comes from, not the setup.

Go to repligram.com and get started. If you're running into something specific with your WordPress setup — particular theme, page builder, multisite config — drop it in the comments and let's figure it out together.

Based on Repligram's official documentation. Plan features and limits may change, so always check current details in your dashboard.