WordPress plugin · WooCommerce · Multisite
Install the plugin. A client clicks Report and points at what broke. The ticket has the element, the failing request, the PHP warning and what WordPress was running.
Your agent reads it over MCP and fixes it, or your team works from the ticket. Built for agencies running many client sites.
“We cut our ‘cannot reproduce’ rate by 80%.”
Or with WP-CLI
wp plugin install snagrelay --activateThen paste your project key under Settings → SnagRelay.
A client clicks Place order. The cart fails.
Checkout
Shipping
Oat soap
€12.00
Linen bag
€18.00
The gap
You can spend the afternoon disabling plugins. The warning that mattered was on the request they already sent.
Today · what arrives
From the client · by email
“Checkout is broken AGAIN. Customers are calling us.”
Screenshot 2026-10-08.png
You
Can you turn on WP_DEBUG and send me the log? And which page were you on?
Then you disable plugins one by one on a live shop.
With SnagRelay · same bug
SITE-18 · “Checkout just spins”
Your agent
checkout-plus was updated today and warns in cart.php:88 on that request. Fixing the plugin, not the theme.
No WP_DEBUG. No plugin roulette.
How it works
From WordPress.org. Paste the project key in Settings → SnagRelay and choose who sees the button. No theme edit. For the WordPress snapshot, also paste the site URL and secret from Developer context into your SnagRelay project.
They click Report, then the button or section that broke. No WordPress login, no SnagRelay account.
The element, the failing request, the PHP warning, plugins, theme and the WooCommerce cart. Attached.
What the ticket contains
Not “the only plugin that does this.” The report arrives with it attached.
Example · SITE-18
6.8
PHP 8.2 · MySQL 8.0 · multisite
Versions, and whether the site is multisite.
Flavor
2.4.1 · parent 1.8.0
Active theme and parent theme, with versions.
Elementor
3.24
Elementor, Bricks or Divi: name and version. Not the clicked element’s id.
Active plugins with versions, plus plugins and themes updated recently.
Warning plugins/checkout-plus/ cart.php:88
Warnings and fatals, plus notices when WP_DEBUG is on. Paths are relative to wp-content.
Version, currency, cart item count, coupon codes, shipping and payment method ids. No customer name or email.
Where it goes
No tracker connected. The report waits in SnagRelay.
Jira, Linear, GitHub, GitLab, Trello or Azure DevOps.
Cursor, Claude Code or Codex read this ticket over MCP and fix the plugin or theme in your repository. No login to the client’s wp-admin.
When the fix ships, mark_issue_resolved comments on the ticket and can email the client who reported it. The next report on that checkout comes with what fixed it last time.
For agencies
Not every client is on WordPress? One script tag covers Webflow, Shopify, React, Laravel and static sites. Before the plugin is in, the Chrome extension reports from the site as it is.
They click Report on the site you built. No account, no wp-admin login, no seat.
Every client site is its own project with its own inbox or tracker. Clients report without a seat or an account.
The Agency plan removes the SnagRelay badge from the widget.
Why trust it
We switched from Usersnap primarily to cut costs, but were also impressed with the quality of the reports and level of detail the platform provides our devs.
We run our own UAT through SnagRelay. Every bug arrives reproducible. Clean releases out.
The customisable widget fits perfectly with our brand, and the automatic sync keeps our entire team in the loop. An essential tool for any development team.
Redacted in the browser
Passwords, tokens, cookies, auth headers and emails never leave the page.
Sent only on Send
Nothing leaves the page until the reporter presses Send.
Free plan, no card
Try it on a real project before you pay.
Security review? In writing.
Hosting region, retention or a DPA: email us and we answer in writing.
FAQ