Replies: 6 comments 1 reply
|
Hi @chkw-rks, thanks for this discussion! It's really interesting idea however it'll be implemented in Q3 '26 at earliest, in the meantime you can add Rich Text type field to your object which can serve as comments and all of the modifications to this field will be reflected in timeline activities (they are aggregated every 15 minutes meaning if user A makes lots of changes within 15 minutes, only the latest change will be reflected but if 2 users make changes within 15 minutes, changes of each user will be shown separately) |
|
Hello @BOHEUS, thank you very much for your answer and the proposed solution. I just tried it and it works well for now. Looking forward to the feature of comments, if possible! |
|
No problem, just in case, standard Text type field will also work, depends if you want to style those comments or not |
|
A comment function would be beneficial for every entity (including custom ones), as we are working in teams and need to keep track of the latest status. Currently, it is difficult for us to trace who is working on what and what has been done so far. A standard text field is only a temporary workaround, as I have to manually enter the date, time, and user every single time. |
|
This is a nice quality of life improvement. CRMs have always been sub-par with integrated communications. |
|
bumping this up. I would add ability to tag people and post notifications to slack |
|
Adding to this; if we could right click a field and associate comments to it (excel/google sheets style), that would be hugely helpful. |
Uh oh!
There was an error while loading. Please reload this page.
Hey! Opening this as an Ideas discussion to gauge interest.
The need
When working an Opportunity (or any record), I often want to drop a quick contextual line, like "replied, wants a call next week", "saw them at the conference", "sent follow-up", without the overhead of creating a full Note record.
Notes are great for substantive things, but every quick status update currently becomes a row in the Notes table with its own title, body, relations, and detail page. That's a lot of structure for a sentence, and it bloats the Notes view fast (especially for users running structured outreach campaigns where every contact gets touched many times).
What I'd love to see
A lightweight comment / activity-log primitive attached to records, separate from Notes. Roughly:
Think GitHub issue comments, or the comment streams on Notion. Optionally also with tagging another record, so the comment also appears in the timeline of a person or opportunity.
Why this is different from Notes / Tasks
Notes are documents. Tasks are work items. Comments are conversational context: the running narrative of what's happening with a record. Conflating them with Notes means either Notes becomes a junk drawer, or users avoid writing the small stuff and lose context.
Workaround I'm using
A custom long-text field on Opportunity called "Log", with manual date prefixes. Works, but loses authorship, isn't queryable per-entry, and doesn't aggregate across records.
Happy to hear if this overlaps with something already planned, or if there's a reason this should stay folded into Notes.
All reactions