Reading what you drop
A proposal for review — what Snoopy says back when you drop a file or a link, in every case it can hit.
Today, dropping a file into a channel is a leap of faith. Something may happen to it. You will not be told what.
This proposal makes one promise: whatever you drop, you get told what happened to it, in the same thread, in plain language — and if something got in the way, you get one clear next step. Behind that, the file becomes searchable, page by page, so you can point at page 7 later and be right.
Below is every case we could find, with the reply we would give. Read it as a script.
The five outcomes
Every drop lands in exactly one of these. The words matter more than the labels — a person should never have to learn this vocabulary to understand the reply.
1 · A PDF it can read
You can ask me about any page now and I'll be able to point at it.
2 · A PDF it can only partly read
I can read those ten by eye if they matter — want me to?
3 · A scan — short enough to just read
That's my reading of the scan rather than its own text, so I'll quote it as a description, not word-for-word.
The most important sentence here is the last one. When the agent reads a picture rather than lifting real text, it says so — and it will never later quote that back as if it were the document's own words. Does that read as trustworthy, or as hedging? This is the wording we most want a second opinion on.
4 · A locked file
Save it again without the password, or paste the part you need.
5 · A damaged file
Your upload is still here and nothing was thrown away. Sending it again usually fixes this.
6 · A photo
That's what I can see in the photo, not text I lifted off it.
7 · An ordinary message
8 · A link
9 · Several files at once
• Q3-expenses.pdf — read, all 10 pages
• scan.pdf — no text in it, so I read its 2 pages by eye
• payroll.pdf — needs a password
Can you re-save payroll unlocked?
10 · A shortened link
Open it once and paste the address it lands on, and I'll read that.
We briefly made it follow the link. A security pass found that following redirects hands an attacker the choice of which address gets safety-checked, and the check underneath is weaker than it looks — so following is deferred until that check is made binding. What stays is the part that was actually wrong: it no longer claims to know where the link goes. Is "paste the address it lands on" a reasonable thing to ask someone?
11 · Something far too big
Tell me which pages matter and I'll do those.
What we would like you to react to
- The description disclaimer (cases 3 and 6) — "that's my reading of the scan rather than its own text". It is there so the agent never passes off a guess as a quote. Does it build trust, or undercut the answer?
- Speaking on every drop (case 1). Silence would be quieter, but silence is indistinguishable from a file being lost. Is one line the right price?
- The offer pattern. Cases 2, 3 and 9 end with a question. Is asking the right default, or should the agent just do it when the document looks important?
- Case 9 at scale. Ten files in one drop — list, or summary?
- Tone. These replies are plain and slightly clipped. Right for a work channel used by Thai SME teams?
Not in this proposal: nothing changes visually anywhere else in the product — no new screen, no new button, no settings. The whole change is what the agent says in a thread, plus files becoming findable in search later. Reading a scan by eye and reading a link both happen only when the agent asks and you say yes.
Ask an agent to do it
You can ask an agent to set things up in Woodstock, change a channel, or tell a channel what to file. Anything that changes your workspace happens only after you tap Approve.
Filing what you drop
A proposal for review — after Snoopy reads what you dropped, it files it onto the right pages, tells you what it did, and every line it wrote carries a chip that opens the exact spot it came from.