1h ago
Add Context to Change Log Whispers
The whispers that appear are a great concept, but it feels like it's lacking a bit of context. It could simply be an eyebrow/tag needed just to frame it a little bit more concisely.
Essentially, what it's doing at the moment is just verbatim outputting the title of the change log item that has just been published. In principle, this is great, but it is lacking context and as a result it's very confusing and almost impossible to understand from a customer's perspective what it actually relates to.
As you can see in the attached screenshot, we rolled out a very simple tweak recently that added a WhatsApp contact field to an existing record type. I can't imagine a customer would ever understand that this represents a new feature update / tweak.
Not sure exactly what the best way to solve this is, but even just having an eyebrow above it called "Change Log" or "New Feature" or something like that (or perhaps better, would be to ise the existing tag that you can associate with a change log entry, such as "New Feature", "Bug", "Documentation", or whatever) would be immediately more helpful. I just feel as though it's very much orphaned at the moment and needs a bit of context or tagging to help customers understand what it is they're actually looking at.
Pending