How to write lead notes another teammate can use

Use a compact structure

Record the question, your response, and the next step. For example: “Asked about CSV imports; shared the preparation guide; agreed to review a sample on Tuesday.” This is short enough to maintain while giving someone else the context needed to act. Length alone does not make a note useful.

Distinguish facts and judgment

“Said three people share the spreadsheet” records useful context. “Has a disorganized team” adds an unnecessary judgment. Write unanswered questions as questions rather than assumptions. A factual note is easier for another teammate to use and less likely to misrepresent what the prospect actually told you.

Limit unrelated detail

Include information needed for the business conversation and avoid unnecessary personal information. Never paste credentials or access tokens into lead notes. Documents requiring restricted handling belong in an appropriate controlled process. A field being convenient to edit does not make it the right place for every piece of information.

Finish with a concrete action

“Confirm whether the sample imported correctly” is clearer than “follow up.” Pair the action with a date when another conversation is appropriate. In Happitap, update notes after the action is completed so the next reviewer sees the current state rather than an old instruction that somebody already carried out.