How “Freshy Sites” Saves Hundreds of Dev Hours Using Our API With ChatGPT

Freshy Sites is a US agency that hosts and manages thousands of WordPress sites.

So when they told us they were experimenting with the WP Remote API, I was very curious about what they’d actually do with it.

The answer surprised me: support tickets. 

So generally, when a client wrote in asking if something was wrong with their site, someone on Freshy’s team would spend the next 20-30 minutes figuring out what went wrong. 

They’d check what changed recently, look through plugin updates, activity logs and backups, and slowly work backwards until they had a decent idea of what broke.

But now, they just ask a question in ChatGPT, and just a few seconds later, have all the details they need.

How cool is that?

When we launched the WP Remote API, the common question was: What can I actually build with this? And is it worth the effort?

Freshy’s example makes both answers much clearer. 

Ok, here’s what they’re actually doing

Freshy connected ChatGPT to their sites using the WP Remote API.

They gave ChatGPT a set of instructions for how their team normally troubleshoots a site, along with access to the WP Remote data it needs to do that work.

So when a new ticket comes in, their custom GPT follows a consistent investigation process:

1. Identify the exact website and resolve its WP Remote site_id.
2. Interpret the problem and determine which evidence is relevant.
3. Pull activity logs for the period mentioned in the ticket.
4. Retrieve supporting data such as plugins, versions, backups, files, security events, or performance information.
5. Compare the evidence with the customer’s reported symptoms.
6. Return the likely cause and the safest next step.
7. When a site change may be required, show the exact proposed operation and wait for human approval.

Then, once the AI has a likely cause, it can help with the next step too.

If a plugin looks suspicious, it can check the exact version and whether it’s active. If the developer wants to test an older version of the site, it can find the right backup and prepare a staging site from it.

It won’t quietly start changing the live site. Anything that could affect production still comes back to the developer for approval. 

You can use the same setup

Freshy’s exact workflow is documented here if you want to check it out. 

The initial setup just takes 2 minutes. Basically, you generate an API key in WP Remote, add our troubleshooting workflow to Codex, and give it a real support problem from one of your sites.

WP Remote’s API gives ChatGPT 100+ endpoints with both read-and-write access, so you can use it for any work you can think of. 

For example, you can ask it: 

“This site became slow yesterday. Check what changed and tell me what you think caused it.”

Or

“This page broke after an update. Find out what changed and which backup we should test.”

If you manage even 50 sites and only get a handful of these requests each week, saving 15 minutes on each one is already useful. If you manage a few hundred, then it’s a no-brainer to set this up.

Just take one investigation you were going to do manually and try this out instead.

Our support team is also actively helping agencies with this, so for any doubts or assistance, just email us at aman@wpremote.com