Is there a character limit on ticket comments?
Yes, the system enforces two comment-related limits.
Limit 1: Comment body size
- Maximum is 65,535 characters per comment, or approximately 64 KB.
- The standard agent interface truncates plain text comments that exceed the limit to the first 65,535 characters.
- The Agent Workspace saves comments in HTML format and doesn't support truncation. Comment submission fails if you exceed the character size limit.
- The limit includes all text, formatting characters, and line breaks. If markdown or rich text formatting is in use, extra characters encode formatting. Even if these characters are hidden, they count toward the 65,535 limit and the system might truncate or reject comments sooner.
Limit 2: Total comments per ticket
- Maximum of 5,000 total comments per ticket.
- This applies to combined public and private comments.
- After reaching 5,000 comments, you can't add additional comments.
- To work around this, create a follow-up ticket and link to the original.
Visual indicators
The Agent Workspace
- Character counter appears as you type.
- Warning at 10% of limit, or 58,981 characters.
- Prevents submission if the limit is exceeded.
- HTML format might appear differently than plain text.
Email channel
- The system might truncate very long email replies.
- The system adds a note if the email exceeds the limit.
- The system encourages separating the message into multiple replies.
Best practices
When you approach the 65,535 character limit
- Split very long updates into two or three separate comments.
- Use the ticket description for extensive initial information.
- Attach documents for lengthy content instead of pasting into a comment.
When you approach the 5,000 comments limit
- Monitor the comment count on tickets that have run for a long time.
- Create a follow-up ticket at 4,500 comments.
- Link the tickets to maintain the relationship.
- Add a note in both tickets to explain the relationship.
Why these limits exist
- Very large comments impact ticket load speed.
- Limits optimize storage and query performance.
- Extremely long tickets are difficult to navigate.
- Limits prevent resource exhaustion.
Common scenarios
Review the recommended approaches for common scenarios:
- Paste log files: Attach as a .txt file instead
- Long troubleshoot session: Use multiple smaller comments
- Ongoing projects that last for years: Create follow-up tickets quarterly
- Email chain with more than 100 replies: Archive old content and summarize
Note: These are hard system limits and can't be increased on any plan.