If you run a WordPress agency, you already have the hard part: clients who pay you monthly to look after their sites. Care plans, maintenance retainers, whatever you call them. The chatbot is a line item you add to plans that already exist, sold to people who already trust you.
That is a very different business from cold-selling AI to strangers, and the math reflects it.
The install is one script tag
No plugin required. The embed is a single script tag, and on WordPress you have three ways to add it: paste it into the theme's footer via the customizer, drop it in with a snippets plugin like WPCode, or push it through Google Tag Manager if the site already runs GTM.
Two minutes per site, and it survives theme updates if you used a snippets plugin instead of editing theme files directly. (A dedicated WordPress plugin is on our public roadmap, but honestly the script tag is not the bottleneck.)
The bot is domain-locked to the client's site, so the embed key being visible in page source does not let anyone run it elsewhere.
What changes in your care plan pricing
A typical WordPress care plan in Pakistan runs ₨5,000 to ₨15,000 a month for updates, backups, and small fixes. Internationally, $50 to $150. The ceiling is low because maintenance is invisible: when you do it well, the client sees nothing.
A chatbot is the opposite. Every week it puts something in front of the client they can count: captured leads with names and phone numbers. Agencies I know add ₨8,000 to ₨15,000 (or $50 to $99) per site for "AI chat with monthly reporting" and it is the easiest line on the invoice to defend, because the client can log into their own portal and watch it work.
Ten care plan clients, six take the add-on at ₨10,000: that is ₨60,000 a month of new recurring revenue on sites you already manage. The platform underneath costs ₨20,000 flat on the Agency plan regardless of how many clients you add. I broke down the retainer pricing in detail separately.
The training content is already in your hands
You built these sites. You have the service pages, the menus, the product exports. Setting up the knowledge base for a site you manage takes under an hour, and the training process is the same loop every time: load the content, watch the unanswered questions for two weeks, fill the gaps.
For WooCommerce stores, export the product CSV and import it directly. The bot answers price and availability questions with the actual catalog data and shows product cards with images and links.
Each client gets their own portal
The part clients remember from the pitch is the login. Their own branded dashboard with their conversations, their leads, their stats. Nobody else's data. On the white-label tiers it carries your agency branding, so the product reads as yours.
It also kills the monthly "any update?" email, because the client checks the numbers themselves. For a ten-site agency that is hours of reporting you stop doing by hand.
How to roll it out
Do not announce it to everyone at once. Pick the two clients whose sites get the most traffic, set up bots trained on their content, and run them for two weeks. Then send each client their portal login and the lead list with a one-line note: "this is what your site collected while you were closed."
Convert those two, take a screenshot of the leads table (with permission), and that screenshot sells the other eight.
Frequently Asked Questions
Try it on your next client project
Free plan — no credit card required.