A Client Feedback Workflow When the Client Only Has a Phone

Your client is standing in line for coffee, looking at the site you built, on their phone. Something is off on the pricing section. You want them to show you where, in a way you can actually act on. Asking them to install an app, create an account, or learn a review tool will lose you the feedback. They will send a vague text instead: "the pricing looks weird."

Here is a flow that works on a phone browser with nothing to install. The client takes a normal screenshot, adds it to a review, marks the exact spot, and sends you a link. It uses the no-login client feedback setup, which is the whole point: the person giving feedback does not sign up for anything.

Step 1: You open a review and send the client one link

You start the review. Open a new review in a browser tab, no password needed, and publish it to get a short link of the form /r/<slug>. Text or email that link to your client. That is everything they receive: one link that opens in whatever browser their phone already has.

Why not have them start from scratch? Because on a phone, browsers cannot capture the screen, so there is no "capture" button to hunt for. Giving them a review that is already live means they open it and go straight to adding an image.

Step 2: The client takes a normal screenshot

Phone browsers cannot grab the screen the way a desktop browser can. That is fine, because every phone can take a screenshot with the hardware buttons. Your client looks at the section that bothers them, takes a screenshot the way they always do, and that image sits in their camera roll. No new skill. They already know how to do this.

If your client is nervous about tools, this is the moment that keeps them on board. You are not asking them to learn a capture flow. You are asking them to take a screenshot, which they have done a hundred times.

Step 3: They add that screenshot to the review

The client opens your link on their phone. The review page lets them add an image: tap Add image, pick the screenshot they just took, and it becomes an item in the review. Each image is one item they can comment on. This is the part that replaces a separate app. The screenshot lives inside the review now, next to the others, instead of floating in a text thread where you lose track of which one they meant.

If they want to add two or three screenshots, they repeat it. Each one becomes its own item.

Step 4: They drop a pin on the exact spot

A screenshot alone tells you the page. A pin tells you the thing. The client taps to drop a numbered pin on the exact spot: the price that is wrong, the button that overlaps, the text that runs off the edge. Pins are baked into the exported image, so when you read it later you see exactly what they marked, not a guess. If you want more on this, pinning the exact spot a reviewer means walks through why this one move saves a round of back-and-forth.

They can add a short comment to the item too, by typing it. Phone keyboards are slow, so a pin plus three words ("this price is wrong") beats a paragraph. The pin carries the location; the words carry the intent.

Step 5: They comment, you read, nobody loses the thread

Anyone with the review link can comment on any item, and the client has the link, so they can. They do not need an account to leave a comment. You, as the owner, can mark each comment resolved as you fix it. That gives you a running list of what the client flagged and what you have handled, without a bug tracker or a project tool in the middle. If your client is never online at the same time as you, an async review that works across timezones covers the same flow when you are hours apart.

What you do with it on your end

Once the client has marked up the screenshots and commented, you read the whole review in one place. The same review exports as a PDF or Word document if you need to forward it, and it is available as clean markdown at /r/<slug>/markdown if an AI coding agent is doing the fixes. If you hand work to a developer, a signed-in owner can send the review to a GitHub repository as an issue. One review, read by whoever needs it, with the client's pins intact.

Two honest notes on the tool. Dictation for comments works in Chrome and Edge, not Firefox, so a Firefox client types. And a free review stays editable for 7 days, then goes read-only for you, the owner, while the shared link keeps working for the client. If you need it editable longer, Pro reopens it instantly and is five dollars a month, cancellable any time.

Why this beats a text thread

A text that says "the pricing looks weird" costs you a phone call to decode. A pinned screenshot in a review says which price, on which section, with a three-word note, and sits in a list you can resolve item by item. The client did nothing harder than take a screenshot and tap a spot. That is the trade you want: zero setup for them, specific and actionable for you.

Set up the review first, send one link, and let the client's own screenshot do the work.

Send us feedback

Stuck, or want to do something it won't let you? Tell us what you're trying to do and we'll reply by email as soon as we can. This isn't a live chat.

Powered by AcornReply