Product

|
read

Product Release Notes - January

Welcome to the January product release notes! At Kronologic, we believe in continuous improvement. To that end, these notes detail the feature enhancements and new functionality we released in January!

Active Scheduling Algorithm

Bulk Instance Activation

Bulk can save a ton of time for the users by activating hundreds of initialized instances in one go.
The bulk activation switch is enabled when multiple initialized instances are selected at bulk. A very important caveat to this feature is that only the instances eligible for activation will be activated. This means that

• If an instance is already in an activated state, this switch will not have any effect on it.

• Instances already in the final state (Accepted, Declined, Engaged No Response, No Response) will not have any effect on them. And

• If there are multiple instances initialized for the same meeting type and contact combination, only one of the instances will be initialized to avoid a situation where the contact receives multiple scheduling emails.

Bulk activation

New Intent Recognition

Kronologic is now trained to interpret complex responses from contacts involving multi-date and/or multi-time suggestions. 

For example, for a response like 

“Can we talk Monday, Thursday, or Friday before 11 AM or after 3 PM Pacific?”

The AI interprets the day as well as time suggestions and sends an email and updates the calendar invite accordingly. The ongoing intent recognition improvements can reduce the number of instances moving to the “Requires User Intervention” state by as much as 10% giving users even more freedom by leaving the meeting negotiation to Kronologic.

Upgraded Accept Recognitions

With this enhancement, Kronologic can recognize when a meeting instance is initially declined but accepted later by a contact even if it is outside of Kronologic. 

Kronologic monitors the user’s calendar for 48 hours after an instance is declined to identify if the same or a different instance is subsequently accepted for the same meeting type - contact combination.

If such an instance is recognized, Kronologic further adds a message "Meeting subsequently accepted" to the meeting history. 

With this update, Kronologic can now recognize meeting accepts at least 20% better than before!

Operations 

Tags

One of the very powerful features released this month is the ability to tag instances! This feature allows users to tag and organize instances for better searchability and data management. 

Users can create a tag within the drawer that opens when the tags icon is clicked. Once created, users can also edit or delete the tags.

Tags features

The tags on instances feature also includes

Ability to bulk apply tags to multiple instances selected at once 

Instances can be filtered by specific tags via the header filter in the instances table 

Users can search a set of instances based on the tags applied to them through the search bar on instances table and finally, 

The CSV export now has a separate column for tags applied to instance and CSV export is responsive to the filters applied. 

Apply tags on csv uploadApart from the instances table, tags feature is also active for contacts imported via CSV upload. The feature will soon be rolled out to other objects within Kronologic. 

Upgraded Channel Logic

Relative Date

So far, for the channel logic the compatible data types were Text, Numbers and Date/Time. 

With this enhancement, we’ve gone a step further to enable time relative date fields. 

For example, referring to the attached screenshot, admins can define a channel logic where the Last Web Form Date can be set to last week or less that 60 days or is not last 8 hours etc. and Kronologic will base the logic around current day and time. 

The advantage this feature offers is that instead of manually choosing the absolute date ranges, users can rely on a broader logic relative to current date to import contacts.   

Another additional feature to the channel logic is the ability to add multiple comma separated values to the channel logic. 

Channel Logic

For reference, in the attached example earlier a user needed to create multiple blocks of logical conditions to import contacts. With this enhancement, that can be done in a single block by using comma separated values that are evaluated as OR statements.

Experiences

Logs Terminal

LogsAnother foundational piece of the platform released this month is the Logs. 

Logs capture all the activity across platform in real time and admins can see the entire stream of information at one place.  Currently logs are created when

A meeting instance status changes and 

A new user is added to the platform.  

Stay tuned for more log records in the future. This is an initial step towards further improved reporting and the functionality to filter and analyze the logs will be released soon in 2021. 

 

Originally published Feb 5, 2021 4:53:39 PM, updated

Topics: Product

Snehal Jogdand

Written by Snehal Jogdand

Snehal Jogdand is a dynamic business professional with 7 years of diverse industry experience. She is passionate about developing innovative solutions that combine cutting-edge technology with a deep understanding of customer needs. With an extensive background in both customer driven roles such as sales, marketing, market research as well as technology driven roles such as business analyst, product owner and scrum-master, she upholds tech-driven approach to problem solving.