How to Add an AI Chatbot Trained on Your Own Content to a WordPress Site (No Code)

A scripted chatbot is a flowchart wearing a speech bubble. It works until a customer asks something the tree does not contain — a shipping exception, a comparison, a policy buried in a PDF. Then the bot loops, dumps "contact us," or invents an answer.

A RAG-style chatbot works the other way around. You give it your existing material. When a visitor asks a question, the system retrieves the relevant passages and writes a reply from them. It can answer questions you never wrote a flow for, and it stays current as you publish. If the delivery policy is in the knowledge, it can handle "do you deliver to Salt Lake on Sunday if I order after 6?" You update the source instead of redrawing a tree.

The trade-off is honesty. A scripted bot fails loudly, because it has no path. A generated bot can fail quietly if it is allowed to guess. Prefer a tool that says it does not know, and offers a person, over one that always sounds confident.

What to feed it

Answers are only as good as the sources. Feed the bot what a good support person would open:

• Published pages and posts — about, shipping, returns, services, and booking instructions.
• Product data — names, prices, stock status, SKUs and categories.
• PDFs, office files and a clean price list — rate cards, menus, policy handbooks, a spreadsheet or catalogue.
• Past questions — old chats or a short Q&A list, in the phrasing people actually use.

Leave out drafts, internal cost sheets, unpublished discounts, staff records, and other people's personal data. If a document is half-public, split it first. A plugin that syncs published WordPress content is worth more than a one-off paste.

Languages your visitors actually type

People ask in the language they think in — Bangla, English, Hindi, Arabic — and they expect the reply in the same one. A bot that only answers in English will miss a large share of those questions.

Look for a bot that replies in the language the visitor typed, rather than a separate tree per locale. ChatNory, used in the walkthrough below, does that. It supports 11 languages, including Bangla, English, Hindi and Arabic.

Feed it sources in the languages you care about, or at least a clear canonical policy. A bot cannot invent your Sunday delivery rule in Bangla if that rule exists nowhere in the knowledge.

Human handover, WhatsApp, Messenger and Telegram

Some questions should never be left to a model: a complaint, a payment dispute, or anything the bot flagged as unknown. The useful pattern is live handover. Your team can step in; when a person starts typing, the bot steps aside so the visitor is not answering two voices at once.

Many customers never open your site widget. They already message you on WhatsApp, Messenger or Telegram. One chatbot, trained once, should answer in those channels. The WordPress plugin keeps site content in sync; the apps are connected in the product dashboard, not in wp-admin.

Check the plan before you promise this. On ChatNory, live chat and human handoff are on the Starter plan ($10 per month) and above. WhatsApp, Messenger and Telegram are on the Pro plan ($35 per month). Connect only channels you actually monitor.

Privacy, before you paste a site key

A chatbot that "knows your business" stores your business, and your visitors' questions, on someone else's server. Read the plugin disclosure and the product's privacy policy before you connect a site.

The ChatNory plugin sends the title, URL and plain text of published pages, posts and WooCommerce products (including price, stock, SKU and categories), plus your site address. Draft, private and password-protected content is not sent. Visitor messages and the page they are on go to the host. Nothing moves until you paste a server URL and site key.

Do not upload customer lists, invoices with personal data, or internal documents as training material. If visitors chat on your site, you are the controller of that conversation data. Use a host that lets you export or delete it, and mention the chat in your own privacy policy. Developers can limit the sync with the chatnory_post_types and chatnory_sync_limit filters if a custom post type should stay off the record.

Step by step: WordPress, no code

This uses ChatNory because it has a free WordPress plugin, a free plan, and it is built around training on your own content. The same checklist works with another host; only the setting names change.

1. Install the plugin. In wp-admin go to Plugins → Add Plugin, search for ChatNory, or install ChatNory – AI Chatbot, Live Chat & Customer Support from WordPress.org. Activate it (WordPress 5.8+, PHP 7.4+). You also need a ChatNory account, because the bot runs on a hosted model, not on shared hosting. The free plan is enough to try this.

2. Create the chatbot. Sign up at chatnory.com, create a chatbot, and give it a role and tone. Add sources the plugin will not sync: PDFs, a price list, Word or Excel files, or a short Q&A.

3. Connect the site. In the ChatNory dashboard open Settings → General → WordPress plugin and copy the Server URL and Site key. In WordPress go to Settings → ChatNory, paste both values, and click "Save & connect."

4. Ask it something awkward. The plugin trains the bot on published pages, posts and, if you use it, WooCommerce products. In a private window, ask what a real customer would ask, including one question you know is not documented. The right behaviour is "I don't know" plus a path to a human, not a guess.

5. Choose how it appears. Placement, devices and published state are set in the ChatNory dashboard, not by editing your theme. To embed the chat inside a page, use the shortcode [chatnory]. Optional attributes are height (default 560) and width (default 100%).

There is a free plan; paid plans start at Starter for $10 per month and Pro for $35 per month.

If ChatNory is not the right fit

Tidio is a strong choice if you want a familiar live-chat widget first, with automation and an AI layer on top, and you are happy in a large, established product.

Crisp is a shared inbox that also does chatbots. If your team already runs support from Crisp, adding a bot there is usually better than introducing a second inbox.

If the problem is "the bot should answer from our pages, PDFs and price list, in the language the customer typed," a content-trained tool with a WordPress sync is the shorter path. If the problem is "five agents need one shared inbox tomorrow," start with the helpdesk you will actually live in.

Before you publish, train the bot only on public content, test a question it cannot answer, and match handover and channels to your plan. Keep a human in the loop, and do not let the model bluff.

I'm D. Raju, founder of ChatNory, based in Kolkata.