Ticket Replies and Internal Notes

Tickets support two kinds of communication: replies and notes.

Use the right type every time. Replies shape what the customer sees. Notes shape what the internal team understands.

Replies

Use replies for the customer-visible conversation. Replies should be clear, specific, and focused on the next step or resolution.

You can create, edit, and delete replies from the ticket detail page when your permissions allow it.

Before sending a reply, check the ticket status, priority, assignee, recent activity, and any linked contact or account context. A good reply explains what changed, what the customer should do next, and whether the team needs more information.

Use replies for:

• Answers the customer should see.
• Requests for screenshots, files, or clarification.
• Confirmation that work has started or finished.
• Follow-up instructions after a fix or workaround.

Before sending, confirm whether attachments, screenshots, invoice links, booking links, or document links should be included. If the ticket involves a public link or payment, test the link before telling the customer to try again.

Do not include internal blame, private troubleshooting notes, credentials, or unconfirmed assumptions in replies. Keep replies useful, specific, and safe for the customer to forward.

Internal Notes

Use notes for team-only context. Notes are useful for:

• Investigation details.
• Steps already tried.
• Handoff context.
• Internal decisions.
• Customer risk or urgency.
• Links to related work.

Do not put customer-facing promises only in internal notes. If the customer needs to know something, send a reply after the internal note is recorded.

Use internal notes for uncertainty too. If the team is still investigating, note what has been checked and what remains open so the next teammate does not repeat the same steps.

Internal notes can include more technical detail, but they should still be clear. Avoid shorthand that only one person understands when the ticket may be reassigned later.

Activity

Use the activity tab to review the ticket history before responding. This helps avoid duplicate work or missing context.

Activity is also useful before changing a ticket's status or priority. Review recent replies and notes so the status reflects the current customer outcome, not just the last internal action.

If activity shows the customer is waiting for the team, send a reply or update the status before moving on. If the team is waiting for the customer, make the next requested action clear in the reply.

Handoff Checklist

When handing a ticket to another teammate:

1. Add an internal note with the current finding, the next action, and any blocker.
2. Link related tasks, files, deals, or customer records when they explain the work.
3. Update assignee, status, and priority.
4. Send a customer reply if the handoff changes timing or expectations.

After handoff, check notifications or mentions so the new owner actually sees the ticket. A perfect internal note is not useful if the assignee is unaware of the transfer.

Reply Review Checklist

Before sending a customer reply:

1. Confirm the customer-visible status.
2. Check recent internal notes.
3. Verify any links or attachments.
4. State the next action clearly.
5. Avoid promising timing unless the owner and due date are known.

Related Docs

• Ticket Detail Page
• Ticket Status and Priority
• Notifications