Most WordPress AI plugins sell you the same thing with a different skin. A floating bubble. A text field. A confident answer. Maybe a link to a page the visitor still has to open, filter, and finish alone.
That is fine when someone asks “what is your return window?” It falls apart when they say “find trail shoes in size 43 and add one to my basket.”
One job is answering. The other job is doing. Most plugins only ship the first. Generatify ships both: an AI Page Agent that navigates and acts on your site, and a Helpdesk Agent that answers from your pages, products, and policies. They are not the same feature with two labels. The docs treat them as different tools for different sites.
If you already pasted ChatGPT into a page and called it support, we have been there. That path has limits. We covered why in Don’t paste ChatGPT into WordPress. This post is about the next step: putting agents on the front end that actually match how people use a store or a content site.
The problem with “answer-only” AI on WordPress
A chat bubble that only answers creates three quiet failures.
It describes the site instead of using it. The visitor still has to leave the widget, find the menu, apply the filter, pick a variant, and hit Add to cart. You paid for AI and got a talking FAQ.
It sounds smart on topics it does not know. Generic models invent shipping rules, invent stock, invent policies. Grounding in your content helps. Acting on the live page helps more when the task is navigation, not explanation.
It trains visitors to wait for text when they wanted an outcome. On a WooCommerce store, the outcome is a filtered catalog or a filled cart. On an app-like membership site, the outcome is the right screen. A paragraph is not that outcome.
Generatify’s product page puts this bluntly: a typical front-end agent is a bubble that answers questions. Generatify Pro’s front-end agent navigates and acts on your site. That is the gap this post is about.
Two agents, two jobs (from the real docs)
Open Generatify > Settings > Agents and you get three visitor-facing pieces: the AI page agent, the AI helpdesk agent, and browser AI tools (WebMCP). Start with the first two.
AI Page Agent: the copilot that works the site
The Page Agent is a floating copilot. A visitor opens it, says what they want in plain language, and the agent works through your pages to do it.
- Finds the page they actually needed
- Fills forms and adds to the basket on request
- Shows every step, and lets them stop at any point
Docs fact that surprises people: the Page Agent is on by default. Check your front end before assuming it is off. Position options are bottom-left, bottom-right, top-left, or top-right. It defaults to the left so it does not collide with the helpdesk, which defaults to the right. You set one button color; icon contrast is derived automatically.
No AI provider key is required for the Page Agent. The work runs in the visitor’s browser. That matters for cost and for “can I try this on free?”
AI Helpdesk Agent: answers from your content
The Helpdesk Agent is a support widget with three tabs: home, message, and help.
- Home tab: greeting, tagline, and a button into the message tab. Pro adds up to three popular topics.
- Message tab:
contact(email form) orconversation(live AI chat). Conversation needs Pro and a connected provider. Free installs should use contact mode. - Help tab: links to your own articles, not content stored inside the plugin.
Answers come from your pages, products, and policies. Pro lets you pick up to three pages whose full content the agent can read, plus custom instructions for language, tone, and what to refuse. Shipping and returns, pricing, and a getting-started page usually beat three deep feature pages. If you do not know, say so and offer the contact form.
We already walked the helpdesk setup path in How to set up an AI helpdesk on your WordPress site in 2026. This post focuses on when helpdesk is the right tool versus when the Page Agent should lead.
The comparison table that settles arguments
| Page agent | Helpdesk agent | |
|---|---|---|
| Answers questions | Indirectly, by navigating | Directly |
| Acts on the site | Yes | No |
| Needs a provider | No | Only in conversation mode |
| Best for | Complex sites and stores | Sites with repeat support questions |
If you only want one: choose the helpdesk for a content or service site, and the page agent for a store or an app-like site where people are trying to accomplish something rather than learn something.
When the Page Agent fits (and when it does not)
Strong fit: WooCommerce and catalog-heavy sites. Someone says “find trail shoes in size 43, add one to my basket.” The agent opens shop, applies the filter, chooses the product, adds to cart, and shows each step with a Stop control. That is not a paraphrased FAQ. That is the store working.
Strong fit: sites that feel like apps. Multi-step flows, filters, forms, and dashboards. If the visitor’s goal is to get to the right screen and finish the action, navigation beats explanation.
Weaker fit alone: pure content or service businesses. If most inbox volume is “what is your pricing?” and “how do refunds work?”, the Helpdesk Agent plus solid help articles is the right default. You can still leave the Page Agent on for “take me to the pricing page,” but conversation mode is where the support load drops.
Do not run both blindly on a phone. Keep them on opposite corners. Audit cookie banners, chat widgets, and back-to-top buttons on a real phone before you ship.
When the Helpdesk Agent fits
Use helpdesk when the same questions hit your inbox every week, you want popular topics on the home screen, you need a clean path from an AI answer to a human contact form, and you care about tone, refusal rules, and grounding in a few critical pages.
Start in contact mode even if you have Pro. It works on free, emails your admin address by default, and shows what conversation mode should be trained to answer. Then connect a provider, flip to conversation, spend your three knowledge-page slots carefully, and write instructions that force honesty over vibes.