We send control messages mid-call to let the agent know about new information. We're expecting to see this message in the "conversations" field in any mid call webhook. We do see this message, however it is often truncated which is causing issues on our system. We send a json as this control message and when it's truncated we lose information. Could we stop this truncation? Ex:

{
        "role": "user",
        "content": "I sent it."
      },
      {
        "role": "system",
        "content": "[{\"type\":\"user-send-email\" [ some more characters] ..."
      },
      {
        "role": "user",
        "content": "Have you gotten it yet?"
      },

The most efficient solution to the problem of truncated control messages is to first contact the platform's technical support and urgently request a change to the configuration to increase the maximum character limit for the "content" or "conversations" field, as this is a data integrity issue that destroys structured JSON. If the platform cannot fix this, the immediate alternative is to refactor the JSON control message by using a minified format (removing all whitespace) and shortening all keys (e.g., using t instead of type or r instead of recipient_email) to reduce the total byte size below the current truncation threshold, ensuring the critical information is passed successfully.