CMDPress help center and support desk

It is inside the CMDPress workspace. Search by task or browse by area to find the guide for what you are doing, and guides open inside the app, so you can follow the steps without losing the screen you were on.

Open a support conversation from the support desk in your CMDPress workspace. Include your account and the details of the issue, so support starts with the context. Before you open one, a quick search of the help center can save a wait, since many questions already have a guide.

Include the account and issue details: which site or screen is affected, what you did, what you expected, and any error text. A request carries your account with it, so support does not start from zero. If a guide in the help center already covers the issue, mention what you tried.

Open the support desk in CMDPress. Replies and status stay in one thread in the same support workspace where you opened the request, so you can follow progress and reply there. That thread is kept apart from your agency’s client queue, so product help and client work do not mix.

No. The CMDPress support desk is for help with the platform, your account or a product workflow. Client requests go to the team support desk, a shared queue where your staff tie each request to a site and an owner. Keeping them apart stops product questions from mixing into client work.

Add the lightweight CMDPress agent plugin to the site, which is how every site connects, on any host from shared hosting to servers with no control panel. Your first connected site is free forever with no credit card. If you get stuck, search the help center by task or open a support request.