How to Collect Client Feedback in Bricks Builder (Without Endless Email Threads)

The quickest way to collect client feedback on a Bricks site is to let the client comment directly on the live page instead of describing changes in email or Loom. Share a link, the client clicks the element they mean and leaves a pinned note, and that feedback lands next to the work — ideally inside the Bricks builder itself, with a screenshot and page context attached. That one shift removes the “which button, on which page?” guesswork that causes most revision rounds.

Here’s the problem, the options, and a workflow that actually sticks.

Why client feedback on Bricks sites gets messy

If you build client sites in Bricks, the feedback stage is where projects stall. The work is fine — the communication about the work is the bottleneck:

• Feedback arrives in five places at once: email, a Loom link, a WhatsApp screenshot, a shared doc, and a phone call.
• It’s vague and positional — “move the heading near the top” — and you burn time mapping comments to actual elements.
• There’s no record of what was agreed, so “I never approved that” becomes a real conversation.
• Every clarifying back-and-forth is another day added to the project.

None of that is a design problem. It’s a feedback-collection problem.

The three common ways (and why they fall short)

1. Email / Loom / screenshots. Zero structure. You become a translator, converting prose into element-level changes. Nothing is tracked, nothing is approved.
2. A shared spreadsheet or doc. Better than email, but the client still has to describe location in words, and you still bounce between the doc and the builder.
3. A generic website-feedback tool (BugHerd, Atarim, Marker.io, etc.). These solve the on-page-comment part well — but they’re not built for Bricks, usually require the client to create an account or sign in, and the feedback lives in a separate dashboard rather than where you actually work.

The pattern: the closer feedback lives to the element and to your builder, the fewer rounds you do.

A feedback workflow that cuts revision rounds

Whatever tool you use, aim for these four principles:

1. On-page, pinned to the element. The client clicks the thing they mean. No ambiguity, no “which section?”
2. No client login. Every account you ask a client to create is friction — and friction means they fall back to email. A no-login link gets 100% participation.
3. Context auto-attached. A screenshot + the page URL + device should ride along with every comment, so you’re not asking “what were you looking at?”
4. A clear sign-off. When the page is done, the client approves it and you keep a timestamped record. That single step ends scope disputes.

How to do it in Bricks specifically

Because Bricks renders the front end from its own element tree, you can tie feedback to the actual element a client clicks — and surface it back inside the builder where you edit. That’s the part generic tools can’t do natively.

This is exactly what we built Reviso for, so here’s the concrete flow:

1. Open any page and generate a review link. From the Reviso button in the WordPress admin bar, create a shareable link for the page (or the whole site). No staging gymnastics.
2. Send the link — the client just clicks. No account, no login. They click any element, drop a pin, and type their comment. A screenshot and the page context attach automatically.
3. Review feedback inside Bricks. Every pin shows up in a panel inside the Bricks builder, so you action comments without leaving where you work. Threaded replies keep each item in one place.
4. Get sign-off. When the client is happy they mark the page approved, and you get a timestamped PDF certificate of the approval — your record that the work was signed off.

The core review flow (unlimited reviews, no client logins) is free on WordPress.org; you can also try the live demo to see the client side and the builder side before installing.

Tips to get cleaner feedback

• Tell the client to click first, type second. Once they realise they can point at the exact element, the vague comments stop.
• Batch your replies in the builder, then send one “ready for another look” rather than reacting comment-by-comment.
• Make approval the finish line. Frame it as “click approve when you’re happy” so sign-off is a normal step, not an awkward ask.

FAQ

What’s the easiest way to collect client feedback on a Bricks site? Give the client a link to the live page and let them leave pinned comments on the elements themselves, with no login required. Element-level, on-page feedback removes the guesswork that email and Loom create.

Can clients leave feedback without a WordPress account or login? Yes. With a no-login review link (the approach Reviso uses), clients click the link and comment directly — no account, no password. That’s the difference between 100% participation and clients defaulting back to email.

How do I track client approval / sign-off on a Bricks build? Use a tool that records an explicit approval with a timestamp. Reviso generates a timestamped PDF sign-off certificate when a client approves a page, so there’s a clear record of what was agreed.

Do I need a separate tool, or can I do this inside Bricks? You can keep it inside Bricks. Reviso is built specifically for the Bricks builder, so feedback pins surface inside the builder where you edit — rather than in a separate dashboard like generic feedback tools.

Is there a free way to do this? Yes — the core review flow is free and unlimited on WordPress.org. Paid tiers add integrations (Slack/webhooks), multi-page reviews, AI summaries, and white-label.

---

Want to see it in action? Try the live demo → or install the free plugin.