Questions? We are here to help!

Use contact notes with automatic Spark memory

Use a contact's notes to understand earlier decisions and outcomes. When Spark is enabled, it can use supported facts from accessible evidence in later conversations.

Read notes from a ticket or chat

In the contact details panel, Contact notes shows up to five accessible notes, with pinned notes first and then the newest notes. Select Add note or Edit when available. Select View all notes to open the contact’s Notes tab for full text, filters and revision history.

Read the contact's notes

You need access to the contact’s space to read notes, and permission to modify contact details to add or edit them. Available actions also depend on the note’s source and authorship.

Open Contacts and select a person. Select the Notes tab. Pinned entries appear first, followed by the latest entries. Open Tickets to see linked work you can access.

Filter notes by source, and category. Search for text, or expand More filters for author and dates. Select Clear filters to restore the view, or Refresh to load current results.

System notes record selected events, including ticket creation and closure, calls and lifecycle changes. Spark notes capture selected useful context. Staff notes contain context your team enters. Routine messages remain in their original conversations. Source links are available when your access permits them.

Add or correct a note

  1. Select Add note, choose a category and enter the context.
  2. Select Save note. Select Cancel to discard an unsaved draft.
  3. Use Edit for notes you can change, and History to inspect previous versions. Add a clarification when a system note needs more context; system notes cannot be edited or deleted.

How Spark uses context

Spark can retain supported preferences and lasting facts automatically. A note can exist without becoming reusable memory. One-time requests and unfinished troubleshooting stay with the conversation.

When facts disagree, Spark excludes the disputed memory until accessible evidence supports a resolution. An unrelated note edit does not settle a disagreement. A clear correction can establish a replacement when its supporting evidence is accessible. It can update its memory without rewriting the original notes. Expired facts and facts whose supporting evidence is no longer valid or accessible are excluded.

There is no staff Memory tab or memory correction, forgetting or retry control. Continue to keep your notes accurate through the normal note workflow. Processing depends on Spark availability, background workers and available credits.

Long conversations may use a shorter summary and relevant facts as context. The original notes and conversation history remain available through their existing access rules. Human handover follows the existing workflow; a memory conflict alone does not request a handover. The handover brief uses supported information from the current case to explain the problem, actions taken and what still needs attention.