Support

The people who write the plugin are the people who answer

There is no first line triaging tickets and no autoresponder closing the conversation with a link to the documentation. Your message reaches someone who can fix the code, and so does the reply.

Before you write

Three screens that answer half the questions on their own

The diagnostic tools are already inside the plugin. In most cases you get there before we do.

“The site is slow”

  • Site health gives you the score with every reason spelled out
  • With profiling on, you see database milliseconds per plugin
  • The thirty-day chart shows whether it got worse suddenly or gradually
  • After an update, the automatic comparison tells you by how much

“The emails aren’t arriving”

  • The mail log says whether the message went out, failed, or was never generated
  • If it failed, the mail server’s error is right there in the row
  • If it was handed over but never arrived, it’s deliverability: SPF and DKIM
  • Every row names the plugin that sent it

“I can’t sign in any more”

  • Every module switches off with a constant in wp-config.php, without dashboard access
  • ADMIN3WEBBLUE_DISABLE_ LOGIN_GUARD suspends the login protections.
    Check the module for more info.
  • ADMIN3WEBBLUE_DISABLE_ HARDENING returns wp-login.php to its standard address.
    Check the module for more info.
  • Constants take precedence over any saved setting

How to get help fast

What to write so it’s solved on the first reply

Three things separate a single answer from four emails of clarifications: what you were doing when it happened, what you expected, and what happened instead. An error message copied in full is worth ten lines of description.

If you have them to hand, add your WordPress version, PHP version, hosting provider and Deskmode version. All four are on the Site health screen, with nothing to hunt for elsewhere.

It also helps to know whether the problem persists with every other plugin deactivated and a default theme active: it is the first test we would run anyway, and running it yourself saves a round trip.

Never send us passwords, API keys or FTP credentials. We don’t need them to understand a problem, and email is not a safe place to put them. If access genuinely becomes necessary we will ask for it through a suitable channel, and ask you to revoke it as soon as we are done.

Where to write

One channel per kind of request

Support channels by type of request, with indicative response times
If you have…Write toTiming
A technical problemContact form24h
A pre-sales questionContact form48h
A vulnerability to reportContact form, subject “security”Priority over everything
An idea for a new featureRequest a featureAs soon as possible
A withdrawal requestWithdrawal formWithin 14 days of purchase
A translation to contributeContact formAs soon as possible

We reply in English and Italian: those are the two languages in which we can guarantee a precise answer, with no misunderstandings over technical detail. The plugin interface, meanwhile, is translated into five languages.

Honest about the limits

What support covers, and what it doesn’t

It covers everything to do with Deskmode Pro Suite: faults, configuration, conflicts with other plugins where the cause is ours, questions about how to set a feature up, and security reports.

It doesn’t cover general WordPress support, custom development, maintenance of your site or configuration of your server. That isn’t meanness: they are different jobs, and pretending to do all of them would mean doing them badly.

For general WordPress questions — how a theme works, why another plugin behaves a certain way, how to configure a host — the right place is the official WordPress.org support forums, where thousands of people have already had that exact problem.

If you aren’t sure which category your case falls into, write anyway. If we can’t help we will say so straight away and, where we can, point you somewhere useful. A short honest answer beats no answer.

Open a request

Shopping Basket