Bugs Fixed:

1) Markdown in Interactive Templates Not Validated Across Translated Languages:

When creating an interactive template, if markdown formatting (like *bold*, _italics_, etc.) was added in elements such as buttons, headings, or footers — anything outside of the message body — that didn’t get delivered on WhatsApp. This was due to a limitation from Meta.

To address this, we have released a version 1 which validates the interactive content while creating templates. However, this validation currently checks only the language in which the template is created, not all translated versions.

For example:

If a template is created in English but the Hindi translation contains markdown in the button text, the issue would go unnoticed, and the message would fail on WhatsApp.

To fix this we worked on the validation which happens across all languages, not just the template’s original creation language.

2) Attachment Links Overwritten During Translation Import

Previously, when we imported a translation CSV into a flow, the attachment links (such as images, documents, or videos) for all languages were incorrectly overridden by the default language’s attachment.

This means that even if different languages originally had different attachment links, after importing the translations, all attachments got replaced by the default one, leading to incorrect or missing resources in flows for non-default languages.

This has been fixed now so when a translation CSV is imported:

• The attachment links in each language will remain intact.

• Only the intended translated text will be updated, without altering attachments linked to individual languages.

New Feature Added/ Enhancement done:


1) Custom Certificates: Raised by by KEF and ATECF

We recently launched this feature to provide personalized certificates and/or badges to the contacts upon completion of a certain task or action or a desired behaviour recorded through the flows.You can find detailed documentation here, please go through it for more information. 

2) Previously Restricted to Uploading One File at a Time When Creating an Assistant

Earlier, when creating an assistant, users could only upload one file at a time, which was not ideal for scenarios where multiple files needed to be uploaded. This restriction led to extra steps and effort, making the process less efficient.

Now, we have implemented this and users are able to upload multiple files simultaneously during the assistant creation process.


Documentation Update:

New Documentation Added:

1) Skip Validation: We recently added a new checkbox on the flow editor page while sending results that are generated dynamically (not pre-defined in the flow). Read more about it here

2) GCS Setup with UPI -This document provides a step-by-step guide for setting up GCS using the UPI method, making it easier for NGOs to complete the GCS set up process efficiently.