Ticket Notes & Communication

Every support ticket in AccuArk includes a Notes Thread that serves as the complete communication history for that ticket. The notes thread is located in the bottom section of the Ticket dialog (FrmCRMTicket) and provides a scrollable, chronological record of every note, update, and observation made about the ticket from the moment it was created until it is closed. This article explains how the notes thread works, the difference between internal and standard notes, best practices for effective communication, and how the thread contributes to your organization's audit trail.

Understanding the Notes Thread

The notes thread appears in the lower portion of the Ticket dialog, below the ticket fields (Subject, Description, Priority, Status, Category, Assigned To, and Contact). It is a scrollable panel that displays all notes in chronological order, with the oldest note at the top and the most recent note at the bottom. This ordering lets you follow the complete conversation history from start to finish, reading from top to bottom just like a chat transcript.

What Each Note Shows

Every note in the thread displays four pieces of information:

The combination of these four elements means that every note in the thread is fully attributed and timestamped. There is never any ambiguity about who said what and when.

Adding Notes to a Ticket

Below the notes thread, you will find two buttons for adding new notes: Add Internal Note and Add Note. Each button creates a different type of note, and it is important to understand the distinction between them.

Add Internal Note

Clicking the Add Internal Note button opens a text input where you can type your note. When you save it, the note is created with the is_internal flag set to 1 (true). This means the note is marked as an internal, staff-only note.

Internal notes are designed for:

• Team communication — Share information with your colleagues about the ticket without exposing it to external parties. For example, you might write, "I called the warehouse and they confirmed the item was shipped on the wrong date."
• Troubleshooting steps — Document the steps you have taken to investigate the issue. This is invaluable if the ticket gets reassigned to another team member, because they can see exactly what has already been tried.
• Technical details — Record technical information such as error codes, log entries, system configurations, or diagnostic results that are relevant to resolving the issue but would not be meaningful to the customer.
• Sensitive observations — Note any sensitive context that should not be shared externally, such as internal policy decisions, escalation reasoning, or notes about the customer's account status.
• Coordination notes — Leave messages for other team members who may work on the ticket later. For example, "Waiting on a response from the vendor. Expected turnaround is 48 hours."

Internal notes appear in the thread with an Internal badge, making them visually distinct from standard notes. Only staff members with access to the ticket can see internal notes.

Add Note

Clicking the Add Note button opens a text input where you can type your note. When you save it, the note is created with the is_internal flag set to 0 (false). This creates a standard note that represents the full communication record.

Standard notes are designed for:

• Communication records — Document what was communicated to or from the customer. For example, "Spoke with the customer by phone. They confirmed the item arrived damaged and would like a replacement."
• Action documentation — Record actions taken that the customer should be aware of. For example, "Processed a refund of $25.00 to the customer's original payment method."
• Status explanations — Explain why the ticket's status is changing. For example, "Moving to Resolved. The replacement item was delivered and the customer confirmed it is in good condition."
• Follow-up records — Note any follow-up actions or commitments. For example, "Promised the customer we would check back in one week to ensure the new installation is working correctly."

Standard notes do not have an Internal badge. They represent the general communication history that provides a complete picture of how the ticket was handled.

The Audit Trail

The notes thread is more than just a communication tool. It functions as a comprehensive audit trail for the entire lifecycle of a support ticket. Every note is permanently recorded with its author, timestamp, and internal/external classification. This creates an unbroken chain of documentation that shows exactly what happened, when it happened, and who was involved.

Why the Audit Trail Matters

A robust audit trail is valuable for several reasons:

• Accountability — If a question arises about how a ticket was handled, the notes thread provides a complete, timestamped record of every action and communication. There is no need to rely on memory or verbal accounts.
• Dispute resolution — If a customer disputes a resolution or claims they were promised something different, the notes thread serves as documentation of what was actually communicated and agreed upon.
• Quality review — Managers can review the notes thread to evaluate how effectively tickets are being handled. Are employees communicating clearly? Are troubleshooting steps being documented? Are resolutions being explained thoroughly?
• Training — New employees can review the notes on past tickets to learn how similar issues have been handled. The audit trail serves as a practical training resource.
• Compliance — In industries with regulatory requirements around customer communication and issue tracking, the permanent audit trail helps demonstrate compliance with record-keeping obligations.

Immutability of Notes

Once a note is created, it cannot be edited or deleted. This is by design. The immutability of notes ensures the integrity of the audit trail. If notes could be modified or removed after the fact, the reliability of the entire communication history would be compromised.

If you make a mistake in a note, the correct approach is to add a new note that clarifies or corrects the previous one. For example, you might write, "Correction to my previous note: the refund amount should be $25.00, not $35.00." This preserves the full history while ensuring accuracy.

Choosing Between Internal and Standard Notes

Knowing when to use an internal note versus a standard note is important for keeping your communication organized and appropriate. Here are guidelines to help you decide:

Use an Internal Note When:

• You are sharing information intended only for your team
• You are documenting troubleshooting steps or technical diagnostics
• You are recording observations about the account or customer that are sensitive
• You are leaving instructions for a colleague who will take over the ticket
• You are noting internal process steps (for example, "Escalated to manager for approval")
• The information would be confusing or inappropriate for the customer to see

Use a Standard Note When:

• You are documenting a conversation with the customer
• You are recording an action that was taken (refund, replacement, credit)
• You are explaining a status change
• You are documenting a commitment or follow-up promise
• The information is part of the general record of how the ticket was handled

Example Scenario

Consider a ticket where a customer reports a defective product. Here is how you might use both types of notes over the ticket's lifecycle:

1. Standard note: "Customer called to report that the widget purchased on order #1234 stopped working after two weeks of use. They would like a replacement."
2. Internal note: "Checked the batch number. This is from batch #B-0892, which had a 3% defect rate reported by QA last month. Likely a known issue."
3. Internal note: "Confirmed with warehouse that we have replacement stock available. Processing a replacement shipment."
4. Standard note: "Replacement widget has been shipped. Tracking number: SHIP-456789. Expected delivery in 3-5 business days."
5. Standard note: "Moving to Resolved. Customer confirmed the replacement arrived and is working correctly."

In this example, the internal notes contain information that is useful for the team (batch defect rates, warehouse confirmation) but would not be relevant or appropriate for the customer. The standard notes document the customer-facing actions and communications.

Viewing the Notes Thread

The notes thread is always visible in the Ticket dialog whenever you open a ticket. You do not need to take any special action to view it. Simply scroll through the thread to read the complete history.

For tickets with a long history, the thread may require significant scrolling. Notes are always displayed in chronological order (oldest first), so you can start at the top to see the initial report and read downward to follow the entire progression of the ticket.

Notes and Status Changes

It is a best practice to add a note whenever you change a ticket's status. While the status change itself is recorded by the system, a note provides the human context behind the change. Explaining why you are moving a ticket from In Progress to Resolved, or why you are reopening a ticket from Resolved back to In Progress, helps everyone understand the reasoning.

For example:

• Moving to In Progress: "Picking this up now. Will contact the customer to gather more details about the issue."
• Moving to Resolved: "Replaced the defective unit and confirmed with the customer that the replacement is working. No further action needed."
• Reopening (Resolved to In Progress): "Customer called back. The replacement is also showing the same defect. Reopening to investigate further."
• Moving to Closed: "Customer confirmed satisfaction with the resolution. Closing the ticket."

These contextual notes make the audit trail far more useful than status changes alone.

Best Practices for Effective Notes

Writing clear, useful notes is a skill that improves with practice. Here are recommendations for making your notes as effective as possible:

• Be specific — Include concrete details such as order numbers, product names, dollar amounts, tracking numbers, and error messages. Vague notes like "talked to customer" provide little value.
• Be concise — While detail is important, avoid unnecessary filler. Get to the point and state what happened, what was decided, and what the next step is.
• Include relevant references — If the issue relates to a specific order, invoice, or product, mention the reference number so anyone reading the note can quickly find the related record.
• Document both what you did and what you found — It is not enough to say "investigated the issue." Say what you investigated and what you discovered. For example, "Checked the shipment log and confirmed the package was delivered to the wrong address."
• Add a note when changing status — Always explain why the status is changing. This provides context that the status badge alone cannot convey.
• Use internal notes for team coordination — If you need to leave a message for a colleague, use an internal note rather than a standard note. This keeps internal discussions separate from the customer-facing record.
• Do not duplicate the description — The ticket already has a Description field for the initial report. Notes should add new information, updates, and progress reports rather than repeating what is already in the description.

Frequently Asked Questions

Can I edit or delete a note after it has been saved?

No. Notes are permanent and cannot be edited or deleted. This preserves the integrity of the audit trail. If you need to correct a mistake, add a new note with the correction.

Who can see internal notes?

Internal notes are visible to all staff members who have access to the ticket. The internal/external distinction controls the classification of the note, not individual user access. Any employee who can open the ticket can see both internal and standard notes.

Is there a limit to how many notes a ticket can have?

There is no hard limit on the number of notes. You can add as many notes as needed over the lifecycle of the ticket.

Can I add a note to a closed ticket?

Yes. Even after a ticket is closed, you can still add notes for documentation purposes. This is useful if follow-up information comes in after closure.

What to Read Next

• Support Tickets Overview — Understanding the ticket system, priority levels, status workflow, and visibility rules
• CRM Troubleshooting & FAQ — Common questions and solutions for CRM issues