ASM Policy handling Emojis in JSON

As part of one of our mobile apps there is a functionality to send a message to support, obviously in this day and age everyone likes to use emojis. This causes the ASM to block these messages as they are quite rightly classified as Malformed JSON data. Has anyone else come across this situation and how did you get around it, I do not want to turn inspection off of this value parameter as its free text it could contain anything? It could be done client side within the app to parse out any emojis, just wondering if there is anything that can be easily done on the ASM.

For reference, the payload is simple:-

{
  "subject" : "subject text here",
  "message" : "message text here (this is where all the emojis appear 😊"
}