Get client feedback on the live page — instead of email or Slack
You shipped a pricing page, a prototype, or a walkthrough from an AI tool. The client replies in email: "Can we move the CTA?" Someone else adds a Slack thread with a screenshot and three bullet points. By round two, nobody is sure which version they reviewed. Docklet puts feedback on the live page itself — so reviewers comment in context, you publish the next version to the same URL, and the thread stays attached to what they actually saw.
Contents
When email or Slack is enough
Email and Slack are excellent for async discussion, approvals in prose, and teams already living in those tools. A quick "looks good, ship it" over email needs no special infrastructure. Screenshot markup in Slack works when the page is static and the feedback is one round.
Those channels break down when multiple stakeholders review different versions, when comments reference layout ("move this block up") without a shared view of the page, or when the artifact itself is an AI-generated HTML page that changes every day. That is when on-page review complements email and Slack rather than replacing your whole stack.
Why feedback on the page matters
Side-channel review creates three predictable problems:
- Version drift — "Which link did you look at?" after you republish.
- Lost context — a Slack message about "the hero" with no anchor to the hero.
- Extra seats — sharing inside Claude or ChatGPT when the client never uses those tools.
Comments on the live page keep feedback attached to the artifact viewers opened. You still use email to send the link; the review happens where the work lives. Analytics show who opened which version — a supporting detail, not a replacement for the comment thread.
What an in-context review loop needs
Three things matter for client review outside your AI tool:
- Open without the tool — a normal browser URL; no Claude, ChatGPT, or Cursor seat required.
- Feedback on the page — inline comments on the live artifact, not only in email threads.
- Any AI tool — you publish via MCP from whatever generated the HTML; the link is not locked to one vendor's share dialog.
Supporting properties: email allowlist so the page is not public by default, version history when you ship v2, and basic analytics on opens.
Your AI made something useful. Docklet makes it usable. Publish AI-generated pages, guides, demos, and mini-sites as live links with comments, analytics, permissions, and version history — in-place right from your AI tool.
How to set up with Docklet
-
Publish the page — Connect MCP
(
https://app.docklet.io/mcp, setup guide) and ask your AI tool to publish, or paste HTML in the Docklet console. - Restrict access — Set visibility to selected users and add client emails to the allowlist. Free tier includes this.
- Send the link — One URL in email or Slack. They open in a browser and leave comments on the page.
- Iterate — Revise in your AI tool, republish to the same URL. Prior versions stay in history; the comment thread stays meaningful.
See a live example with comments enabled: ashley.docklets.io/q3-pricing/ (opens without login).
For sharing ChatGPT Canvas or Claude artifacts specifically, see share ChatGPT Canvas with a client and share a Claude artifact with a client.
FAQ
Can I still notify clients over email or Slack?
Yes. Docklet does not replace your notification channel — it replaces screenshot-and-bullet-point review. Send the Docklet link in email or Slack; they comment on the page when they open it.
Do reviewers need a Docklet account?
They sign in with the email on your allowlist (or open a public Docklet with no account, if you chose public visibility). They do not need Claude, ChatGPT, or any AI subscription.
How is this different from Figma comments or Google Docs?
Figma and Docs are built for design files and documents. Docklet is built for AI-generated HTML pages, guides, and mini-sites — live in the browser, published from MCP, with the same URL when you update. Use the tool that matches the artifact.
Can multiple clients comment on the same page?
Yes. Add each email to the allowlist. Comments are visible to allowed viewers on that Docklet.
What if the client only gives feedback over email anyway?
That happens. On-page comments still give you a canonical place to copy notes into and a stable URL for "please look at this version." Many teams find one round of in-context review reduces back-and-forth enough to keep using it.
What does it cost?
Free ($0) covers five Docklets with public and selected-user visibility, email allowlist, and on-page comments. Pro is $4 per user per month (private visibility, custom domain, five versions). Team is $9 per user per month. Enterprise is custom. Yearly billing saves 20%. See pricing for full details.
Stop sending screenshots. Send a Docklet.
Share AI artifacts with feedback and analytics. Free covers your first five Docklets, including email allowlist and comments.
ChatGPT is a trademark of OpenAI. Claude, Claude.ai, and Anthropic are trademarks of Anthropic, PBC. Slack is a trademark of Salesforce. Figma, Google Docs, Netlify, and other product names are trademarks of their respective owners. Docklet is not affiliated with, endorsed by, or sponsored by those companies. Product behavior cited here is based on public documentation as of September 2026 and may change.