Your clients aren't developers. They shouldn't need to be. When a client finds a bug, they should click the thing that is wrong, say what they expected, and send it. SnagRelay captures the rest: the element, the requests, the console and a replay of what they did. No "what browser are you using?"
The freelance support problem
- Vague reports. "The form doesn't work" with nothing else.
- Back-and-forth. Which browser, which page, what did you click?
- Unbilled investigation. Hours spent reproducing something you can't see.
How it works
- Add the widget to the client's site: one script tag, or the WordPress plugin.
- The client clicks what is wrong and describes it. No account.
- You get the evidence. The element, console errors, requests with bodies, repro steps and a session replay.
- Your agent can take the fix. In Cursor, Claude Code or Codex, tell it to fix the report by its key. It reads the same evidence over MCP and resolves the report.
- The client hears back. Resolving a report sends them a "fixed" email, so you don't have to write it.
One workspace, many clients
- One project per client site or app, so each client's reports stay separate
- Inbox or tracker. Keep reports in the SnagRelay inbox, or send each project to Jira, Linear, GitHub, GitLab, Trello or Azure DevOps
- History. Look back at earlier reports when a client asks about previous work; how far back depends on your plan
Running a team of client sites?
See SnagRelay for WordPress and agencies for guest reporting, the WordPress snapshot and a white-label widget on higher plans.
