Notes in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers what Notes are, how they differ from Tasks, where to add them, how automated notes work in workflows, what makes a useful note, and how to use notes effectively for team handoffs and re-engagement preparation.

Reading time: about 5 minutes.

What Are Notes in HighLevel?

Notes in HighLevel are free-text internal entries attached to a contact record. They are written by team members to capture information about a contact that does not fit into the contact’s structured fields – things like what was discussed in a phone call, what specific preferences the contact expressed, what commitments were made, or why a particular decision was taken.

Notes live on the contact record and accumulate over time, building a documented history of the relationship. Each note is timestamped and attributed to the user who created it.

The contact never sees their notes – they are internal communication visible only to team members with access to the sub-account.

Where to Find and Add Notes

Notes are found within the contact detail view. Open any contact record and look for the Notes section – it may appear in the activity timeline alongside calls, emails, and SMS history, or in a dedicated Notes tab depending on the sub-account layout.

Adding a note is straightforward: click the option to add a new note, type the note content in the text area, and save. The note immediately appears in the contact’s record with the current timestamp and the logged-in user’s name as the author.

Notes Are Internal Only

Notes are strictly internal. They are never sent to the contact, never displayed in any client-facing interface, and never included in any automated communication.

The contact has no way to see their notes through any HighLevel feature.

This means notes can be written candidly. A note that says “Contact is price-sensitive and comparing with two competitors – come in 10% lower if possible at close” is appropriate because it stays internal.

A note that says “Contact was frustrated during the call about the project delay – handle carefully on next contact” is appropriate because it will only be seen by the team.

The internal-only nature is what makes notes useful. Team members can write honest, specific context without worrying about the contact seeing their assessments or internal observations.

Notes vs. Tasks

Notes and Tasks are the two primary internal tools on a HighLevel contact record, and they serve distinct purposes.

A Note is a record of something that happened or something known about the contact. It is passive – it documents information but does not require action.

Notes answer the question: “What do we know about this contact and what has happened?”

A Task is an action item with a due date, an assignee, and a completion status. It is active – it represents something that needs to be done.

Tasks answer the question: “What does someone need to do for or about this contact, and by when?”

A useful pattern: after a sales call, add a Note summarizing what was discussed, then add a Task for the follow-up action with a specific due date. The Note captures the context; the Task ensures the action happens.

Automated Notes via Workflow Builder

Workflow Builder includes an Add Note action that appends a note to a contact’s record automatically when the action is reached in a workflow. This creates an automated audit trail – a log of what the system did to or for the contact without requiring a team member to manually document it.

Common automated notes: “Sent initial lead response SMS at [timestamp].” “Contact entered the review request sequence.” “Appointment confirmation email sent.” “Contact moved to Active Customer stage.” These automated notes mean that when a team member reviews the contact’s record, they can see not just the communication history but also what automation workflows the contact has been through.

Automated notes are particularly useful for troubleshooting. If a contact says they never received a review request, an automated note on their record showing “Review request SMS sent on [date]” immediately clarifies whether the message was sent or not – without anyone having to dig through workflow logs manually.

What Makes a Useful Note

Not all notes are equally valuable. A note that says “Called” adds almost no information.

A note that says “Called 3/15 – spoke with Sarah about the kitchen remodel quote. She prefers white oak cabinets over the walnut option we discussed.

Quote needs to come in under $18k to move forward. Husband is the final decision-maker.

Following up end of March.” – that note is genuinely useful to every team member who touches the contact in the next month.

The elements of a useful note: the date of the interaction (even if the note is timestamped, explicit dates are clearer), what was discussed or discovered, any specific preferences or requirements mentioned, any commitments made (by either side), and the stated or implied next step. This is not a long format – two to five sentences typically captures what matters.

The discipline of note-taking after interactions is what separates a CRM that works as institutional memory from one that is just a contact database. The contact database stores who the contact is.

The notes store the history of the relationship.

Notes for Team Handoffs

Notes become most visibly valuable during team handoffs – when a contact moves from one team member to another. This happens in sales-to-operations transitions, when a sales rep leaves and their contacts are reassigned, when a specialist takes over from a generalist, or when a manager steps in on a contact’s account.

Without notes, the receiving team member has to ask the previous team member to brief them on the contact’s history – or worse, approach the contact from zero context. With notes, the receiving team member can read the contact’s record and understand the relationship without a briefing.

They know what was promised, what the contact’s preferences are, what their situation is, and what the last interaction covered.

This continuity of context is the core value of the notes system. It keeps the business’s knowledge about its contacts from being locked in individual team members’ memories – accessible only as long as that person is on the team.

Reviewing Notes Before Re-Engagement

A contact who has not been contacted in several months may have had multiple previous interactions – calls, emails, appointments – with various notes accumulated on their record. Before a team member reaches out to re-engage that contact, reviewing the notes is the difference between a contextualized outreach and a generic one.

A re-engagement call that opens with “Last time we spoke in September, you mentioned you were waiting until after the holidays to make a decision – wanted to check back in” is more effective than “Hi, we worked together before, wanted to reconnect.” The first requires a note. Without the note, the second is the default.

What Can You Do With It?

• Capture conversation context that structured fields cannot hold: Contact preferences, discussion summaries, specific commitments, and situational observations that belong on the record but do not fit in a standard field.
• Build institutional memory about contacts that outlasts individual team members: Notes ensure that what is known about a contact stays with the contact record – not in a single team member’s head or notes app.
• Enable smooth team handoffs without requiring verbal briefings: A well-documented contact record allows the receiving team member to understand the relationship without needing to be briefed by the person handing off.
• Create an automated audit trail with workflow Add Note actions: Log what automations did to a contact – which sequences they entered, which emails were sent – without manual documentation effort.
• Prepare more relevant re-engagement conversations: Reading notes before calling or emailing a dormant contact provides the context needed to make the outreach relevant and personalized rather than generic.

Key Definitions

Use Cases by Industry

Home Services – Post-Call Context Capture

A roofing company’s sales team adds a note after every inbound inquiry call. The note follows a standard format: date of call, what the customer’s situation is (hail damage, age of roof, insurance claim pending or not), their timeline, their primary concern (cost, timeline, or quality), and the agreed-upon next step.

When the estimator shows up for the site visit, they review the contact’s notes on their phone before ringing the doorbell. They already know the customer is dealing with an insurance claim, that cost is the secondary concern behind quality, and that the initial call was with a different rep.

They can walk in with relevant conversation rather than starting from zero.

Result: Every team member who touches a contact knows exactly what previous interactions covered. Customers do not have to repeat themselves. The estimation visit is more productive because the estimator arrives informed.

Legal Services – Case Context Documentation

A law firm uses HighLevel for client intake. After every client consultation call, the intake coordinator adds a detailed note: the matter type, the key facts as the client described them, the client’s stated urgency, any specific concerns they raised, and which attorney would be the right fit.

Notes also capture practical details: the client’s preferred contact time, whether they need documents translated, and whether they were referred by another client.

When the attorney reviews the contact record before the first substantive meeting, they have the intake coordinator’s full notes – not just the structured intake fields. The attorney can reference specific details the client mentioned (“You mentioned your main concern was the timeline for the property transfer”) that demonstrates they were paying attention before the conversation even started.

Result: Attorneys enter client meetings already informed. The client experience is stronger because the attorney clearly knows their situation – which builds trust from the first interaction.

Marketing Agency – Client Relationship History

An agency account manager adds notes after every client call – what campaigns were discussed, what the client’s concerns are, any feedback on recent results, any new priorities the client mentioned. When the account manager goes on leave and a colleague covers their accounts, the colleague reads the notes and handles the client relationship without needing to ask the account manager to brief them.

The agency also uses automated notes in the client onboarding workflow – “Onboarding email sequence started,” “Sub-account snapshot imported,” “Initial strategy call scheduled” – so the full onboarding timeline is visible on the contact record even if no team member manually documented each step.

Result: Client relationship history is preserved at the account level, not in individual employees’ memories or personal notes. Team coverage is seamless because the context is always accessible in the contact record.

Who Is This For?

How to Use Notes Effectively

Step 1: Open the contact record

Navigate to the contact via the Contacts section or Conversations Inbox. Open the full contact detail view.

Step 2: Find the Notes section

Locate the Notes area – in the activity timeline or a Notes tab depending on layout.

Step 3: Add a note after every significant interaction

After every call, meeting, or significant email exchange, add a brief note. Two to five sentences capturing what was discussed and what the next step is.

Step 4: Include the key context

Every useful note should capture: the date and type of interaction, what was discussed or discovered, any contact-specific preferences or requirements, any commitments made, and the next step.

Step 5: Add automated notes to key workflows

In Workflow Builder, add Add Note actions at key milestones – when a sequence is started, when an email is sent, when a stage changes. These notes build the automation audit trail without manual effort.

Step 6: Review notes before re-engaging

Before calling or emailing a contact, especially one not contacted recently, read their notes. Use the context from previous interactions to make the outreach relevant and specific.

Step 7: Use notes during handoffs

When a contact transitions between team members, read the notes thoroughly before any interaction. The notes replace the need for a verbal briefing.

Step 8: Establish a team note standard

If multiple team members add notes, agree on a minimal standard format so notes are consistently useful regardless of who wrote them.

Step 9: Clean up outdated notes periodically

Delete notes that no longer reflect the contact’s current situation. Keep the notes section relevant – useful context, not a historical archive of obsolete information.

How Does It Connect to HighLevel?

• Contact Management: Notes are a core component of Contact Management. They exist within the contact detail view alongside structured contact fields, custom fields, tags, and the activity timeline.
• Workflow Builder: The Add Note action in Workflow Builder creates automated notes. Any key workflow milestone can log itself to the contact record through this action – creating an automated audit trail without manual documentation.
• Tasks: Tasks and Notes are companion features on the contact record. Notes document what is known; Tasks define what needs to be done. Together they make a contact record both informative and actionable.
• Conversations Inbox: Notes are accessible from the contact’s record which is viewable from the Conversations Inbox. Team members handling incoming messages can reference the contact’s notes without leaving the conversation view.
• Call Recording: While Call Recording captures the audio of calls, Notes capture the summary and actionable context from those calls. Both exist on the contact’s activity timeline – recordings for full reference, notes for quick context.

Common Questions

What are Notes in HighLevel?

Internal text entries on contact records capturing context, conversation summaries, preferences, and commitments. Visible to team members only – never sent to contacts.

Where do I add Notes in HighLevel?

In the contact detail view – in the activity timeline or a Notes tab. Click to add a new note, write the content, and save.

The note is timestamped immediately.

Are Notes in HighLevel visible to the contact?

No. Notes are strictly internal – visible only to team members with sub-account access. They are never sent to or displayed to the contact.

Can Notes in HighLevel be edited or deleted?

Yes, typically by the creating user or admin-level users. Edit to correct inaccuracies.

Delete notes that are no longer relevant to keep the record clean.

What is the difference between Notes and Tasks in HighLevel?

Notes document information about a contact – passive records. Tasks are action items with due dates and assignees – active items requiring follow-through.

Both live on the contact record and complement each other.

Can workflow automations add Notes to contacts in HighLevel?

Yes. The Add Note workflow action appends notes automatically when reached in a workflow – creating an audit trail of system events without manual documentation.

How are Notes useful for team handoffs in HighLevel?

The receiving team member reads the contact’s notes to understand the relationship history – eliminating the need for verbal briefings and ensuring continuity of context across team transitions.

To Wrap It Up

Notes are one of those CRM features that seem obvious but get dramatically underused. Most HighLevel users know notes exist.

Far fewer use them consistently after every significant interaction. The ones who do build contact records that function as genuine institutional memory – accessible to any team member, at any time, about any contact, without needing to rely on individual recollection.

The return on note-taking discipline is asymmetric. Adding a note takes 60 seconds.

The value of that note – in a team handoff two months later, in a re-engagement call six months later, in a dispute about what was promised a year later – can be hours of clarity and many times the value of the 60 seconds invested.

The most effective note-taking practice: make it a post-call habit, not an occasional action. After every call, add a note.

After every significant email, add a note. After every in-person interaction, add a note.

Build the habit before the stakes are high enough to regret not having it.

1. Open any active contact record after the next significant interaction
2. Find the Notes section in the contact detail view
3. Add a note – date, what was discussed, preferences mentioned, commitments made, next step
4. Review the notes on the contact before the next interaction
5. Add an Add Note action to key Workflow Builder steps for automated logging
6. Establish a simple team note format if multiple team members share contacts
7. Review and clean up outdated notes on active contacts quarterly

The automated Add Note action in Workflow Builder is the easiest starting point for teams that struggle with manual note-taking consistency. Configure the action at key workflow milestones – sequence enrollment, email sent, appointment booked.

These automated notes create a baseline audit trail even before the manual note-taking habit is established. Once team members see automated notes appearing on contact records, it makes the value of the notes system visible and often increases manual note-taking too.