Keep Account Notes Current Across Every Call

TL;DR

• An account document is not a stack of summaries. It holds current state, and the hard part is expressing change rather than appending more text.
• What has to stay current is narrower than it looks: decisions, open items, stakeholders and constraints. Everything else belongs in the individual meeting note.
• Multiple opportunities on one account break naive merging, because status stops being singular and the document starts contradicting itself.
• Reviewing what changed since the last call is faster and more accurate than rereading an document that grows every week.

Open an account with ten meeting summaries and try to answer a simple question: what has the customer actually agreed to?

The answer may be spread across discovery, a technical review, a call with finance and a conversation that changed the rollout plan. A folder of individually useful notes can still leave someone reconstructing the sale.

Keep the current account position in one document. Meeting-level records should remain available for context and verification, but the working brief should tell the team where the account stands now.

Magic Screen's Living Notes support that model. A Living Note belongs to an account and updates from its linked meetings. The account view also provides meeting history and account-level questions. 1 2

The setup matters because the document is only as useful as the information associated with it and the instructions describing what to maintain.

Decide what should stay current

A useful account brief should help a seller prepare, coordinate with teammates and avoid reopening questions the customer already answered.

Start with the customer's goal and current process. Add stakeholders with the roles they have actually described, the evaluation criteria, confirmed decisions, blockers, open questions and next steps.

Keep the current state separate from history. An early target date can explain urgency without remaining the current target. An initial pilot scope can show how the evaluation evolved without being presented alongside the revised scope as though both apply.

Some information should remain unresolved. A buyer saying that finance will review the proposal does not establish who controls the budget. A senior title does not prove final purchasing authority. The document should preserve those gaps until the account provides the evidence.

Avoid asking the brief to contain everything. If a field never influences a meeting, handoff or decision, it may belong in the underlying record rather than the working account view.

A three-call example

The following account is fictional. The example shows the desired organization of information, not measured Magic Screen output or an automated conflict-resolution guarantee.

Call one: discovery

Northstar Services wants to reduce the time its operations team spends reconciling location reports. Dana manages operations and will coordinate the evaluation. The team is considering a pilot at six locations. They mention October as a possible start, but procurement and technical review have not begun.

The account brief should say:

The words "proposed" and "possible" are doing real work here. Removing them would make the account look more advanced than the conversation supports.

Call two: technical review

The technical team identifies an access requirement that needs further validation. Dana and the technical lead agree to reduce the pilot to two locations. Production data cannot be used until the agreement is approved. The seller will demonstrate the access pattern using fictional data.

The current brief should now show two locations, the access-validation requirement and the restriction on production data. Six locations should move into a short change history if it remains useful.

The brief should not say the technical review passed. It should say which requirement is still being evaluated and who is responsible for the next response.

Call three: budget discussion

Finance explains that approval will be considered in the next planning cycle. January is now the target under discussion. The team wants the technical issue resolved before submitting the request.

The account brief should now reflect this sequence:

October is no longer the current target. A reader who needs to understand the change can inspect the history or relevant meeting, but they should not have to read all three recaps to discover it.

Use instructions that preserve change

A Living Note needs more than an instruction to summarize all meetings. Give it a definition of current state and a place for important uncertainty.

Maintain a current internal account brief from the linked meetings.

Sections:
1. Customer goal and current operating process.
2. Stakeholders and explicitly stated roles.
3. Evaluation criteria and mandatory requirements.
4. Current decisions and agreed scope.
5. Approvals, blockers and dependencies.
6. Open questions.
7. Next steps with owners and dates when stated.
8. Material changes since earlier meetings.

Rules:
- Distinguish confirmed facts, proposals and unknowns.
- Preserve conditions and approval requirements.
- When a later discussion explicitly changes an earlier decision,
 show the new position and summarize the relevant change.
- When sources disagree without resolution, flag the disagreement.
- Do not silently choose a winner based only on recency.
- Do not infer authority, budget approval or purchase intent.
- Refer to a contributing meeting only when its identity is available.
- Never invent a source link, timestamp or quotation.

This is a proposed instruction set. Review how it performs on your actual account structure before making the brief part of forecasting or an external commitment.

Set up the account in Magic Screen

Create or identify the correct account first. Confirm that the relevant meetings belong to it. Magic Screen lets users associate a meeting with an account during the call or afterward, and the account area brings its notes and meetings together. 2

Create a note template with Living Note behavior enabled, then add it to the account's Notes area. The documented workflow incorporates already linked meetings and updates the note as additional linked meetings finish. 3 1

The work you should no longer need to repeat is writing a fresh cross-call prompt and manually merging every recap into a new account summary. The work you still own is source association, the note's structure and checking significant changes.

Use the contributing-meetings list to check coverage. Do not treat that list as proof that every individual sentence has been independently verified. It tells you which meetings contributed, which is useful when something appears missing or unrelated. 1

Handle multiple opportunities carefully

One company can have more than one evaluation. An expansion conversation in one division may have a different buyer, timeline and scope from the initial deployment in another.

Decide how your team will represent that distinction before combining the notes. Use the account structure and available controls that match your process, and make the opportunity or project context explicit in the meeting and note instructions.

Do not assume that sharing a company name makes every statement applicable to every deal. A requirement accepted for one business unit may not be approved for another.

The same issue appears with partners, agencies and consultants who attend calls for several customers. Attendee similarity can be a useful hint for association, but it is not enough to establish that two meetings belong to the same opportunity.

Review changes rather than rereading everything equally

After a material meeting, focus the review on what changed.

Check scope, timing, approval status, technical requirements and ownership. Inspect any newly resolved item to confirm it was actually resolved. Look at any strong statement about budget or commitment and confirm that the source supports it.

For a handoff, review the whole current brief once. The next owner should receive a clear account state and a way to find the underlying meetings. They should not inherit an unexplained mixture of old targets and current commitments.

If an incorrect meeting was linked, correct the association and verify the resulting account output. Do not assume that deleting a sentence from the note fixes the source problem that produced it.

Keep internal and customer-facing documents separate

A current account brief is usually an internal working document. It can include questions about approvals, risks and information from different stakeholder conversations.

A customer follow-up should be generated for its own audience. Share only the relevant, reviewed content. The convenience of having the whole account in one place increases the importance of deciding who should see it.

Before giving a teammate or external participant access, check the actual product controls and your policy. A familiar-looking note interface does not establish private-by-default access.

Build the habit around one active account

Start with an opportunity that has a few clear, approved meeting records. Create the Living Note, inspect the first brief and run the next meeting through the same process.

Look for specific improvements: less repeated reconstruction, fewer stale dates, clearer ownership and a faster path to the underlying discussion when a detail matters. Measure those observations rather than assuming a better-looking document proves a revenue outcome.

Use the Living Notes setup for the account document, then build a narrower pre-call brief around the next meeting. The account should become easier to understand as the conversation develops, without requiring the seller to rewrite its history every time.

The meetings that never reach the document

An account document assembled only from video calls will contradict what the account manager actually knows, because the in-person conversations are missing from it.

Recording those is widely available now; merging them into one running account document is the part that varies. MagicScreen captures from iPhone and Apple Watch into the same document as every call.

Frequently asked questions

What is a living account note?

A single document holding current state for an account rather than a stack of meeting summaries. The hard part is expressing what changed, not appending more text.

What belongs in an account document?

Decisions, open items, stakeholders and constraints. Everything else belongs in the individual meeting note, or the document becomes unreadable within a quarter.

How do I handle multiple opportunities on one account?

Keep them separate. Naive merging breaks as soon as status stops being singular, and the document starts contradicting itself.

Sources

1. Magic Screen. Living Notes. Checked September 10, 2026.
2. Magic Screen. Accounts and Account Intelligence. Checked September 10, 2026.
3. Magic Screen. Creating Note Templates. Checked September 10, 2026.