Yes. WP FeedBack PRO is designed to work with any theme available on the market.

We’re looking at the raw HTML rendered on the frontend so that the theme you choose does not affect the use of the plugin.

Yes. Our plugin is designed to work with any page builder available on the market.

We’re looking at the raw HTML rendered on the frontend so that the page builder you chose does not affect the use of the plugin.

We also tested the plugin with the following builders:

Elementor, Divi, Beaver Builder, WP Bakery, Brizy, Oxygen, Cornerstone.

We are constantly working on WP FeedBack PRO to make it the best platform it can be.

So much so that our users are saving 50%-80% of time on their projects from the very first day they start using it.

As we have a full team of developers, doing constant research with feedback from our users AND we strive to provide the best support ever, their is so much value with every plan we provide.

First of all, that’s great, you’re already ahead of most. It really just means you felt the same pain we did when you’re trying to serve your own clients.

Here at the Agency, we tried it all:

• I started by having no system, allowing clients to contact me however they like. But then when I had to find a piece of information or after I found myself avoiding my FB messanger feed, or getting these annoying 2 minute voice messages on WhatsApp,  I searched for a real solution.
• I then tried getting them used to just sending me emails, but then I’d get 5 emails, with no subject line, with each file in different place.
• Ok, so let’s try inviting them to the project management system.
  I started with BaseCamp, then moved to Trello, so it’s easier for them. But it meant they need to manage yet another platform, just for our collaboration.
• Then we moved to a support desk. at $80 per user I’m spending thousands on the solution. But then my team and I are spending so much time doing admin. I even hired a VA just to manage the support desk.
• Plus for big projects, having all the tickets coming in from email into the support desk. Things became messy, so we manage the big ones on massive spreasheets that we shared with the client to list all the issues, status, urgency and so on. But then again, things quickly lose context. When it’s just a sentence out of 100 lines with no visual aids.

Our solution will help you at any of these stages. I wish I had when I first started and I can see the direct effect on my own agency.

Yes they can, you can transfer the license between domain is you’d like. As long as there is 1 active domain (or more for the higher plans).

That being said, the way I see it, once you get the client used to using the tool, you should keep using it for ongoing support!

Why would you then train the client on a new process if he’s already playing ball??

Originally, the tool was built as a support tool rather than get content and approve designs but it saved us so much time on the support side that we gave it a test from day one with some new clients and since they gotten used to it, it was even easier to get them to keep using it for post-launch support.

You will need to add each subdomain as its own domain – The licensing system recognises that these are separate installations so they require verification.
I guess a more accurate definition is per WP install.
But, in any case, the real magic that we’re seeing within my agency and from the beta users is using it for your ongoing support as the 1 way you communicate with the client.

All the other solutions focus just on 1 part of your client communications (Content Snare – Content, Project Huddle/Invision – Design approval, Zendesk and others – Support) and they all work. I want our solution to be the 1 way your clients communicate with you. The thought behind it is that most of us use a different system for each process – Introducing (and training) the client on 3 different things over approx 6 weeks (content, design approval & post-launch support), which when you think about it is very confusing.

Imagine your accountant would’ve done the same – You’d probably end up just carving your own path for communication based on what you’re already used to from other suppliers. But if you establish just 1 way, you need to only train the client once, explaining the logic and importance and how it will save you both a lot of time, and that’s it.

No problem, you will get 30 days to check and decide if our solution is right for you. If you feel that it isn’t, we will issue a full refund.

Yes! We’re a feedback plugin so it’s only natural that we’d take our support very seriously – And we do!

In fact, that’s one the biggest mentions when we asked the beta group what we’re doing well. 🤓

There’s a designated screen inside the plugin where you reach us instantly.

Plus, you can always pop a question into our Facebook group and either us or others users will be happy to help.

Absolutely! WP FeedBack PRO is translated in 11 different languages. These include:

• Portuguese (Brazil)
• German
• Italian
• Czech
• Hebrew
• Spanish (Spain)
• Dutch
• German (Austria)
• Greek
• French
• Swedish

If you’d like to offer to translate in your language, let us know. We have created an awesome platform to do so, and we’ll offer you a 30% discount on any plan of your choice for life.

Email is at [email protected]
for more info.

Speed is cruicial for any successful website and we take this part very seriously.

The plugin is an admin tool so it loads only when the users are logged to the site. You can choose the user roles that are allowed to leave comments so it’s mostly used by admins and editors.

Even for them, it’s pretty annoying when the backend is slow so we’re loading the details of each task on click, which means that you’re loading only the ticket you’re currently working on allowing us to reduce the effect on the speed to the minimum.

The speed can be compared to loading a small comments feed on a blog post.

InvisionApp is a great platform for prototyping, the visual logic of allowing your client to simply click to provide feedback is shared between us. But when it comes to WordPress sites, a lot of the times it’s easier to build the page directly in the browser using one of the many visual design tool out there rather than start on a design software.

When we tried InvisionApp for one of our projects we had to build the page on WP, then take a screenshot and upload it to InvisionApp and map the entire page to the targets it sends to – linking nav items, buttons and inner links to other pages (or screenshots), so that the client can comment on the design and features.

We ended up with 107 screens to manage (On-page actions like tabs or accordions also require a screenshot of their own). So we spent a few hours designing a page, then another hour setting it up on InvisionApp.

Then, after the client added her comments, we went back to WP, made the needed changes, took another screenshot and replaced the previous screenshot on InvisionApp.

If a section changed, or we added/removed a section, all the link mappings were misaligned, so we had to move them around to the new positions.

It gave a good experience for the client but cost us hours to manage and maintain.

Plus, in a responsive website, we had to create a different screenshot for each break point which tripled our work.

AND we had to get the client to form a habit of logging in to InvisionApp every time they want to review or request a change.

WPFeedback removes all of this friction from both your side as the designer, developer or agency as well as from the client side, so now instaed of them going into yet another 3rd party platform, they will get used to visiting their own website. Helping them confront the WP dashboard and feeling comfortable using it. Thus helping them appreciate the incredible value that can be achieved through a WP website and inspiring them to keep adding new features and itterating the website resulting in more work for you.

Other than sharing the concept of visual tags (like with Invision for example), the approach is very different:

• Built into the client’s website – We’re the only ones that do that, this helps with the speed, basically with only of a fraction of a second added to the load time after 100 live stickers on a page (which is a lot). There are no calls to a 3rd party server for every task request. Other benefits are file uploads that go directly to your media folder (no need to download/re-upload) and the coolest of them all – WP Admin Commenting – Allowing you and your clients to do the same things you do on the front, only in the back – Explain custom fields and UI for different plugins.
• No extra logins – Also by built into the client’s website you never send them to a 3rd party URL. This is actually part of a bigger philosophy of getting the client to actually use their own website. I found that most of us (crazily) send the client to every other platform except their own website, reducing their confidence in using it – By helping them face the WP dashboard, they will be empowered to do the small tasks themselves (like changing text here and there, checking contact submissions and so on) while helping them understand the value of the amazing marketing machine you’ve built for them, inspiring them to initiate more meaningful features, like adding a booking system, building a funnel or creating a client area for their own clients.
• 1 system for 3 processes – All the other solutions focus just on 1 part of your client communications (Content Snare – Content, Project Huddle/Invision – Design approval, Zendesk and others – Support) and they all work. I want our solution to be the 1 way your clients communicate with you. The thought behind it is that most of us use a different system for each process – Introducing (and training) the client on 3 different things over approx 6 weeks (content, design approval & post-launch support), which when you think about it is very confusing. Imagine your accountant would’ve done the same – You’d probably end up just carving your own path for communication based on what you’re already used to from other suppliers.
  But if you establish just 1 way, you need to only train the client once, explaining the logic and importance and how it will save you both a lot of time, and that’s it.
• Our own design – Rather than counting on the WordPress interface, which could be pretty intimidating for clients, our interface is modeled after native apps your client is already using (like his Gmail or Facebook account). Making it super friendly for them. As if they don’t end up using it, there’s no real point to it.
• Centralized tasks – Even though this is on the roadmap, at the moment our solution is per website with the ability to integrate all the sites to your own support desk or project management system via Zapier. In the future, you will have the option to use our own cloud-based centralized area or keep using your own tools with Zapier and other more specific integrations we will build. The idea is to give you the freedom to craft your own workflow. I like to use TeamWork and my team is already used to it, so this just pushes tasks in there with an additional notification to the support desk, them my team clicks the link in the task to be redirected to the exact location of the request, just 1 click. So instead of completely modifying my workflow, WPF enhanced it to reduce admin and confusion time.

There are a bunch more differences but these are the main ones 🙂