May has been an eventful month as well in Glific-land. As always, most of the features we’ve build (as listed below) are inspired from our interactions with NGO partners to help accomplish their use case better, smoother, with greater ease.
- Buttons support for template messages: Added support on the interface for staff and admin to see buttons interaction by the end-users. Earlier you would see the template messages without buttons, same as the submitted format.
- Natural language processing with Dialog Flow: With few NGOs wanting to test ML/NLP we’ve integrated Dialog Flow which can be used in flows to send responses to end-users based on their intent when a specific keyword doesn’t match. Check it out under split by intent
- System alerts: We renovated the way alerts and errors generated in the system are displayed. We’ve categorised them as warnings and critical and provided an easy click action to navigate to where the error occurred.
- Activate/Disable a flow: When a flow is not in use, you can simply untick the `is active` checkbox. This way, end-users sending the keyword will not be able to trigger that flow if you didn’t want that.
- Contact fields: While creating flows, you might be creating many contact fields such as @contact.fields.name for name to save data. Now you can manage all these contact fields from one screen and even edit any field. such as changing @contact.fields.name to @contact.fields.contact_name
- Webhooks update: Added support to fetch dynamic variable for the get request.
- Parent/child variables in flows: Added support for fetching flow level variable in parent and child flow. Thus the user input stored in child flow can be accessed in parent flow and vice versa.
- Upload attachment from flow editor: Now you can also upload attachments from your device in flows, provided that your GCS (google cloud storage) account is integrated.
To contact us, please write to firstname.lastname@example.org or hit the message us button at the top.