Right now, throughout GHL, custom value and custom field merge field "keys" are visible in various places. The "keys" are the actual backend merge fields themselves, such as {{contact.name}} for example. These should never be visible. They can cause confusion throughout the system.

Only the names should ever be visible. This means in workflows, in email templates, in websites, everywhere, only the names should be visible. Using the same example, that would mean seeing Contact Full Name instead of {{contact.name}} every instance where it's used.

The reason this is meaningful is because, like I said above, the keys can cause confusion. When a custom value and custom field are created, the keys are generated and never change. So if I create a custom value and then change the name for whatever reason, after that the key may not match name.

When you're the creator of the custom value or custom field, this isn't a huge deal because you're not that likely to forget what you've created. The bigger problem comes with snapshots for customers and staff that you hire. Anyone who didn't create the assets and aren't familiar with exactly what they're referring can easily get confused about the fields when the names and keys don't match, and they choose the value/field based on the name, but then the key is displayed, etc.