Current Limitations
- Users can tag others in the comment section, but there is no confirmation that the tagged person has actually viewed the message.
- Critical instructions, updates, or clarifications can be missed if the tagged user does not check notifications promptly.
- There is no read receipt or follow-up mechanism to provide assurance that the tagged comment has been seen.
General Example
A supervisor tags a technician in a task comment with an important instruction.
- The technician never acknowledges or responds, and the supervisor has no way to know if the message was overlooked or simply ignored.
- This uncertainty slows down communication and creates workflow risks.
Requested Enhancements
- "Seen" Notation
Add a small marker (e.g., “Seen by [Name], [Time]”) under a comment once the tagged user has viewed it. - Follow-Up Action (Optional)
Allow tagged comments to require acknowledgment (e.g., a quick “✔ Acknowledged” button). - Notification Tracking
Provide visibility in the activity log for when a tagged user has opened or acknowledged the comment.
Business Value
- Clarity: Provides confidence that critical messages have been received and read.
- Accountability: Ensures tagged users are aware of their responsibilities.
- Efficiency: Reduces the need for redundant reminders or duplicate comments.
- Reliability: Strengthens collaboration by aligning communication with modern “read receipt” standards.
