Overview
For a long time, our support request form kept growing. Each question was added for a reason. We wanted to understand what someone needed, gather useful information before replying, and reduce the back-and-forth required to investigate a problem.
But the overall experience had still become more complicated than I wanted it to be. I had heard feedback about that, and honestly, I agreed. We were trying to make support more efficient, but asking for more information doesn’t always make the experience better.Â
So I went back through the entire form and reconsidered nearly everything.
The new support request form is now live, and after using it for a few weeks, I’m really happy with how it has turned out. It is substantially simpler, more visual, and more guided, while still helping us gather the information that can make a real difference when someone needs our help.
A More Visual and Guided Experience
The previous version relied on traditional form elements such as dropdowns, inputs, and checkboxes. Those work, of course, but they aren’t always the easiest way to understand your options or know where to go next.
The new form uses cards, icons, and visual selections throughout the experience. When you’re choosing what you need help with, the options are presented clearly rather than hidden inside a dropdown. When you select one of our products, you’ll see the actual plugin logos, and the form guides you through the next steps based on what you selected.
The experience can also change depending on why you’re contacting us. A general question doesn’t need the same information as a technical problem, and a feature request shouldn’t follow the same path as an account or billing question. Instead of making everyone work through one large form, the request guides you toward the information that is relevant to you.
Fewer Questions and More Room to Explain
One of the biggest changes was simply removing questions. We spent a lot of time thinking about what information was genuinely helpful and what we were asking simply because we thought we might need it later.
Rather than trying to anticipate every possible situation with another field, the new form gives you more room to explain what you need in your own words.
If you’re asking a general question, you can simply tell us about your question. If you’re reporting a technical issue, we ask you to walk us through what happened and share relevant context, such as where you’re seeing the problem, what you were doing, whether anything recently changed, and any steps we can follow to reproduce it.
We also make it easy to share additional information when it would help, including a relevant page link, screenshots, or a screen recording. The goal isn’t to make you explain everything perfectly or diagnose the problem for us. We simply want enough context to understand what you’re experiencing and begin helping.
Confirming Your Plugin Version Without Making You Look It Up
Knowing which version of a plugin someone is using is important when we’re helping with a technical issue, but asking people to go find that information and type it into a form was another unnecessary step.
Now, after selecting a plugin, the form automatically tells you which version is currently available and asks you to confirm whether you’re using it. If you are, you can continue. If you’re using an older version, we’ll encourage you to update first because many issues are already resolved in newer releases.
It’s a small change, but it represents a lot of the thinking behind this redesign. We still need certain information to provide good support; we just don’t need to make you do more work than necessary to provide it.
Troubleshooting That Matches the Plugin You’re Using
When you select a plugin and report a technical problem, the form directs you to that plugin’s own Troubleshooting & FAQs page. These pages contain common issues, recommended troubleshooting steps, and answers to frequently asked questions related specifically to that product.
We do encourage customers to take a few minutes to review those resources before continuing. Sometimes the recommended steps resolve the problem immediately, which is obviously better than waiting for us to respond. If the problem continues, completing those steps can also help us begin investigating with a better understanding of what has already been checked.
Temporary Access When We Need to Investigate Further
One of the things that tends to surprise most people is that most problems cannot be reproduced on our own websites and only appear in a specific WordPress, hosting, and Divi setup. The only practical way for us to troubleshoot is to check what is happening directly on the customer’s site.
In the past, when we needed temporary access, we had to ask customers to create it using a separate plugin. We have now built our own Temporary Login feature directly into our plugins, giving customers a simple way to securely provide access when it would help us investigate an issue.
The new support form makes this even more useful by letting you include the temporary login with your initial request.Â
Temporary access isn’t required, but if you’re comfortable providing it and if you believe we need to investigate something directly, it can save everyone a round of messages and let us get started sooner. In some cases, we may even be able to identify or resolve the problem before sending our first response.
When You Contact Us, You Reach Real People
We’re Humans, Not AI Bots
I want to say this part plainly: when you contact Pee-Aye Creative, you’re contacting real people.
We don’t have an AI chatbot gatekeeping access to our team, and you don’t need to figure out special keywords or how to get past a frustrating automated system before speaking with someone. Your support request comes directly to us.
Samaira and I work together to keep up with support requests, and we coordinate with our development team when further investigation is needed. We try to work together to get back to you as quickly as possible while the other is sleeping, away, or busy with something else.
Sometimes we’re able to reply very quickly, while other requests need more time because we want to investigate them properly. Either way, there is a person reading your request and trying to understand how we can help.
Lots Of Ongoing Improvements For You
We’ve been making a lot of improvements lately, from our newer plugin interfaces and product updates to new features and behind-the-scenes changes. The redesigned support experience is another part of that work.
I don’t expect everything we create to be perfect the first time, but I do want to keep listening, paying attention, and improving things when we see an opportunity to make the experience better. I hope this new form makes it easier to tell us what you need, easier to provide helpful information when it’s relevant, and easier to get your request directly to the people who are here to help.
Thank You For Supporting Our Small Business!
Thank you, as always, for supporting Pee-Aye Creative. We appreciate it more than you know. We are a small family business, and I’m genuinely grateful to everyone who supports what we’re doing. My family is growing, our team is doing exceptional work, and we are committed to continuing to build new products and improving the ones that already exist for our wonderful customers.

















Thanks for this article, really useful. [[cap-comment-check]] peeayecreative.com