Launching today

Cliedesk
An AI help desk that runs inside your WordPress admin
1 follower
An AI help desk that runs inside your WordPress admin
1 follower
Cliedesk is a complete help desk built as a WordPress plugin: shared inbox, live chat, help center and customer portal in one place. An AI agent answers customers and can act on their WooCommerce orders, while a copilot drafts every reply for your team. It's for WordPress and WooCommerce stores that don't want support data living in another SaaS: tickets stay in your own database, and the AI runs on your own API key.









Free Options
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hey Product Hunt,
Every WooCommerce store owner knows one support ticket by heart: "Where is my order?" The first time it really got to me, I had the help desk open in one tab, the WordPress admin in another and the customer's email in a third. I copied the order number from the email, pasted it into WooCommerce, read the status, copied the details back and wrote the same polite paragraph I had already written dozens of times that week. The answer was already sitting in my own database. I was just the slowest possible bridge between the question and the data.
So I went looking for a better setup and tried the obvious things first. A standalone SaaS help desk with a WooCommerce integration gave me a nicer inbox. But my customers' conversations now lived on someone else's servers, the order data was a synced copy rather than the real thing, and every new teammate meant another seat on another bill. Then I tried AI chatbots. Most of them could recite my FAQ beautifully and could do nothing at all about an actual order. A bot that says "please contact support" is just a slower contact form.
What I wanted was boring in a good way: the help desk should live where the store already lives. That's Cliedesk. It's a WordPress plugin, and once it's installed your support runs inside your WordPress admin, right next to your orders and your customers.
Here's what's in it:
An AI agent that answers customers directly and can act on their WooCommerce orders. It works with the same order data your store uses, not an export.
A copilot that drafts a reply for every conversation, so your team starts from a good draft and edits instead of typing from scratch.
A shared inbox, so everyone sees the same queue and nobody answers the same customer twice.
Live chat on your site.
A help center for your articles, so common questions get answered before they turn into tickets.
A customer portal where customers can check on their own requests.
Here's the decision I expect people to push back on: Cliedesk doesn't sell you AI. You plug in your own key. The easy business move would have been to resell model usage with a markup and bundle it into a plan, which is what a lot of AI support tools do. I didn't want that, for two reasons.
First, I think store owners should see exactly what their AI costs and pay the provider directly, without a middleman deciding what a "resolution" is worth. Second, it keeps the data path short. Your conversations sit in your own WordPress database, and they only leave when your own key sends a request to the model provider you chose. There's no extra copy of your customer history sitting with us.
The same logic applies to staying inside WordPress instead of building yet another dashboard. Another team would have built a hosted app, because hosted apps are easier to control and easier to charge for. But WordPress store owners already have an admin they know, a database they back up and a host they pay for. I'd rather fit into that than ask them to move their support somewhere new.
Who it's for: WordPress site owners, and especially WooCommerce stores that handle their own support. That could be one founder answering emails at night or a small team sharing an inbox. Agencies that run support for client stores should find it a natural fit too.
Who it's honestly not for: if your store isn't on WordPress, this won't help you. And if you want a fully managed service where someone else handles hosting, AI accounts and keys, a hosted SaaS help desk will suit you better. Bringing your own key is one extra setup step, and you'll be watching your own AI bill.
There are real trade-offs in this approach, and I'd rather name them up front. Because everything runs on your server, your hosting matters. A cheap, overloaded host will feel slower than a big SaaS platform. And letting an AI agent act on real orders is something to roll out deliberately. I'd suggest watching how it handles conversations in the inbox before you lean on it fully. What I build next will be shaped heavily by what store owners tell me this week, so I'll be here all day reading every comment.
Which brings me to my question: if an AI agent could act on your WooCommerce orders, what's the first task you'd hand to it? And what's the one thing you'd never let it touch without a human approving it first?
Thanks for taking a look.