Should You Tell a Client You Can See They Opened It?

Two different things are hiding inside this question, and merging them is why people get it wrong in both directions.

The first is disclosure: does the client know, in general, that opening your link produces a record. The second is narration: do you tell them what the record says.

The answers are opposite. Disclosure: yes, always. Narration: almost never.

Disclosure is not optional, and it is mostly not your job

A reader should be able to tell that a link is instrumented without having to ask. If the only way to find out is to ask, the arrangement is not consent, it is a gap you are hoping nobody notices.

The good news is that with a properly built tool this is handled for you. A shared Quixli document carries a permanent notice at the foot of the reader’s screen — “The author of this document can see view statistics.” The reader is informed at the moment it matters, by the document itself, without you having to work an awkward sentence into a covering email.

That is the baseline. What follows is about the cases where the baseline is not enough or where you want to go further.

Narration is where it goes wrong

There is a specific sentence that ends deals, and it is this one:

“I noticed you opened the proposal twice on Thursday evening — any thoughts?”

Every word of it is true. It is also, to the person receiving it, the moment the relationship changes. They were reading a document in their own time and it turns out somebody was watching the clock. Even readers who intellectually know this is normal react badly to being told the specifics, because the specifics make it concrete in a way the general knowledge never did.

The rule is simple and worth writing on the wall: use the signal to choose when to write and what to lead with, never as the content of what you write. How to follow up after your proposal is read is entirely about doing this well.

Four moments where you should say something

Disclosure beyond the on-screen notice is worth making deliberately in four situations.

1. When you send it, if the relationship is long or formal. One clause in the covering email — “the link tells me when it’s been opened, so I’ll know when to follow up rather than guessing” — costs nothing and permanently removes the possibility of an awkward discovery later. It also, in practice, reads as organised rather than creepy.

2. When they ask. Immediately, without qualification. This has its own article — what to say when a client asks if you are tracking them — because the way you answer in the first sentence decides everything after it.

3. When the timing of your follow-up would otherwise look uncanny. If you call somebody eleven minutes after they finish reading, they will work it out. Either wait, or be the one to say it first: “I know you’ve had a chance to look at it” is a fair, non-specific acknowledgement that beats being caught.

4. When you are asking them to identify themselves. If you put an email gate in front of the document, you are asking for something and you should say what it is for. A gate with no explanation converts worse than one with a sentence attached, and it deserves the explanation on its own merits — whether to require an email to view at all is the prior question.

Three moments where you should say nothing

• When the only reason to mention it is to apply pressure. “I can see it’s been read” deployed as a prompt is a threat with a friendly face and the recipient hears it as one.

• When you would be reporting on somebody who is not in the conversation. If a second reader appeared — a forward to a colleague — that is information about someone who never contacted you. Do not put it in an email to your contact. It puts them in the position of explaining their own organisation to a supplier.

• When you are not sure the reading is right. Most of the time you are not. A location is a hint with a real error rate, a unique-reader count is a floor rather than a total, and an open in the first minutes after sending is more likely to be a link preview than a person. Saying a wrong thing confidently is worse than saying nothing.

What if they would object?

Some readers genuinely do not want to be counted, and the honest thing to notice is that this is a real preference and not a symptom of having something to hide.

If a client tells you they would rather you did not, the correct response is to stop — send a PDF, or send a link and delete the read data afterwards. In Quixli, the owner of a document can erase every view session, event and gate capture it holds for that document in one action, across every share of it, and it is not recoverable. It cannot un-send a notification email that already went out, and it would be dishonest to imply otherwise; but the record itself goes.

A client who asks you to turn it off and finds that you did is a client who will believe the next thing you tell them.

The short version

• They should always be able to know. Pick a tool that tells them so you do not have to.

• Say it out loud when the relationship is formal, when they ask, or when your timing would give it away anyway.

• Never recite the numbers back to a person. Ever. There is no version of that sentence that lands well.

• If they ask you to stop, stop, and delete what you have.

If you want the underlying question rather than the etiquette — whether any of this should be happening in the first place — is it ethical to track a document you sent works through where the line sits. And what Quixli shows a reader documents the notice itself.