Changelog
Follow up on the latest improvements andย updates.
RSS
fixed
Contact
Inbox
16/11/25 Bug Fixes ๐ ๏ธ
Here are the bugs that we crushed in this update ๐๐
- When creating a contact from the Inbox, the contact was not automatically linked to the Inbox ticket.
- Searching for a contact using their first name and last name in the Contact module showed โno contact foundโ even when the contact exists.
- When sending several messages quickly, one of the messages occasionally displayed as โsendingโ status.
- The bulk merge duplicate feature didn't display the list of duplicated contacts.
fixed
Flowbuilder
14/11/25 Bug Fixes ๐ ๏ธ
Here are the bugs that we crushed in this update ๐๐
- When uploading a document with Chinese characters, the file name or text was displayed incorrectly in the Flowbuilder module.
improved
Contact List
Round Robin Settings for All Contacts or Only Unassigned Contacts ๐ค
What's New:
You can now choose whether the contact list should assign contacts through Round Robin for everyone or only for contacts that have not been assigned yet. ๐
How to set it up:
- Click the pencil icon to open the contact list settings.
- Turn on the Round Robin option.
- Select the round robin users and select the lead source.
- Choose if you want it to apply to all contacts or only unassigned contacts.
- Click Submit to save your changes.
It helps your team stay organised so everyone receives contacts fairly without any manual work. ๐ผ
Note: Only the super admin of the organisation can set up Round Robin.

fixed
WA Personal
Inbox
12/11/25 Bug Fixes ๐ ๏ธ
Here are the bugs that we crushed in this update ๐๐
- Messages sent through the Inbox for the WA Personal channel would keep trying to resend even though the contact had already received them.
- In WA Personal Campaigns, the document name would automatically change and add extra numbers whenever a new document was uploaded.
- Quickly switching between chats in the Inbox would cause an error page to appear.
fixed
Inbox
10/11/25 Bug Fixes ๐ ๏ธ
Here are the bugs that we crushed in this update ๐๐
- When editing a flowbuilder that contains a smart delay action wiith 0 delay before triggering in Inbox, an error prompt would appear stating the delay cannot be zero.
- When a flowbuilder with text and image was triggered for Messenger or Instagram, the Inbox would show the message wrongly as two text messages and one image.
- WA API Broadcast messages would keep trying to resend even though the contact already received the message.
- When opening a previously sent email broadcast, the sender email shown would be incorrect.
- When updating the broadcast title for a duplicated broadcast, the new title would not be saved.
improved
Report
New Customer Retention Insights Report ๐
What's New:
We have introduced a brand new report that helps you understand how well you are keeping your customers. โจ
These insights help you see how valuable your customers are over time. ๐ก
Report module location:

Customer Retention Report view:

improved
WA API
Clearer WA API Broadcast Stats Info โน๏ธ
What's New:
You can now hover your mouse over the sent, delivered, read or failed numbers to see a simple description of what each statistic means. ๐ก

fixed
WA API
Flowbuilder
7/11/25 Bug Fixes ๐ ๏ธ
Here are the bugs that we crushed in this update ๐๐
- WA API Broadcast messages that included the shipping address variable were not showing the shipping address correctly when contacts received them.
- Contact replied to the WA API quick reply but the no reply condition was still executed.
fixed
WA API
Inbox
6/11/25 Bug Fixes ๐ ๏ธ
Here are the bugs that we crushed in this update ๐๐
- Notes created in the Inbox were shown in the wrong format.
- WA API Templates could not be submitted when the header type was set as media.
improved
Flowbuilder
Tag Based Flowbuilder Trigger ๐ท๏ธ
What's New:
Now you can make your flow start automatically whenever a tag is added to a contact. ๐
Just go to the Flowbuilder, create a new flow or edit an existing one, and choose the Tag Based option.
Once you have set everything up, the flow will run based on the channel the contact messaged in. ๐ฉ
Example:
If your flowbuilder is set to run on WA Personal, WA API, Messenger and Instagram:
โข When the tag is added to a contact who messaged you through WA API, the flow will be triggered through WA API, and if they also have messaged into the WA Personal, it will trigger through WA Personal too.
โข When the tag is added to a contact who messaged you through Messenger, the flow will be triggered only through Messenger.
โข When the tag is added to a contact who messaged you through Instagram, the flow will be triggered only through Instagram.

Load More
โ