Bugs Fixed:

1) Ensure consistent contact names across Contact Profile: Raised by 1 NGO Nayi Disha

Previously, contact names appeared differently on the left side of the contact field compared to the name captured under the contact name, causing confusion. Added screenshots below for reference

Before Fix:

After Fix:

2) Automatically mark chats as read when responding to users via Support Tickets : Raised by 1 NGO Nayi Disha

When sending a message from Support Tickets, it is directed to the user’s chat history page. However, even after the NGO staff replied, the chat remained marked as unread, with the green dot (unread status)still visible.

Both the above issues are fixed by making changes in the Glific backend



Enhancements Done:

1) Adding support for smaller, standalone nodes:

We’re simplifying things with a new all-in-one node for Voice-to-Voice. Earlier, the setup involved three different nodes:

• Voice-to-text with Bhasini
• File searches to get GPT responses
• Text-to-voice with Bhasini, including translations
  

Now, it’s just setting up a single webhook for smooth voice-to-voice interaction. Check out this documentation to learn more on how to set it up Read Here

2) Automate the process of enabling Message Events in Gupshup:

After the Gupshup was set up, we asked the NGO to enable message status events as an additional step while doing the onboarding process.

To reduce this step and manual effort we updated  the partner API  so that it  allow us to enable or disable message events directly.

3) Added warnings for HSM Template messages | Rejection reasons during submission:

Enhanced  the HSM submission process by adding warnings for known rejection reasons to prevent common mistakes. Buttons cannot include variables, newlines, emojis, or formatting characters like bold or italics

4) Geo locate with Google Maps Integration:

It was challenging to pinpoint the exact location of users.To address this, we integrated with the Google Maps API, allowing users to update contact variables automatically when they share their location.

Users can now easily share their current location pin. With Glific’s geolocate function, NGO’s can obtain details like country, state, district, city/village, ward, postal code, and address based on the latitude and longitude. This has been updated in our existing. Read Here 

Documentation Updated:

New Documentation Added :

1) How to add new contacts in bulk:

This feature allows NGO staff to upload a large number of new contacts into their Glific account and mark them as opt-in. This enables NGOs to initiate the first message to these contacts. Read Here

Existing Documentation Revamped:

1) Find the QR Code of BOT for opt-in contacts

We frequently receive queries about creating multiple QR codes for specific flows. The steps and all relevant information are detailed in our documentation.Read Here

2) Create Flow:

When creating a new flow, you have two options:

• Create from Scratch – This will take you directly to the page for designing a new flow.

• Create from Template – This will direct you to a page with pre-designed template flows that you can reuse. Read Here to learn more about its functionalities.