Hi, Chris from Airy here. Glad that you like it! Yes this was a very challenging problem. After many iterations we came to the conclusion that in general it's

Hi, Chris from Airy here. Glad that you like it! Yes this was a very challenging problem. After many iterations we came to the conclusion that in general it's best to have no opinion on the structure of the content that is being sent. So we store every message exactly as we receive it and do platform specific file interactions in a separate stream. We then store the results in a metadata topic and use that to render messages on-demand. This immutable approach makes retrying and storage migrations easy and safe. Regarding WhatsApp Business containers we are still waiting for them to wrap up their Beta. Currently we support WhatsApp and SMS via our Twilio messaging source (https://airy.co/docs/core/sources/whatsapp-twilio https://airy.co/docs/core/sources/whatsapp-twilio), but we definitely plan on making it a first class citizen. Hope I could answer your questions! :)