At 10:17 a.m., a notification says yesterday’s proposal has been opened. The account owner starts typing, “Any questions?”—then pauses.
The response is fast, but not necessarily useful. The recipient’s reason for opening the proposal—and whether they can reply now—is unknown. Treat the notification as a cue to revisit the document and the last conversation, then prepare a better question.
A view is an observation, not intent
An open does not prove that interest has increased. The recipient may be seeing the proposal for the first time, forwarding it to a colleague, or looking for information that is hard to find.
Start with “What do we know?” The confirmed fact is that the document was opened. Every reason behind that action is still a hypothesis. Keeping the two separate makes follow-up more helpful and less intrusive.
Restore three pieces of context first
First, confirm which document and version was shared. If several copies are circulating, the notification cannot tell you which terms are under review.
Second, revisit the expectation set when the document was sent. A next-day review creates a different follow-up window from background material for next week’s meeting.
Third, identify open questions from the previous conversation. Pricing scope, security review, implementation timing, or internal decision material may already be on the agenda. That context matters more than the notification.
Use activity to narrow the question list
FeatPaper can notify a team when a shared document is opened. An individual viewing record can also show page-level viewing time, revisited pages, and link clicks. Those observations still do not explain why the recipient acted that way.
More time on pricing may reflect budget interest, a confusing fee structure, or an internal comparison. A return to security may signal progress—or someone gathering material for a specialist.
Turn the record into a question, not a conclusion:
- Instead of “I noticed you spent time on pricing,” ask, “You were going to review the rollout scope internally. Are there any additional criteria that would make the options easier to compare?”
- Instead of “I saw you revisit security,” offer, “If your security reviewer needs supporting material, I can prepare it before our next conversation.”
A good question does not advertise the observation. It helps the recipient identify what they need for the next decision.
Let the relationship set the timing
If the next meeting is already scheduled, an immediate message may add little value. Put the question on the agenda and prepare the relevant material instead.
If the recipient promised a quick review, a brief offer of support can fit the existing conversation: “Let me know if you need any additional material.” There is no need to announce the open.
For a new relationship, do not use the notification as a reason to make contact. Follow the agreed cadence and use the activity only to improve the message. During pricing or security review, ask about the reviewer, required evidence, and remaining approvals before pressing for a decision.
A five-step follow-up checklist
A rule such as “Call within five minutes” makes speed the goal. A better playbook records five items before choosing an action:
- notification time and the exact document version
- the next step agreed when the proposal was sent
- unresolved questions from the previous conversation
- two plausible explanations for the observed activity
- one question to bring to the next meeting
Only then decide whether to contact the recipient, update the meeting agenda, or prepare supporting material. This order keeps the activity record connected to the account context, even when several people work with the same customer.
A proposal view does not explain why someone opened the document. It can, however, be a useful moment to reconnect the document with the conversation. The first move is not to call. It is to restore context and turn that context into one specific question.