Why We Built It
Your Help Desk Can See the Order.
Now It Can Do Something About It.
We run a lot of WordPress sites, and for years our support looked the same as everyone else's: a hosted help desk in one tab, wp-admin in another, and an agent copying an order number from one to the other while the customer waited. The help desk could show the order. It couldn't do anything with it. And every new teammate meant another monthly seat.
FAQ bots didn't fix that, because customers rarely want an article. They want the address changed before the parcel ships, the duplicate charge refunded, the licence moved to a new domain. That is action, not answers — and action is exactly where you can't afford an AI that guesses. So Cliedesk's agent works the other way round from most chatbots: every action starts switched off, every amount of money needs a human's approval by default, the customer confirms anything that changes their order, and the agent proves itself in shadow mode on real conversations before it speaks to anyone.
The rest followed from one decision: the help desk belongs inside the site the customer already has an account on. That is why there are no seats to count, why WooCommerce data needs no sync, why the help center ranks on your domain, and why you can take every byte with you whenever you like.
No Seat Tax
Unlimited agents on every plan. Pro is priced only by the number of sites.
Approval Before Money Moves
Refunds, credits, coupons and reships need approval for every amount by default.
One Brain, Three Layers
Agent, copilot and triage share the same knowledge, policies and actions.
Your Key, Your Model
OpenAI, Claude, Gemini, Mistral, Azure, Bedrock, Vertex — or Ollama on your own server.
Built for WordPress
Customers recognised from their accounts; articles in the block editor; SEO by your SEO plugin.
Built to Be Checked
PHPStan level 8, Plugin Check, OWASP ZAP baseline, signed builds, checksums and an SBOM.