How Do I Get Premium Support?

Elementor Pro users get premium support from our team of professionals. To get support, you have to be connected to your Elementor account which will allow us to identify you as a Pro user.

Accessing Premium Support

Whether you’re just getting started or need assistance with advanced features, our Premium Support team is here to answer you within 1 day on average. Our paid users are given top priority in our customer experience system, with replies to their customer experience tickets taking precedence. In addition, support reps will offer to log into paid users’ WordPress dashboards and even their hosting control panels, such as cPanel, when required, in order to debug and solve issues. This service is not available to free users.

Tip: Please remember to check your Spam mailbox periodically if you don’t receive a reply. 

Note: We strongly recommend that you backup your website before contacting support.

Have You Tried the Knowledge Base?

Although we’re eager to help you, please be aware that we also offer extensive documentation and tutorials for every feature in our docs area. This is sometimes the quickest way for you to solve your issue.

If you’re seeing an actual error message, try searching for a few words of the message itself. For example, if you see a message that includes the phrase “Could not create directory”, type that exact phrase into the search bar, and you’ll get directed to a help document that gives suggestions for solving that issue. Likewise, searching for “500 error” would lead you straight to a guide for solving those errors.

Tips for Getting Fast, Accurate Support

Are you an Elementor Pro user? If so, please make sure you use the same email address in your support ticket that you used when you purchased Elementor Pro. This will enable the system to match you up with your Pro account, and that gives us the ability to provide you with the Premium level of support that you paid for. 

In your initial support request, please be as detailed as possible so we can understand the issue. 

Here are some tips that help us help you:

  • Give us links to the pages that have the actual issue happening right now.
  • Show screenshots so we can visualize the problem.
  • If the layout looks different in the editor than it does on the live site, show screenshots of both.
  • What’s even better than screenshots? Video screencasts!  Loom lets you create a free screencast where you can show us exactly the steps you are taking and you can explain it as you go. 
  • No matter how much detail you provide us, even with screenshots and screencasts, there are many situations where the only way we can take the troubleshooting to the next level is to be able to log into your WordPress admin area, using an Administrative-level user account, so we can fully investigate, and hopefully solve, the problem. We may ask you for your wp-admin administrative-level credentials, but you can be proactive and issue these credentials at the same time as you submit your ticket by following these procedures. In this case, you include the following information in your ticket:
    • The wp-admin URL, such as www.yourdomain.com/wp-admin (this may seem obvious but some users have the admin URL set up differently).
    • Occasionally, we may even need access to your server’s cPanel account, so we can troubleshoot server setup issues. You can get this information from your host. We will need the cPanel’s URL, its username, and its password.

Note: Once we receive credentials, we will begin troubleshooting, which may involve steps such as temporarily deactivating plugins or themes, so that we can test for compatibility issues. If you do not wish us to troubleshoot on your live site, then you should create a staging site, which is a duplicate test site, and give us credentials to this staging site instead. Several major hosting platforms like WP Engine or SiteGround offer services that create an online staging site, or you could also use a plugin such as WP Staging or WP Stagecoach, to do the same thing.

Support Scope

What do we support?

We support issues related to the current features of the Elementor plugin. 

What don’t we support?

Third-party Themes and Plugins

Officially, we don’t support 3rd-party themes or plugins, even if they are Elementor addons. However, we do try hard to provide free support for this whenever possible. Precedence, of course, is given to issues that are linked solely to Elementor. So, while we may try to help solve a compatibility problem, please understand that it may take time and ultimately we cannot guarantee that we can resolve it, as the solution may require the 3rd party to make changes on their end. For that reason, you should report the problem to the 3rd party as well. We strive to make Elementor as compatible as possible with 3rd party plugins and themes, but we cannot control the 3rd party’s code. If you find conflicts, please report the problem via the relevant support channel for either the Free or Pro version of Elementor. You can report problems with the free version at the WordPress repository support channel and you can report problems with Elementor Pro via your Elementor Pro account dashboard.

Although Elementor acquired the Layers theme in January 2019, all customer experience for the theme is handled by the Layers User Community. You can read more about the terms of the acquisition.

Custom Code and WordPress

We don’t support custom code or custom CSS. We recommend joining our Elementor Community. Our tens of thousands of members may be able to help you create or troubleshoot custom code.

We do not give general WordPress support. You can find resources and answers around WordPress in the WordPress.org forums.

We do not provide SEO consulting. Please contact an SEO expert for these matters.

Share it on social networks

Share on facebook
Share on twitter
Share on linkedin
Share on email
Was this article helpful?

Get Started With Elementor Today

Join millions of professionals who use Elementor to build WordPress websites faster and better than ever before

On this page