Comments are essential for contact information of all kinds - e-mail, phone, and mailing addresses. I hope that comments will be added for all of these, as well as date fields to go with the comments.

This would be great!

We rely heavily on comments attached to email addresses in RE NXT to track email preference changes—both the reason for the change and its source. When a constituent unsubscribes from a specific email address, it's often because they don't want to receive solicitation at that particular email, not from the organization entirely. They may have work and personal emails in the database and only want solicitation at one.

Using solicit codes or consent fields at the constituent level would be too broad for our workflow—it would exclude them entirely from being contacted, even if they want to receive emails at an alternate address.

We also use comments to maintain an audit trail of where changes originated: from our Constant Contact integration, from an Omatic Cloud flow, directly from the donor via self-service, or from parish staff. This visibility is critical for support and troubleshooting.

This is a must, for all the reasons in the comments below.

We use email and phone comments to record the source of the contact. This is essential, as a phone number found in a directory may be viewed more cautiously than one provided by the constituent. A dated update field is also critical. This isn't an "idea" - this is basic functionality found in database view that should be available in webview. We should not be losing functionality.

This is essential - please also add the Date field on phone numbers, emails, addresses in WebView

This field is key to our contact data.

Now, need source for implied opt-in for text messaging!

We have always used field to indicate source of data and/or notes with more info.

Full audit logs would be much appreciated, but this is a good step in the right direction.

We relied on the comment field to help differentiate between unsubscribes, bounced emails, and which emails can be used by gift officers but not in mass communications. For our purposes, solicit codes and the DNC checkbox aren't quite enough. It's also helpful to see the date it was last viewed and who changed it.

These fields are vital for keeping our data clean!

A vastly inferior CRM that I was using before RE had an automatic log of which user changed what, when. Old and new data... as an audit log. So frustrating to not have this automatic audit.
we seem to have bad phone data at the moment, it would be nice to leave a comment to say it has been checked.

This is especially frustrating since I often received instruction during Blackbaud led trainings to use the Comments field as a way to track which emails had already been reviewed when doing data hygiene projects like fixing issues like .con or emails without an @ sign. So one of the "official" policies that I was told to follow is now just useless to me in webview.

Please make this update to the unified view!!
we have used this field you many years to make tracking information useable! We track where contact information come from as well as details about web links and there is not a better place for this information to be stored that doesn’t create more work or make the information less functional!

It’s not okay to lose functionality when transitioning to a new system.

I frequently use Database View instead of Web View when looking up contact info, precisely for this reason. If you want us to move towards using Web View exclusively, show us the data we've added to improve how useful the contact info is.

In emails we put source or reason in Comments.

We often use comments to record the source of the email address. For example, if a constituent provides a new email address when signing up for the annual gala, we'll put: Source: Gala, or if a phone number of found through Nexis Public Records, we'll add: Source: Nexis. This is helpful to development officers if a constituent has a question about where we got their contact information from.

We use it on email ("phone") to track source of the email e.g. direct contact, out of office. Absolute necessity!

{"children":[{"type":"paragraph","children":[{"text":"We have a large number of records (married couples) with shared email addresses. This isn't an issue if only one constituent is included in an a list, but it can be an issue when both are on a list. Our email system only allows an email address to appear on a blast list once, so when both constituents are on a list, we use the email comments to determine which constitent should stay and which should be removed (based on a set of rules we've established). Utilizing these comment fields saves literal hours of least cleanup work. "}]}]}

Comment fields may seem extraneous but they're part and parcel for us to be able to make notes that regular database fields cannot accommodate. I often use the fields to do things like: clarify whose phone number is whose; when certain emails should be used over others; if I have to reorder or change the type of something, I can use the comment field to indicate last time it was actually changed so that we can keep a more accurate record of which number is oldest in our system; and it helps us with these extra bits of notes across the database (phone/email/link fields, sure, but also relationships, gifts, and solicitors. I LOVE the idea of an indicator of the note signatures and dates, but just making sure those comment fields exist at all (and are editable) in NXT is important, especially considering all the lost data those fields contain.

This would be extremely helpful. At the very least, tracking metadata for when things are changed and by whom is essential for data hygeine; sometimes this is available in database view but almost never in NXT. A comment field like this would go a long way.