Show clients proof, not screenshots
A screenshot in an email proves one moment. A share link to a test result shows each check, the value it saw, a replay and a video, and expires when you choose.

“We tested it” is a claim#
At handoff, or when a client reports a problem, the usual evidence is a screenshot pasted into an email. It shows one screen at one moment, it cannot show that the form actually sent, and the client has to take the rest on trust.
Agencies that sell care plans know the value of visible work: maintenance guides say reports are how clients see what they are paying for. The strongest report is not a list of tasks; it is the site doing its job.
A share link instead#
Every Testsy result can be shared with a read-only link that anyone can open without signing in. From the share link docs, the viewer sees:
- each check, with the value it was decided on and where it was read,
- the replay of every step,
- the video,
- the console and network logs,
- and your workspace's name, marked read-only with the expiry date.
Nothing else in your workspace: no other client's runs, tests or settings. Emails the run received are left out, since an email can contain a link that still works.

Choose how long it lasts#
When you create a link you choose 7, 30 or 90 days. Links that work now lists each one with when it expires and how often it was opened, and Turn off stops it at once. For a record you need to keep longer, keep the run in your workspace: run files are kept for 365 days.
What to share, and when#
- At handoff: a link per key journey (contact form, booking, checkout) with a passed result.
- After a reported problem: the failed run that reproduces it, then the passed run after the fix.
- In a monthly report: a link to last night's run for each check in the care plan.
Branding#
The page shows your workspace's name, so name the workspace after your agency. That is the extent of branding: there is no white-label report. If a client wants to look around themselves, give them a viewer seat instead.
This post is part of Find the bug before your client does.
Filed underWebClient sitesSharing and alerts