NewPlans from $49 a month, AI credits included

Give your support team superpowers.

AI technical support for WordPress plugin teams. Repile clones the customer's site, reproduces the failure, finds the cause in your code and drafts the reply. You press send.

Works insideFreeScoutHelp ScoutWordPress.org forums
Runs onClaude CodeCodex

Your customers don't need another link to the docs.

Plugin and theme tickets are rarely “how do I”. They're “it broke on my site”. That takes someone who opens the site, reads the code and finds out why.

AI customer support

Answers from your help center

Bot reply · 12 secondsSorry to hear the checkout isn't working! Please try clearing your cache and disabling other plugins. You might also find this article helpful: “Troubleshooting checkout issues”.
  • Never sees the customer's site
  • Guesses from articles written before the bug existed
  • Replies to the customer on its own

Repile · AI technical support

Troubleshoots like your best engineer

Internal note · verdict with evidenceTheme conflict, reproduced. The theme's sticky header covers “Place order” under 430px wide, so taps never reach the button. A CSS fix was verified in the sandbox. The draft reply includes it.
  • Clones the customer's site into a sandbox
  • Reproduces the failure and reads your plugin's code
  • Opens the GitHub issue or PR when it's your bug
  • Leaves a draft. A human presses send.

Other tools read your docs. Repile reads your code.

Documentation goes out of date. Your codebase can't, because it's the thing actually running on the customer's site. It's the best single source of information about how your plugin behaves.

  • Nothing to keep in syncShip a release and Repile already knows it. No articles to rewrite, no bot to retrain.
  • The customer's exact versionRepile checks out the release the customer has installed, not whatever the docs describe.
  • Answers with receiptsEvery verdict points at the file and line it came from, so your team can check it in seconds.

What Repile does with every ticket.

Every ticket goes through the same four steps a senior engineer would take. You see each one as it happens.

01

Reads the ticket and triages it.

Repile decides whether the ticket is a real bug, a setup question or a duplicate, and what it needs to check before anyone answers.

  • Uses your project's instructions
  • Remembers past tickets for this product
  • Skips spam and thank-you replies
How it works in detail
02

Clones the customer's site and reproduces it.

Repile copies the site into a private sandbox with the same WordPress version, PHP version, theme and plugins, then triggers the failure itself.

  • Real browsers and phone viewports
  • Screenshots and recordings as evidence
  • The live site is never touched
How it works in detail
03

Finds the cause in your code.

With the failure in hand, Repile reads your plugin's source to find the exact line, and tells you whether it's your bug or something on the customer's side.

  • Your bug, their theme, or their hosting
  • File and line for every claim
  • Fixes tested in the sandbox before they're suggested
How it works in detail
04

Leaves a note and a draft. You press send.

Repile writes an internal note with the verdict and a reply draft straight into the ticket. Your customers never hear from a bot.

  • Private note with findings and evidence
  • Draft reply, ready to edit
  • Ticket status stays in your hands
How it works in detail

Built for the way support teams work.

Ask it anything

@mention Repile in a note.

“Is this our bug or their theme?” Tag Repile in an internal note and it picks the ticket back up, re-checks, and answers in the thread like a coworker.

Learn more

Ticket status

Sorted the way your helpdesk sorts them.

Repile mirrors each ticket's status from FreeScout or Help Scout. When a ticket moves to Pending or Closed there, it moves in Repile too.

Learn more

Slack

Chat with your Director in Slack.

Ask it anything in Slack and watch the answer stream in. Daily digests and ticket alerts land in your channel, tagging the right person.

Learn more

Project Director

A Director that runs the whole project.

One agent your whole team can talk to. It watches every ticket in the project, starts the work, adds private notes and tags the right person.

Learn more

Case file

The whole case on one panel.

A case file sits next to every ticket and updates itself as Repile works: the summary, the customer, the timeline and the sandbox site.

Learn more

GitHub

Files the issue when it's your bug.

When the cause is in your code, Repile opens a GitHub issue with the steps to reproduce, the evidence and the failing line, and links it back to the ticket.

Learn more

WordPress.org forums

Answers your support forum too.

New topics on your WordPress.org support forum land in Repile like any other ticket. When the draft is ready, one click posts it from your own account.

Learn more

Projects

One project per product, with its own memory.

Each product you support gets a project with its name, avatar, instructions and memory. Repile learns from every ticket and gets sharper on the next one.

Learn more

Your server, your model

Runs on your own Claude or Codex subscription.

Every customer gets their own Repile server and domain. There's no shared backend. Pick the model per project, and switch any time.

Learn more

Why I built Repile

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.

Now everything has changed. AI got really good, and I can say this with confidence:

Give AI the right context, and it troubleshoots better than a human.

That's what I did with Repile. It works with your codebase directly, so it can triage each ticket and find the cause of the problem on its own. The reply is ready when you get there. You still press send.

I believe Repile will change the way your team works with tickets.


RizaFounder of Repile · @rizaardiyanto

Plugs into the inbox you have.

No migration. Repile works inside your helpdesk and runs on your own Claude or Codex subscription.

  • FreeScoutHelpdesk
  • Help ScoutHelpdesk
  • WordPress.orgForums
  • GitHubCode & issues
  • SlackDirector chat
  • Claude CodeRuntime
  • CodexRuntime

Every feature on every plan.

Unlimited tickets on every plan. Each plan comes with monthly AI credits and a private cloud machine. Prefer your own key? Bring your own Claude or Codex key on any plan.

Starter

For a small support desk

$49/ month

$50 of AI credits included

Get started
  • $50 of AI credits every month
  • Or bring your own Claude or Codex key
  • Private machine up to 4 CPU / 8 GB
  • Unlimited tickets, brands and seats
  • FreeScout, Help Scout and WP.org forums
  • Reads your GitHub code and files issues
  • SandyWP Plus included for test sites
  • Web app and Mac app

Pro Popular

For busy support teams

$99/ month

$110 of AI credits included

Get started

Everything in Starter, plus

  • $110 of AI credits, a 10% bonus
  • Private machine up to 8 CPU / 16 GB
  • More tickets worked at the same time

Max

For teams with many products

$199/ month

$250 of AI credits included

Get started

Everything in Pro, plus

  • $250 of AI credits, a 25% bonus
  • Private machine up to 16 CPU / 32 GB
  • The most tickets worked at the same time

Enterprise

For larger organizations

Custom

Credits and machine sized to you

Contact us

Everything in Max, plus

  • Custom AI credits and machine size
  • Slack support

Payments run through Polar. You get your own Repile server within one business day of paying, and you can cancel from the billing link in your receipt. First payment refundable within 14 days, see our Refund policy.

The short answers.

Anything else? Write to [email protected] and a human answers.

Does Repile ever email my customers?

No. It leaves an internal note with its verdict and evidence, plus a reply draft in the ticket. You read it, edit if you want, and click send in your helpdesk like you always have.

Where does my data live?

On your own server. Every customer gets a separate instance and domain; there is no shared backend.

Which AI does it run on?

Claude Code or Codex. The AI credits in your plan run Claude Code. To use Codex, or Claude on your own Anthropic account, bring your own key.

Which helpdesks does it work with?

FreeScout and Help Scout through their webhooks, plus WordPress.org support forums.

What does it cost?

Starter is $49 a month, Pro $99 and Max $199. Enterprise is priced to fit. Every plan has every feature, unlimited tickets, brands and seats, and the SandyWP Plus plan for your test sites. See Pricing.

Do I pay for the AI on top?

Every plan includes monthly AI credits: $50 on Starter, $110 on Pro and $250 on Max. Prefer your own key? Bring your own Claude or Codex key on any plan.

What happens after I pay?

We set up your private Repile server and email you the login within one business day. The first sign-in walks you through connecting your AI, your helpdesk and your code.

Can I cancel?

Yes, anytime, from the billing link in your receipt. Your server stays on until the end of the period you paid for.

Let the next ticket reproduce itself.

Plans from $49 a month, AI credits included.

Start with Pro Compare plans

Already a customer? Log in