We have several types of calls: customer discovery, product demo, process setup and Q&A sessions. We always document the call results in Conversation entity that is linked to a customer/lead, and link all feedback from the documented conversation. Here is an example of the real conversation:
We use emoji to make text more insightful. Here is our scheme:
🎉 positive feedback
🚧 current pain point, a problem for us to solve
🚨 missing Fibery functionality
🙄 feature request — better be dug to 🚧
💡 our idea, born out of discussion
The number of emojis (from 1 to 3) describe the impact: from a 🚨 slight annoyance to a 🚨🚨🚨 showstopper. For example, on the image above there are several serious problems marked with 🚨🚨, but no showstoppers.
✔️ Solved: Using emojis is not an effective method to denote the severity of a problem. They are merely text symbols and cannot be quantified or used to calculate overall severity.
Solution: Now we can set pain level for the selected highlight.
When you review the conversation, the status of linked Insights and Features are not clear, it would be good to see more info here.