Recent Gainsight Assist changes introduce risks/challenges

I know lots of Gainsight customers were clamoring for the ability to select the Activity Type when logging an email through Gainsight Assist.  I do not dispute this may have been a handy feature had it been properly executed.

However, it seems this was released too quickly and with absence of thought regarding the downstream impacts:
 

1. Users can now choose an Activity Type, but they cannot fill out any custom/required fields associated with the type. This doesn’t save the CSM any real time/effort as they still have to go into Gainsight and edit the entry.
2. And if they don’t go edit the entry, custom fields get logged with ‘--’ (including required fields) which exacerbates dirty/inaccurate data issues.
3. Additionally, a custom/new Activity Type is really only necessary when there are data capture requirements that warrant custom fields on the layout for a single specific use case.  However, now that users can select Activity Type (but not any other field values) it is more difficult to make that argument and will result in a bloated list of Activity Types that could otherwise have been more streamlined.
4. Similar to this idea, there may be Activity Types that are reserved for very specific processes that we do not want users to select through GA. This can also exacerbate dirty/inaccurate data issues.  Enablement and documentation only get you so far - a common end user thought seems to be: “if something is possible, then it must be acceptable.”