Skip to main content
MainWP is a WordPress plugin that you run on your own WordPress site, the MainWP Dashboard, to manage your clients’ WordPress sites. Each site can belong to a client in MainWP. Connect MainWP, and Neo agents can answer WordPress tickets from the Dashboard.

What Neo can do with MainWP

  • Find a client’s WordPress site by the URL or site name in the ticket, and read its WordPress, PHP, MySQL and MainWP Child versions, connection status, last sync and sync errors, active theme and Site Health
  • List the site’s pending WordPress core, plugin, theme and translation updates, and the updates you chose to ignore
  • Read the site’s plugins and themes, abandoned plugins, security checks, changes made outside MainWP, uptime monitor and incidents, and SSL and domain checks when those add-ons are installed
  • Add an internal note to the ticket with the site’s details, its pending updates and its wp-admin link
  • With the access you give it: sync a site, run its updates, activate or deactivate plugins and themes, and manage posts, pages, users, clients, tags, costs and monitors. Helpdesk asks a technician before each change
Neo never reads a child site’s keys, its HTTP authentication password or a backup provider’s API key from MainWP, and it never creates an API key.

Your clients are mapped to companies

Neo matches your MainWP clients to the companies in your PSA and keeps the mapping on the MainWP card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the client’s name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC), then the domain of the client’s email against the company’s website, and last an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents. An email-domain match and an AI match are not handed to your agents automatically. They show on the Organization Mapping tab, where you can confirm or correct them. On a ticket, an agent reaches only the MainWP client mapped to the ticket’s company, and that client’s sites. Before it acts on a site, Neo reads from MainWP that the site is assigned to that client. Assign each site to its client in MainWP (Clients, then the client’s sites): a site with no client is reachable from no ticket. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. See MainWP API for the permission groups.

Next steps

Connect MainWP

Create an API key and save it in Neo.