I spent seven years doing technical support for WordPress plugins. Back then it was rough. I had to debug and reproduce every issue by hand before I could even start on an answer.
Where the time actually goes
The hard tickets in plugin and theme support are about something that stopped working on one customer's site. Answering one of those means a lot of work before you write a single word to the customer:
- Find out which version of the plugin they run.
- Rebuild something close to their site: the WordPress version, the PHP version, the theme, the other plugins.
- Follow their steps until the bug shows up.
- Read the code until you find the line that fails, or prove that it is not your code at all.
Only then can you write a reply you trust. The reply itself takes five minutes. Everything before it can take an afternoon.
What changed
AI got really good. I can say this with confidence: give AI the right context, and it troubleshoots better than a human.
The key word is context. A chatbot that only reads your help articles cannot do this work, because help articles go out of date and they never describe the customer's site. The work needs the customer's real setup and your real code.
So that is what Repile does
Repile works with your codebase directly. When a ticket comes in, it sorts it first: a real bug, a setup question, or a duplicate. For a real bug, it copies the customer's site into a private sandbox, follows their steps, and reads your plugin's source to find the cause.
Then it leaves two things in the ticket: an internal note with what it found, and a reply draft. The reply is ready when you get there. You still press send.
What I hope it changes
I believe Repile will change the way your team works with tickets. Less time rebuilding sites by hand, more time on the replies and the fixes that only your team can make.
If you want to see it on one of your own tickets, write to me. I answer every message myself.