Get started
Launch$99 a month for the first 10 teams

AI technical support,
not AI customer support.

Other tools answer tickets from your help articles. Repile clones the customer's site, reproduces the failure, finds the cause in your code and drafts the reply. You press send.

See pricingTry the app below ↓
···
Ask a follow-up, or tell Repile what to check next
Agent default Medium
FormwiseSandbox: formwise-412Full Access
Try itClick a ticket in the sidebarPress Send on a draftWatch the running ticket finish
Works insideFreeScoutHelp ScoutWordPress.org forums
Runs onClaude CodeorCodex
Why technical

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 seconds
Sorry 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 evidence
Theme 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.
Source of truth

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.
Help centerUpdated Nov 2024

Notification emails not arriving

Emails go through the Formwise mailer. Install our SMTP Connect add-on and set the sender in Formwise → Email → From.

Outdated
includes/class-mailer.phpv3.4.2 · live
40$from = get_option( 'formwise_sender' );
41if ( ! is_email( $from ) ) return false;
42$headers = [ "From: $name <$from>" ];
43return wp_mail( $to, $subject, $body, $headers );
RRepile: our bug. Updating to 3.4 left the sender setting empty, so line 41 skips every email without logging it. Workaround: set a sender in Settings → Email. Fix: fall back to the admin email and log the failure.
How it works

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
DW
Dana Whitfield[email protected]
Checkout button does nothing on mobile

Hi,

Since this morning the Place order button does nothing on phones. I tap it and nothing happens. Desktop is fine.

We are losing orders, please help!

Dana
Northwind Bakery

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
FWCheckout button does nothing on mobileFormwise
RRepileworking
Copied northwindbakery.com into a sandbox1m 12s
Matched WordPress 6.6.2, PHP 8.2, 31 plugins8s
Opened checkout on an iPhone 14 screen4s
Tapped Place order: nothing happened
Reproduced on iPhone 14

The tap lands on the store's sticky header, not on the button. Desktop checkout works.

Recording, 0:14
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
FWCheckout button does nothing on mobileFormwise
RRepile2 files read

Not our bug. It's the theme. Formwise's button handler is fine (checkout.js:42). The Harbor theme pins its header to the bottom on phones, on top of the button:

harbor/header.css:118
.site-header--sticky {
  position: fixed; bottom: 0;
  z-index: 9999;
}
✓ Tested a CSS fix in the sandbox. Order #10482 went through.
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
Support inbox#412
Checkout button does nothing on mobileDana Whitfield
RRepileInternal note

Not our bug: theme conflict. The theme's sticky header covers “Place order” below 430px, so taps never reach the button. Reproduced on iPhone 14; fix verified in the sandbox.

RRepileDraft

Hi Dana, thanks for the details. Your theme's sticky header is sitting on top of the button on phones. Add this CSS under Appearance → Customize and checkout will work again…

EditSend
Everything else

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.

Support inbox#418
License key says already usedJane Doe
RARizaInternal note

@Repile did Jane's reply change anything? Should we just reset her activation?

RRepileInternal note

Re-checked the ticket. The old site is no longer active, so resetting is safe. I updated the draft to confirm the reset.

RRepileDraft updated

Hi Jane, thanks for confirming. I've released the activation from your old site, so the key works on the new one now.

Ticket status

Tickets sorted the way your helpdesk sorts them.

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

Active3
Checkout button does nothing on mobile4m
Form won't submit after updatenow
Fatal error on PHP 8.3 after 3.412m
Pending1
Waiting on customer's staging login2h
Closed1
License key says already used1d
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.

  • Case file, Customer, Timeline and Site tabs
  • Updated after every step
  • Hand a ticket over without re-reading it
Problem

“Place order” can't be tapped on phones since this morning.

Cause

Theme sticky header overlaps the button below 430px.

Next step

Send the CSS fix; suggest reporting it to the theme author.

Updated after the sandbox check
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.

Fatal error on PHP 8.3 in Form_Validator::sanitize() #422
OpenRrepile[bot] opened this from ticket #418
  • Reproduced on PHP 8.3.4, WP 6.6.2
  • Deprecated dynamic property at includes/class-validator.php:88
  • Passes on PHP 8.2; fix suggested in the issue
WordPress.org forums

Answers your plugin's 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.

  • Picks up new topics and replies
  • Your WordPress.org password never leaves your Mac
WordPress.orgPluginsSupport
Plugins › Formwise › Support

Emails stopped sending after 3.4

M
meiharbor3 minutes ago

Since the update, no notification emails arrive. My SMTP plugin is active and its test email works.

Reply To: Emails stopped sending after 3.4Drafted by Repile
Thanks for the report. 3.4 moved sending to the wp_mail filter, and your SMTP plugin hooks in too early, so our emails skip it…
Notify me of follow-up repliesPost to forum
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.

FW
Formwisegithub.com/formwise/formwise · 4 open tickets
Instructions
Always ask for the Formwise version. Pro features live in formwise-pro. Never promise release dates.
Memory
harbor-child theme breaks checkout on mobile (3 tickets)
Customers on PHP 8.3 need 3.4.1 or later
Your server, your model

Runs on your own Claude or Codex subscription.

Sign in once with the Claude or Codex plan you already have, and Repile works on that. Every customer gets their own Repile server and domain. There's no shared backend. Pick the model per project, and switch any time.

Repile model favorites: Opus, Sonnet, GPT-5 Codex
Integrations

Plugs into the inbox you have.

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

Pricing

One plan. Every ticket included.

One plan with everything in it. No per-ticket fees. Repile runs on your own Claude or Codex subscription, so the AI usage stays on the plan you already pay for.

Early bird
$99 a month for the first 10 teams.

Keep the $99 price for as long as you stay subscribed. After 10 teams, the price is $149.

10 of 10 spots left

Repile

Everything Repile does, for all your brands, plugins and themes.

$99$149/ month

Early bird price, locked in. Regular price $149 a month.

Start for $99 a month
  • Unlimited brands and products
  • Every ticket source: FreeScout, Help Scout, WordPress.org forums
  • Unlimited tickets and team seats
  • SandyWP Plus plan included for the test sites
  • Clones the customer's site to reproduce each bug
  • Reads your GitHub code and files issues
  • Your own private server
  • Web app and Mac app

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.

Questions

The short 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, running on your own Claude or Codex subscription. You sign in once and Repile uses that plan.

Which helpdesks does it work with?

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

What does it cost?

$149 a month, with every feature, unlimited brands and products, and the SandyWP Plus plan included. The first 10 teams pay $99 a month for as long as they stay subscribed. See Pricing.

Do I pay for the AI on top?

Repile uses your own Claude or Codex subscription, so AI usage is billed by Anthropic or OpenAI on the plan you already have. Repile's price covers your server, your SandyWP Plus plan and the app.

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.

Early bird: $99 a month, first 10 teams only.

Start for $99 a monthSee what's included

Already a customer? Log in