Bugs Fixed:

1) Gupshup credential setup was failing for New NGOs:

Newly onboarded organisations were unable to save their Gupshup credentials, which blocked them from getting started on the platform. As a temporary measure, we provided an alternative workaround so they could continue onboarding.

Fix:We resolved the issue with saving app-level API keys. New organisations can now complete their Gupshup setup smoothly and start WhatsApp conversations without any manual workarounds.

2) Voice File Search broken with new AI Architecture:

NGOs using voice-based file search (speech-to-text → AI lookup → text-to-speech) found that the feature stopped working entirely after our migration to the new unified Kaapi API. Voice queries were being routed to the old direct OpenAI path, which no longer had the assistants they had created.

Fix: The voice file search pipeline now correctly routes through the Kaapi-based API, matching the same path as text file search. Voice-based AI queries work again for all assistants created with the new architecture.

3) Assistant List Status Visibility:

The assistant list page showed no indication of whether an assistant was still being set up, ready to use, or had failed. Users had to open each assistant individually to find out was time taking when managing multiple assistants.

Fix: The assistant list page now shows the live status (e.g., in progress, ready, failed) for each assistant at a glance, so that NGOs always know which assistants are operational.

Enhancement Done:

1) Secure Google Sheets Integration — No more public sharing Required:

Previously, READ-type Google Sheets used in Glific had to be shared publicly (Anyone with the link can view) to sync data. For NGOs handling beneficiary data or sensitive program information, this was a real security concern.

What’s new: Google Sheet reads now use your organisation’s existing Google Service Account — the same one already used for write operations. Sheets no longer need to be publicly accessible. Instead, you simply invite the service account as a viewer on your sheet.
This brings read and write operations under the same secure, organization-level authentication model.

2) Read-Only view on Assistant Knowledge Base Files:

For  assistants created before March 2026 the Manage Files button was grayed out entirely, making it impossible for NGO staff to even see which files were associated with their assistant.

What’s new: You can now click “Manage Files” on a legacy assistant to view all the files currently in its knowledge base in read-only mode. While adding or removing files remains disabled (since legacy assistants require cloning for edits), you can now clearly see the file names — making it much easier to recreate or clone the assistant with the right files.

3) File Upload Throttling for AI Assistants:

There were no limits on how many files could be uploaded simultaneously when setting up an AI Assistant’s knowledge base, which could overwhelm the platform during large uploads.

What’s new: File uploads to assistant knowledge bases are now rate-limited and throttled on the backend. This keeps the platform stable for all organizations, even when uploading large batches of documents.



Documentation Update:

New Documentation Added:

1) Speech-to-Text and Text-to-Speech Capabilities in Glific:
Glific enables NGOs and organisations to provide real-time translation and transliteration across multiple Indian languages, helping them communicate effectively with end users in their preferred language. While webhook names still reference “Bhashini,” since January 2026, Google Gemini 2.5 Pro has been powering both speech-to-text and text-to-speech capabilities.Read more details here.