Chatbot and Live Chat Modules for Drupal

Live-chat modules from drupal.org connect your site to a staffed chat box. Fine if someone is always there.

Universal widgets added through a block or a template hook work with any vendor, and read what is published rather than what is in your entities.

A native module connects the site to an assistant that trains on your content and, on Drupal Commerce, answers order-status questions live.

The distinction matters more on Drupal than on most platforms, because so many Drupal sites carry deep documentation, policy and programme content that visitors genuinely struggle to search.

What to check before you install anything

• Does it read your catalogue, or just your website? A crawler sees your product pages as text. A native module reads products, categories, prices and sale prices as data, which is what makes "is the blue one in stock" answerable.
• Can it answer order-status questions? It is the most common post-purchase message. If the extension cannot look an order up, every one of those becomes a ticket.
• How does it verify the customer? An order lookup that accepts an order number alone leaks data. It should require the email or phone on the order too.
• What happens when the AI does not know? The honest behaviour is to say so and offer a person, with your real availability hours.
• What triggers the bill? Seats, conversations, AI resolutions and message credits are four different meters. Pick the one that matches how your store actually gets busy.
• Which languages? If you ship internationally, the reply has to come back in the language of the question.

The module covers Drupal 10 and 11. Once connected, it trains on your published content, plus any PDFs, spreadsheets or extra URLs you add in your Vatdi dashboard. Answers are retrieved from that material rather than generated from general knowledge, and where your content does not cover a question, the assistant says so and offers a person instead of improvising.

On Drupal Commerce, order-status lookup is available through the module's route: the customer gives the order number plus the email or phone on the order, the second factor is checked, attempts are rate-limited, and the reply carries status, items and tracking.

Large Drupal sites usually have the answer to a visitor question somewhere — in a policy node, a programme page, a PDF from three years ago — and no realistic way for the visitor to find it. Site search matches words; it does not answer questions. That gap is where a retrieval assistant does its most useful work, and it is why the case on Drupal often has nothing to do with e-commerce.

Three patterns come up repeatedly. Public-sector and university sites answering eligibility and process questions from published policy. Membership organisations answering renewal, benefit and event questions. Documentation-heavy product sites answering "how do I" from their own handbooks.

In all three the honest behaviour matters more than the fluency: when the content does not cover a case, the assistant should say so and offer a person rather than produce a confident paragraph. Every conversation is graded 0 to 10 with plain advice, and the insights report lists unanswered questions, so the content team gets a ranked list of what to write next.

Sales-count best sellers are not available on Drupal — that ships on the OpenCart, WooCommerce, Magento and Shopware plugins. Product suggestions still work, ranked by relevance to the question rather than by units sold.

The assistant also never writes to your site: no node edits, no order changes, no refunds. It answers, captures leads, and hands over to your team with the full transcript.

1. Create a free Vatdi account and add your site domain.
2. Install and enable the module the way you install any contributed module.
3. Connect the site from the module's settings form; content sync begins automatically.
4. Upload documents that hold answers not published as pages.
5. Enable order lookup if you run Drupal Commerce, and test it against a real order.
6. Set agent hours, so the widget offers a person only when one is available.

The Drupal integration page has the full install detail.

Free covers 15 conversations a month with every feature on and no card. Starter is $4.49 a month for 150 conversations, which also removes the vendor badge, and Grow is $7.49 for unlimited conversations and unlimited knowledge items. Teammates are unlimited on every plan — useful for the multi-department teams that Drupal sites tend to have, where several people may need to answer without anyone buying seats.