Feedback

No more Word docs full of screenshots.

Your client opens their live site from the portal, taps what they want changed, and asks. You get the page, the element, a screenshot, and the device, not a guessing game.

If it's in Dropl, change it yourself. If it isn't, point at it and ask.

Point and ask

Made for thumbs first.

A small toolbar at the bottom of their screen. Browsing still works; picking something is a deliberate tap.

  • Comment

    Tap the part of the page to change and describe it. Photos from the camera or library can go along.

  • Change text

    Tap a heading, paragraph, button, or link and type the new wording. It arrives as a precise from → to.

  • General request

    For anything not on the page yet, like “Add a page for our new location.”

  • My requests

    Their requests on this site, with statuses and replies. They can reply right there.

Tap a photo to ask for it to be replaced or removed, with the new photo attached. Photos already managed in Dropl point them to the portal instead.

Captured automatically

Every request comes with context.

Which page, which element, which screen size. In one inbox per site, or across every client site.

  • Page URL and title
  • The element: selector, nearby text, and position
  • Current text and the requested text
  • A screenshot of what they saw
  • Device, browser, viewport, and scroll position
  • Who asked, and when
  • Inputs masked

    Form and password fields are masked in screenshots.

  • No recording

    Only the moment a request is sent is captured. No session recording or analytics.

  • Nothing for visitors

    The script loads async, shows nothing, and makes no requests unless that browser was given a feedback link.

Install

One line. Any site.

Paste it into the site's head once. Your dashboard has the tag with the client site's ID, and shows when the script is detected.

<head>
<script src="https://www.dropl.io/embed/d.js" data-site="q4n8w2zt" async></script>
  • Next.js
  • WordPress: your theme header or any header-code plugin (Dropl plugin coming soon)The Dropl plugin is coming soon to the WordPress.org plugin directory. Until then, use the script tag.
  • WebflowCustom code needs a paid Webflow site plan.
  • FramerCustom code needs a paid Framer plan.
  • SquarespaceCode injection needs a Business plan or higher.
  • WixCustom code needs a premium plan with a connected domain.
  • Shopify
  • HTML

AI resolves it

“Fix the open Dropl feedback.”

Your assistant reads each request through the Dropl MCP server, applies text changes in your code, asks the client when something is unclear, and marks finished requests done with a note. Nothing goes live until you deploy.

Prompt for Cursor or Claude Code

Fix the open Dropl feedback for this site. Use list_feedback to find the open requests and get_feedback to read each one, including the screenshot and the element details. Make the changes in this project. Apply text changes directly. If a request is ambiguous or you can't find the element, reply to the client with reply_to_feedback asking what they mean instead of guessing, and leave it open. Run the build, then mark each finished request done with update_feedback_status and a short note for the client saying what you changed.

Included on Freelancer, Studio, and Agency. Not on Solo.

Screenshots and photos count toward your storage. More in the Feedback docs.

Compare plans

Stop decoding screenshots.

Turn on Feedback for a client site on Freelancer or higher, and let your client point at what they want.