By Marcel Seibold, Founder of sendhey · Published 14 Jul 2026
A raw ChatGPT share link, a pasted Claude artifact, or a link to a Drive folder full of exported files gets a file to a client, but it does not deliver it. None of the three give you a real access gate, a record of whether it was opened, or a link built to survive past the moment you sent it.
Anyone who has the link — or anyone who finds a "shared" Drive folder through a forwarded email or a browser history — can open it, forward it again, or keep it long after the engagement ends. Nothing about the share tells you whether the client actually opened what you sent, so "did you see the report" stays a guess instead of a fact you already know. And none of it is built to last: a shared chat conversation can be edited or deleted by either side, a Drive link can be revoked by an IT policy change on the client's end, and a chat provider's own share feature is a courtesy layer on a consumer product, not a delivery contract you control. None of that is a defect in ChatGPT, Claude, or Drive — they were never built to be a client-delivery system, and it shows the moment something matters enough that "who can see this" and "did they see it" stop being optional questions.
The default handoff today, even at agencies that are otherwise fully AI-augmented, is manual: the agent — human or AI — finishes the work, someone exports it as a PDF or an HTML file, and a person attaches it to an email or pastes a link into a client Slack channel. If the client needs a password, someone invents one and sends it in a second message. If anyone wants to know whether the client opened it, they ask. sendhey replaces that manual hand-off with one instruction to the same agent that already did the work: publish it, instead of exporting it.
Connect once at /connect — one browser OAuth approval for Claude, ChatGPT, Cursor, or Codex, done once. After that, delivery for every future artifact looks the same:
publish_page with the HTML (or a file bundle) and a policy: open, password, email verification, or restricted to named recipients or domains.url for the client and, for a hosted page, a separate manageUrl for you — never send the manage link to a client.get_activity for the same answer without leaving the chat.The access decision travels with the link itself instead of living in a separate password email: a client-only audit gets an email gate, a public case-study prototype stays open, a sensitive financial report gets restricted to named domains — and every choice is visible on the link's own settings, not buried in a habit only one person on the team remembers.
Not every share needs any of this. A quick screenshot to a teammate, a draft pasted into your own notes, or a link you expect to matter for an hour and never again — a native chat share or a Drive link is the right amount of process for those, and adding a gate and viewer tracking would be overhead nobody asked for. This workflow is for the artifacts a client will actually rely on: the ones worth a real access decision and a real record of who opened them, not everything that happens to leave an AI chat window.
See the full pillar overview of sharing AI-generated work with clients, the tool-by-tool reference at /docs/mcp-publish, or two related posts: setting up MCP client delivery in Claude Code and why viewer tracking is consent-clean by default.
Free 14-day Pro trial starts when you publish your first link. No card.
See pricing for plan limits.
Written by Marcel Seibold, founder of sendhey.
About · Privacy · Legal notice · Report illegal content · Terms · DSA