Skip to main content
Back to projects

ChatBot for WordPress (WPBot)

Led development of a no-code, native WordPress chatbot plugin from concept to a widely-used product, at QuantumCloud.

Overview #

From January 2016 to December 2021, I led development of WPBot, a no-code, native WordPress chatbot plugin built at QuantumCloud. As Lead Developer, I was responsible for architecting the core plugin, ensuring it stayed genuinely no-code for non-technical site owners, and guiding the project from initial concept through to a public release on WordPress.org.

The Problem #

At the time, most chatbot options for WordPress site owners meant embedding a third-party JavaScript widget — separate accounts, separate dashboards, and data living outside WordPress entirely. Site owners who wanted a chatbot but weren't developers had no straightforward, native way to add one without touching code or trusting an external service with their visitor data.

The Solution #

WPBot was built as a fully native WordPress plugin: install it, configure automated responses and lead-capture flows through a WordPress-native admin screen, and it works — no external account, no separate dashboard, no code required. Core areas I owned as Lead Developer:

  • The plugin's core architecture and admin UX, keeping the no-code promise intact as features grew
  • Automated conversation flows for live-support-style interactions and lead generation/data collection
  • Guiding the plugin from initial concept through to public release and iteration based on real user feedback

Technology Stack #

Core PHP (OOP) for the plugin architecture, MySQL for storing conversation data and settings within WordPress's own database, and JavaScript for the front-end chat widget and admin configuration screens — all native to the WordPress plugin ecosystem, no external services required for the core experience.

Lessons Learned #

Keeping a genuinely non-technical audience's workflow "no-code" gets harder, not easier, as a plugin's feature set grows — every new capability is a design decision about whether it belongs in the visible UI or stays as an advanced/hidden option. That discipline is what let the plugin keep growing (it has since expanded significantly beyond the version I worked on, including AI-assisted response features) without losing the simplicity that made it useful in the first place.