Relay - DocSend for AI agents: send and receive docs with context
by•
You send a deck or doc. They ask their AI to read it.
The AI sees what's on the page, but not the thinking behind it: why you made those choices, what you left out, or what's still open.
Relay shares that context with your document, so they and their AI can understand it and ask questions.
You choose what to share. Decisions that need your input, like a discount or a date, come back to you.
Try a sample relay. No sign-up needed.
Replies
Hi Product Hunt, I'm Saurabh, building Relay with @aacansha.
The first reader of your deck, your proposal or your contract is now an AI. Your agent knows why. Their agent gets a PDF.
A document tells someone what you recommend. The reasons behind it are often left in your notes or your agent.
Relay brings them along: a doc for the person, context for their agent, one purpose for both. You review what gets shared and send one link. They can read and ask questions in the browser, or use their own agent.
We’d love feedback from anyone sharing decks, docs, or plans—does the context answer questions the file leaves open?
The schema and skill are open. The product is hosted and proprietary.
Try a relay, no sign-up: https://relayto.ai/try
This could be especially useful for proposals where the recipient has lots of questions but doesn't necessarily want to schedule another meeting just to get answers.
@henry_habib yes, absolutely! It'll help speed up the back and forth so either your sales cycle speeds up, or you get to an informed decision faster. We all hate spending time in meetings that could've been an email, and now you don't have to do either.
@henry_habib Henry, is that proposal back-and-forth something you deal with yourself? If you have one coming up, I’d love to help you try Relay on it and hear where it helps—or adds friction.
decisions like a discount or a date coming back to me instead of their agent answering is what makes me ok sending this to a prospect, i don't want someone's AI negotiating with my notes
can I see waht questions their agent actually asked about the doc afterwards??? that would tell me way more than a view count
Thanks @thamibenjelloun, that’s exactly why we built it this way. Their agent can explain your reasoning, but it has no authority to negotiate for you. Discounts, dates and anything you mark come back to you as a question.
And yes. Each relay has an Activity tab that shows, for every person, which agent read it, which pages they viewed and what they asked. Questions their agent answered from your context are listed there too, and anything that needs you is pinned at the top with a reply box.
One honest limit: if they open it inside their own ChatGPT or Claude, we see that their agent read it and anything it sends back to you, but not the private chat around it.
You can check out some use-cases listed here and interact with these relays : https://relayto.ai/use-cases
@thamibenjelloun we had this exact use-case in mind where we do not want agent to make commitments on our behalf. It strictly adhere's to the context it has and when in doubt it revert back to you.
if they interact with Relay's agent then you see all the replies. if it's in their own agent, they will have to relay the questions back to you but their agent will offer to send it so they know it's an option.
can i pull a bit of context back after sending it?
@leoheo yup, you can keep editing the same relay at any point (including the context). The recipient won't be able to see the context you edited out, unless they've opened it before you made changes.
@sherman_szeto ah so whoever opened it early still saw the old one, got it
@sherman_szeto @leoheo you can always revoke the relay if you think you sent wrong context.
@leoheo Yes, you can update the context and the doc, it will create a v2 and the receiver only see's the latest. Try sending one and then ask your agent to update it. https://relayto.ai
Hey Product Hunt! I’m Aakanksha, co-founder of Relay 👋
You know that moment when you send a deck or doc and immediately think, “I should explain one more thing”?
Why you chose that price. What you ruled out. What’s still open.
Now the person receiving it often asks their AI to read it first. That explanation matters even more.
We built Relay so your agent can talk to theirs, with the context you choose to share. They get the doc and the thinking behind it. Anything that needs your decision comes back to you.
Would love your feedback on the product : relayto.ai
This is the part of the agent workflow I keep running into — the doc itself is fine, it's the reasoning behind it that gets lost when someone else's AI reads it. Keeping the 'why we chose this' and what I ruled out as context the agent can pull on, instead of baking it into the deck, feels like the right split. The must-ask part is what sells it for me — a discount or a date shouldn't be answered by their agent.
@jcbuilds 100%. Putting everything into the deck makes it super hard for someone to read it, but not having the context in there leaves so much context and questions unanswered. Really glad you see the value in the must-ask portion as well - we put in a lot of thought behind the right guardrails so an agent doesn't hallucinate something critical.
Definitely check it out and let us know any feedback you might have! https://relayto.ai/login
@jcbuilds exactly, agent should represent you to what it know best, not make things up.
Thus the context aspect is meant to be verified and controlled by you so you know what their agent can and cannot say.
sharing the thinking behind the deck, not just the deck. smart idea, congrats Sherman
@mohitvishwakarma thanks. Try out relayto.ai/try
we send a lot of proposals at the agency and the first question back is almost always why the estimate is that high 😅 can the context include a cost breakdown that only shows up when someone asks about price
@eldarmiensutov Yes, this is exactly where context helps. Documents are usually high level and meant to be skimmed; the real heavy lifting is done by the context. It’s never shown on the page, and their AI uses it only when it’s relevant, so the cost breakdown comes up when they ask about price.
There’s plenty of room, so add the details, an FAQ, or links it can follow. Mark anything internal, like your margin, as must-ask and it comes back to you instead.
Here’s a sample proposal relay: https://relayto.ai/try/annual-proposal
@eldarmiensutov Eldar, have you got a client proposal going out this week? If you’re up for it, I’d like to help you add the scope and cost reasoning to one real relay and see what questions come back. We can start with an example you’re comfortable sharing.
we see this on websites too, a lot of pricing questions now come from someone's AI assistant. the must-ask list is the part I'd use most. does the sender set it for every relay, or can a team keep one default list?
@olia_nemirovski yup we see pricing as a frequent thing people use agents to ask about. At the moment, the questions & answers context is set for each relay so the sender knows exactly what goes out per relay - though we definitely see value in having an approved set of information that someone on the team can optionally include. And we'll add that in soon for supporting teams!