Notes combines the lead's note timeline with a note composer. Open the intended record in the shared drawer and select Notes; there is no separate Notes route. You need access to that lead and authority to add or change its information.
What you’ll see
Review existing context
- Confirm the drawer's record identity.
- Read note type, content, timestamp, and attribution together.
- Distinguish ordinary notes from imported form answers and edited notes.
- Use the composer only when you intend to add information; its restored text can be a local unsaved draft.
The composer supports Note Type, Markdown formatting, and Write/Preview. Preview renders the current text; it does not establish a saved note. Tags are separate lead information, and changing them should be treated as a write.
Save deliberately
Save Notes persists the note and updates lead information. The source also requests pipeline-stage evaluation from the note's content after saving. This can have consequences beyond adding a timeline entry, so do not save placeholder notes simply to demonstrate the screen.
AI rewrite and dictation invoke processing. Dictation can start automatic AI polish. If Save is clicked while polish is underway, the UI shows Waiting for AI polish… and saves after that work settles. Switching leads cancels that queued save rather than applying it to another record.
Check and recover
After an authorized save, confirm the note appears under the correct lead and inspect any resulting lead changes. A failed refresh can coexist with a successfully saved note; check before resubmitting.
Available edit actions use Save Changes and preserve original content in audit metadata. Hide and Delete affect stored history or visibility; neither is a harmless way to close the panel. Only use actions offered for your identity, and verify their result.
Screenshots
The screenshot for this guide is shown above, under “What you’ll see”.