--- title: Product Release Notes - November description: New functionalities and feature enhancements released in October 2020 image: https://knowledge.kronologic.ai/hubfs/PRN-November-2.png --- [![Kronologic](https://knowledge.kronologic.ai/hs-fs/hubfs/KRONOLOGIC%20LOGO%20FULL%20COLOR-1.png?width=4931&height=537&name=KRONOLOGIC%20LOGO%20FULL%20COLOR-1.png "Kronologic")](https://www.kronologic.ai) - [Kronologic Home](https://www.kronologic.com) All tags - [All tags](https://knowledge.kronologic.ai/) - [Product](https://knowledge.kronologic.ai/tag/product) - [Sales and Customer Success](https://knowledge.kronologic.ai/tag/sales-and-customer-success) - [Channel](https://knowledge.kronologic.ai/tag/channel) - [Academy](https://knowledge.kronologic.ai/tag/academy) - [Inbound-Leads](https://knowledge.kronologic.ai/tag/inbound-leads) - [Support](https://knowledge.kronologic.ai/tag/support) - [Featured](https://knowledge.kronologic.ai/tag/featured) - [Meeting Type](https://knowledge.kronologic.ai/tag/meeting-type) Latest Posts - [Latest Posts](https://knowledge.kronologic.ai/) - [Oldest Posts](https://www.kronologic.ai/oldest-posts) - [Popular Posts](https://www.kronologic.ai/popular-posts) [Product](https://knowledge.kronologic.ai/tag/product) | read # Product Release Notes - November Written by [![Snehal Jogdand](https://knowledge.kronologic.ai/hubfs/SJ.jpg) Snehal Jogdand](https://knowledge.kronologic.ai/author/snehal-jogdand) - [mailto:?subject=I%20wanted%20you%20to%20see%20this%20site&body=Check%20out%20this%20site%20https://knowledge.kronologic.ai/product-release-notes-november](mailto:?subject=I%20wanted%20you%20to%20see%20this%20site&body=Check%20out%20this%20site%20https://knowledge.kronologic.ai/product-release-notes-november) - Welcome to November’s product release notes! We at Kronologic believe in constantly improving the product and the services being offered. In here, you will find the feature enhancements and new functionalities the Engineering team released in November!   ## **Active Scheduling Algorithm** ***Decline intent recognition *** Kronologic now has improved intent recognition. This means that the AI not only understands the contents of a reply message to a meeting invite but also interprets it to reflect the accurate status of the instance on the instances dashboard and decides whether the subsequent scheduling attempts will be continued or not.  ![Decline intent](https://knowledge.kronologic.ai/hs-fs/hubfs/Decline%20intent.png?width=459&name=Decline%20intent.png)    ## **Operations ** ***CSV Export*** Within the instances dashboard, Kronologic has the CSV export functionality that allows users to export all the instance-related information for further analysis. However, the data captured against the instances was limited to a certain number of fields. There are now many data points associated with meeting instances available for users that can be downloaded in a CSV format. On top of that, users now can have instance information at a granular level of each meeting attempt provisioned!  To understand this further, refer to the screenshot below. Now, after selecting “Export as CSV” on the instances table, an option to include attempts is enabled, which will include data for all the attempts. Moreover, the CSV export is now responsive to the filters applied. This means that, if there are active filters on the instances table, not only will the table reflect the relevant information, but those same filters will apply to the information in the CSV file exported.  ![CSV Export2](https://knowledge.kronologic.ai/hs-fs/hubfs/CSV%20Export2.png?width=800&name=CSV%20Export2.png) The table below provides an overview of fields available for export and their description. | **Logs** | **Data Point** | **Description** | | --- | --- | --- | | Meeting Specific Logs | Meeting ID | Unique identifier for the instance | | Meeting Type | Meeting type name associated with the instance | | | Instance State | Instance lifecycle state (Initialization, Scheduling, Final) | | | Last Activity | A timestamp for the last activity that was recorded. The instance-specific activity may include email received, instances status change, etc. | | | Current Attempt | Counter of the attempt associated with the instance out of total attempts scheduled. | | | Total/Maximum Attempts | Total number of attempts scheduled for the meeting type | | | Realized Value | This field reflects the Per Meeting Value associated with a Meeting Type only for accepted meetings. This field will have a value only if that meeting was ultimately accepted. | | | Instance Status | Instance status within instance state Initialization: •  Initializing •  Initialization Error •  Initialized Scheduling: •  Proposal Pending •  AI Negotiating •  Requires User Intervention •  User Intervened Final State: •  Accepted •  Declined •  No response •  Engaged No Intent | | | Start time | The start time of the meeting (same as proposed time) | | | User Name | Name of the user associated with the instance | | | User Email | Email for the user associated with the instance | | | Contact Name | Name of the contact associated with the instance | | | Contact Email | Email for the contact associated with the instance | | | Contact Timezone | Contact timezone considered in the platform for scheduling meeting attempts | | | Initialization Time | A timestamp for when the instance was initialized | | | Activation Time | A timestamp for when the instance was activated | | | Event Specific Logs | Event Type | Instance related events (Email sent, Email received, Status change) | | Event Time | A timestamp for each of the events captured in the event type above | | | Meeting Status | Captures the latest status of the meeting. | | | Invite Title | Title of meeting invite on the calendar | | | Invite Copy | Body for the meeting invite on the calendar | | | Email Subject | The subject of the email invitation sent | | | Email Copy | Body for the email invitation sent | | | Calendar Event ID | Unique identifier for calendar specific events i.e., Email Sent and Email Received only | | | Calendar Event Outcome | Captures the outcome for calendar events. The possible values here can be •  response\_needed •  accepted •  declined •  cancelled\_recycling •  cancelled\_error •  cancelled\_moved • tracked Note: The Calendar Event Outcome at its current state is mainly used for internal purposes to introduce new data points. The outcome of these statuses may not reflect actual statuses of instances. | | | Proposed Start Time (America/Los\_Angeles) | For a meeting invite, the calendar events captured are all the emails sent and received to/from the contact. Consider that the first email sent is from a user to a contact with a time proposal. This sent email will have a unique calendar event ID, outcome, proposed start time, and end time. Here the proposed start and end times are the proposed meeting start and end time from a user to a contact. Similarly, let's say the contact in response proposes a new time. For this response again, a new calendar event is recorded with a unique calendar event ID, outcome, proposed start time and, end time. This time, however, the proposed start time and end time fields capture the meeting start and end  time proposed by the contact to the user. Currently, these fields only show the latest proposed start time and end times across all the events captured. Stay tuned for having all the historic information available within these fields. Note: When a CSV is downloaded, the times captured are shown in the user's timezone and the timezone is mentioned in the column headers. | | | Proposed End Time (America/Los\_Angeles) | | | | Proposed Timezone | This field captures the contact’s estimated timezone. The timezone information is based on what is detected from a particular sent/received email to/from the contact. | | | Proposed Value | This field reflects the Per Meeting Value associated with a Meeting Type regardless of whether or not the meeting was ultimately accepted. For accepted meetings, this field should have the same value as the **Realized Value**. | |   The data made available via CSV Export is extremely useful for users from an analytics and reporting standpoint. Some interesting insights many Kronologic admins are obtaining from the data are:  **• ** Activation to Accept Duration**:** Average time taken to accept a meeting invite once a meeting instance is activated. **• ** Attempt Number vs. Accept Rate: Trend for meeting accept rate with subsequent attempts.  **• ** Best Time and Best Day to Attempt: The time and day of the week generating maximum meeting accepts. **• ** Best Accept Start Time and Day: The most popular meeting start time and day.  Being cognizant of the trends can further optimize meeting accepts for the users and can open a whole new dimension of being able to forecast and predict   **• ** Meeting acceptance probability  •  User by user Meeting Value  Along with the ability for **• ** Real-time copy coaching  •  Real-time Meeting Value Calculation    ***CSV Import Improvements *** The CSV import feature on the contacts page provides error feedback in case of data inconsistencies. We’ve gone one step further and now the error feedback also includes  **• ** Error message when a user tries to import an empty CSV file.  ![Error](https://knowledge.kronologic.ai/hs-fs/hubfs/Error.png?width=940&name=Error.png) **• ** Error message if a user selects “No header” but tries to upload a CSV with headers and ![header error](https://knowledge.kronologic.ai/hs-fs/hubfs/header%20error.png?width=423&name=header%20error.png) **•  Another addition is the sample row section that previews the data being imported** while uploading a CSV by showing the first row from the file.    ***Salesforce Campaign Object (beta)*** One of the most interesting features released this month is the addition of Salesforce Campaign objects to channels within Kronologic. Channels are the medium through which CRM contacts connect with Kronologic meeting types and vice versa.  ![Campaign Beta](https://knowledge.kronologic.ai/hs-fs/hubfs/Campaign%20Beta.png?width=493&name=Campaign%20Beta.png) Kronologic can now integrate with the Campaign Member object within Salesforce!  This integration will allow users access to leads/contacts/opportunity contacts for a single or across multiple campaigns. There are Campaign object-specific logic fields enabled for creating a channel using a campaign e.g., Campaign Type and Campaign Name. However, the feature currently is only offered for users opting in for the Beta Program. The feature is expected to enter General Availability early in 2021.   ***Inclusion of newly added team members in email-based routing  *** Selecting email-based routing on a meeting type will route meeting instances to the lead/contact object owner in Salesforce. Previously, the list of owners/users associated with that meeting type was static. This list is now dynamic meaning if a new member is added to the team assigned to that meeting type, they will be automatically added to the routing list.    ## **Experiences** ***Contact Page Improvements*** The contacts table on the contacts page of the platform has now been supplemented to include the “Last activity” column. This column is sorted by most recent activity by default and the entries in the last activity column once clicked show the entire communication and routing history for the latest instance provisioned for that contact.  ![Last Activity-1](https://knowledge.kronologic.ai/hs-fs/hubfs/Last%20Activity-1.png?width=800&name=Last%20Activity-1.png) The historic snapshot will help the admins understand who has most recently been in touch with the contact as well as what the most recent communication contained.  Another change on the contacts page is the highlighted section on the right which captures instance-specific data for the contact. Here, instead of indicating a current meeting attempt, the new “Activity” column shows information for each of the provisioned instances for the contact. ![Activity](https://knowledge.kronologic.ai/hs-fs/hubfs/Activity.png?width=472&name=Activity.png) The activity fields against each entry once clicked, bring up the entire communication history for that specific instance.    ***Gaussian Blur *** The instance-specific last activity details now incorporate the beautiful Gaussian Blur aesthetic that reduces the image noise and highlights necessary details. ![Blur without blanks](https://knowledge.kronologic.ai/hs-fs/hubfs/Blur%20without%20blanks.png?width=600&name=Blur%20without%20blanks.png)   ***Clear Instances Filters with One-Click*** The instances dashboard on the instances page allows filtering of provisioned instances by Meeting Type, Meeting Instance Status, or Date range selected. The “Clear filter” button on the top allows users to clear all the filters applied to the table with just one click! ![Clear filters1](https://knowledge.kronologic.ai/hs-fs/hubfs/Clear%20filters1.png?width=800&name=Clear%20filters1.png)   Originally published Nov 23, 2020 2:05:31 PM, updated Topics: [Product](https://knowledge.kronologic.ai/tag/product) ## Don't forget to share this post! - - - [mailto:?subject=I%20wanted%20you%20to%20see%20this%20site&body=Check%20out%20this%20site%20https://knowledge.kronologic.ai/product-release-notes-november](mailto:?subject=I%20wanted%20you%20to%20see%20this%20site&body=Check%20out%20this%20site%20https://knowledge.kronologic.ai/product-release-notes-november) - - ![Snehal Jogdand](https://knowledge.kronologic.ai/hubfs/SJ.jpg) ### Written by [Snehal Jogdand](https://knowledge.kronologic.ai/author/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. [Facebook](https://www.facebook.com/snehal.jogdand/) [LinkedIn](https://www.linkedin.com/in/snehaljogdand/) - Knowledge Base - [Product Videos](https://vimeo.com/showcase/9239396) - [Tourial Product Demo](https://kronologic.tourial.com/60913395475f590017f8aefc) - Integrations - Legal ## Related Articles [![](https://knowledge.kronologic.ai/hubfs/Product_Release_Notes_Sept_2nd_4.png)](https://knowledge.kronologic.ai/product-release-notes-sep-2nd-21-0-1-1) ## [Product Release Notes - September 2021 \[2\]](https://knowledge.kronologic.ai/product-release-notes-sep-2nd-21-0-1-1) Welcome to our release notes for September ‘21. Our Engineering Team has been so busy that we needed a second set of release notes for this month. These notes, published monthly, detail the enhancements and new features we’ve released. Continuous improvement is our focus, as always. ## **ACTIVE SCHEDULING** *Verified User* We are super excited to announce the release of the Verified User functionality. This is something that our existing customers wanted and we believe this opens up the possibility of expanding Kronologic to even more meeting automation! In a nutshell, this function allows any user with an email id (only Microsoft or Google email ids) to create a Kronologic account. When a user does this, they also provide “Read only” access to their primary calendar associated with this email id. Why is this such a big deal? When a user from a Kronologic customer organization uses Kronologic to schedule meetings, Kronologic has access to the Users’ calendar and proposes meetings which factor in the Users’ availability. However, the user is typically trying to set up a meeting with a  prospect whose calendar access, Kronologic does not have. Kronologic needs some interaction from the prospect, to understand their schedules better. However, many of our existing large customers find Kronologic so useful for scheduling meetings, that they schedule meetings with their colleagues in the same organization and also with people from their other organizations, outside sales situations. For instance, one of our largest customers has a number of channel partners that they work with and have frequent meetings with people in the Channel Partner companies. In these cases, the meeting guest is willing to share their calendar. If Kronologic has access to the meeting guest’s calendar as well, then Kronologic can propose meeting time slots which are available for both parties from the very first time. To enable this, we have launched the “Verified User” feature. This will ensure that Kronologic will get the meeting right almost every time, first time. Of course, our meeting accepts rates will sky-rocket up. To do this, anybody who is willing to share their calendar can create a “Verified User” account in Kronologic, and Kronologic as usual, will silently take care of the rest in the background. The verified user is only required to provide “Read Only” access to their calendar. Kronologic only reads availability information from the verified users’ calendar. Pretty convenient, we think. (what do you think? Let us know at [feedback@kronologic.ai](mailto:feedback@kronologic.ai)) So the next question is, How do I get my regular contacts a “Verified User” account with Kronologic? Pretty simple, actually. All you have to do is to send them a link to the login page of Kronologic which you regularly use. If you are already logged into Kronologic, you can get the link by just logging out of Kronologic and getting the link of the address bar in your browser. Logging out of Kronologic will take you to the Sign-in page. In the sign-in page, you will find the link “New! Create a verified personal account”.  ![](https://lh5.googleusercontent.com/bnR70eNXs9tTAgxmSysc07JKvthXdVowjujd0zVfxyb23dWouOHHTqRPRNrny_3fMjCkgK2JPvaYICHi6zrfhf7nGBEtieaAJoz375RUjZ_thTRyME4JxNKjwpgGPSRBlp9xDXKg=s1600) Click on that link and you will be presented with with the following page: ![](https://lh5.googleusercontent.com/7vOrVI3plso6rQPemxVq5otxju5QW_ItVgeci2LlPBhsJf-SzRyTVkgfBa-WUWm7qUp07a705mtA8AK-3w211zIBhRC29bVNyNEB5-9Xdt20HI5dFJoygvvVdtwglb_9Hme9pkbF=s1600) Choose Google or Microsoft email id and login into your account with the right credentials. After the standard warning about allowing access (remember, you are giving Kronologic only read permissions to your calendar, so we can find out when you are busy/free is all), you can see your Kronologic profile. ![](https://lh5.googleusercontent.com/SVzt_N822GL2mLXVhjN8KLYywksOizGfMZUrUz3XnF15byKmbHUu0ZNsMGhMVwB1frGHtiAS8LNGHmJGSRO2H4T0EkAXxUwRG-jQl7B_AKW9-1bKzqRlUPNgdbQIMu1rgT0jfcwf=s1600) Click “Update” and  you are good to go! Kronologic can now get “Read Only” access to the calendar associated with this email id, and whenever somebody tries to schedule a meeting through Kronologic with this email id, it will take the availability in this calendar into account, as well. As you can see, you can disable the “read only” access any time that you choose. In a sales situation, if you can get your prospective customer to share calendar availability with you, then getting a meeting confirmed is practically guaranteed. With a 30 second authorization, your prospect can now allow you to choose the optimum time for both the prospect and you - making the life of your favourite prospect just a little easier. You don’t have to get your prospect to choose from 16 slots over the next week, so you can sell something to them !!! (like some of our competitors make your prospects do) *Handle "Undeliverable email replies"* When users try to schedule a meeting with invalid contact email addresses, Kronologic now automatically cancels the meeting, if an “undeliverable” response is detected. In earlier versions, Kronologic did not auto-cancel the meetings, leaving it to the user to take the appropriate corrective action. However, we see from our users’ behavior that many campaigns have a number of invalid email addresses and typically, these meetings are abandoned. We have now changed Kronologic behavior to automatically detect email “undeliverable” responses and cancel the meetings, so we mimic our users’ behavior. ![](https://lh6.googleusercontent.com/sRFus62X32TXaPHU3pb_3L4RbX4jYwBouRSTIZjidP-qpb1XYf2GbSgU8oX1PfoTtWPlo5jWT-OlULN047erNGG5MRDL1y0sUX1ivD2YvwKBzBKc-28NRRgjn2BmXjaEskxUUQ-S=s1600) When a contact email id is invalid and there is an “Undeliverable” mail response, the user can see the status of the meeting as “Cancelled” in the Instances page. If the user opens the Instance details page, they can see the extract from the “Undeliverable” response to the meeting invitation. ![](https://lh3.googleusercontent.com/KyHq3KI0Xu6h70UzHz7V0CjQQZikYonQktKRN02mIKJ_awslW2GYLHPyhi8fWzPITwES-An2WVlSBWKOf4-nJBi_d07zNydK_xkW5kXia5AAK_4kzEoG41uWVV2Annz-6OOPtBCF=s1600) In addition to the above, Kronologic user also gets a detailed email in his inbox with the reason why the mail was not delivered. | ## **Address not found** | | --- | | Your message wasn't delivered to **kahssgk@ajhga.jh** because the domain ajhga.jh couldn't be found. Check for typos or unnecessary spaces and try again. | ## **OPERATIONS** ***Types Tag Automation*** The next step in Kronologic’s journey in Tag Automation is on the Meeting Types. As you may know already, meeting types in Kronologic can be assigned tags, which can be then used to segment, organize and filter meeting types. However, if you wanted to assign tags to Instances created with a particular meeting type or if you wanted to assign a specific tag to contacts associated with a meeting type, this can be done using the tag automation feature. This feature can be used in multiple ways to save time - for instance, a user needs to upload a few hundred contacts through the CSV upload feature, associate these contacts with a meeting type and then automatically get Kronologic to create instances for each of these contacts. The user also wants to tag these contacts with a unique tag for later identification. In this case, the user has  to locate the specific meeting type in the Meeting Types page and auto tag the contacts with the desired tag. All new contacts associated with this meeting type will hereinafter be tagged. On the Meeting Types page, a separate tab called “Auto Tag” is available now: ![](https://lh5.googleusercontent.com/GN6jDuUoVmc_NjGDjSQnQGXHASIWoPI0tu-XZUZGN-6ty7e3ZrdfghNx7CY69vWcFBjlm_Xa-JW88YkJvGb9OEqO8W0eMrMeAj2ixsN8MHMjaCb6nKMofEGaTg8XYFlyfDywLMjX=s1600) In the Auto Tag tab, click on any of the Tag Icon to pull out the Tags Drawer ![](https://lh6.googleusercontent.com/ql1GJSCzKmT8gj4sFBANx_jsfDXfHiyS86OJ68AiAZMk7PeXAHk4UJ-FmaS5YsyidzoQJbhnB4_8l_ZandUwXNl8yNrC0dpOk3-1dB7YTSgzq9pExE-32IGosAVt7SS13Y4BUcQb=s1600) From the Tags Drawer, any tag can be created / removed / assigned, as required. ![](https://lh5.googleusercontent.com/uJoUiFQycBB3GYYdUsNQP-MXAJXXqDtVK5EFbbLlRwOkQs6xqBKgAUqDQw_ITmSFray7kAjAmJdzPZEx9lyMRkgMVIOastVBWmTf3NQn9GhJvsOQHW48DoxKO3zZfudXt_JefwFr=s1600) ***User Management - Bulk Upload Time zone and Availability*** We have added some time saving utilities in the User Management page. It is now possible to select multiple users and assign availability for those users at one shot. In the User Management page, there are a set of blue buttons on the top row - the third is “Update Schedulers”. ![](https://lh4.googleusercontent.com/iFA8-7dkoA3wHBtwAR6lSqcLytSSae8W6QgB-7loqe-_5KbuVM74XVgiQsWkiitQ2EluxPcfxK4SNLnPx6nx5HfL2E00HDcwmQaUrYTKBJCSxDIaHvSSvGys4Fpq1FqMPWBnVYvo=s1600) A set of more than one users can be selected in the user table below, and on clicking this button, the days of the week available for scheduling and the start time and end time for each of those days can be set for all the selected users at one shot (as shown below) ![](https://lh5.googleusercontent.com/Hws4yWdgpO0isn2aX9ZcOYPpl3na3HAFo5aux9rtxPFuTIFpDwaWl4jRTW-rPM5ZSArjdvyMmRh4RVbaUdw6ENlkyjEky1UY7VOfZpovYqQXVMCGN-2w09F2T3F0vOdzmC5D2f-w=s1600) A very similar functionality has been provided for updating time zones for a set of users. Select a set of users and click on the “Update Timezone” button: ![](https://lh6.googleusercontent.com/PmMLryqSlo-moMAO6VvlZ307gTcfkJpP6G3vrt-FJrF0UlxTYCju3PFTT5AE2uPHPt6DCVjkU8spqRlwNOsDWYgec4mrSok21RfGMHaKzMHqW6lDJtrndjocedNOMVuIVVPF52a4=s1600) Now, select any desired time zone and on clicking the Update button, the selected time zone will be applied to all the selected users (the number of selected users are displayed on the left) ![](https://lh5.googleusercontent.com/xKSjbHVbLZjJfBXdMcgNhLI810UC1b1kCIdVUYY50aRa2nzCKcm60tp-yYWIkKsR-b81sNkjpB0Dm5fr4g1gj6Q6XGN0-THhZc_M7N3T-RDjuWlaj7eNOsyJBNiImBKjICdgNrAl=s1600) We continually improve our product based on your feedback. If you would like to provide insights in a short interview, please contact feedback@kronologic.ai. [![Product Release Notes September 21](https://knowledge.kronologic.ai/hubfs/Product_Release_Notes_Sep21_4.png)](https://knowledge.kronologic.ai/product-release-notes-sep-21-0-1) ## [Product Release Notes - September 2021](https://knowledge.kronologic.ai/product-release-notes-sep-21-0-1) Welcome to the September ‘21 Product Release Notes from Kronologic! The Product Release notes which are released at approximately once per month, detail the enhancements and new features & functions we released since the last Product Release Notes (Product Release Notes June ‘21) - as a product driven organization, Kronologic is committed to continuous improvement. ## **ACTIVE SCHEDULING** *Native Natural Language Processing* For understanding replies from Guests, Kronologic has migrated to a new Natural Language Processing tool called Merlin, specifically with reference to Time and Date Intent Recognition.  ## **OPERATIONS** ***Channels Tag Automation*** **All Kronologic objects can be tagged - providing the users the ability to categorize, segment and organize objects effectively. Now, Kronologic is embarking on a tag automation journey, with automatic tagging on the Channels - Import, Intercept and Update.** **Channels are an important part of Kronologic’s ability to allow users to communicate meaningfully and automatically with their CRM applications. Through the use of Import/Intercept/Update channels, users can import contacts and create instances automatically, deactivate instances where necessary and update specific CRM objects.** **When Kronologic objects are created/impacted by Channel operations, it can be very useful to tag such objects specifically, for later easy identification. Our Sep ‘21 release, we are happy to announce, incorporates Tag Automation for all three Kronologic Channels. Read on below for specific examples:** IMPORT CHANNELS **- Import Channels primarily import Contacts (Guests) from the CRM and create Meeting Instances with these Contacts (Guests). With the “Auto tagging” facility, it is now possible to identify such Guests and Meetings with tags, so that it will be possible to identify/filter these Guests/Meetings at a later stage.** **For instance, if a Team Lead with our customer decides to get her team to talk to every respondent of a particular survey - “Product A Renewal”. So, she creates an appropriate meeting type and an import channel to import all the respondents who are Contacts in their Salesforce CRM. Kronologic will then import these contacts and create meetings for each of these contacts. If she had created two tags, “Product A Survey Respondents” and “Product A Renewal Meetings” respectively for the imported Contacts and the meetings created, every contact imported through these channels will carry the tag “Product A Survey Respondents” and every meeting created will have the tag “Product A Renewal Meetings” associated with them. The team lead can then quickly identify these contacts and meetings by filtering on the appropriate tags on the Contacts and Meetings page.** **As usual, more tags can be associated with the same contacts and meetings if required. As can be seen from the image below, the user can choose to “Auto Tag” either the contacts or the instances or both with same or different tags.** **![](https://lh6.googleusercontent.com/14DKgVismeX4cVXm1YAh-KP6wU9N-0gcFAp-z_rFoU9Igymg2HAYvFpspdVNOiKQBiOc-PrItzv5pm2eXm2lMB3ot5ALUREeU3aI5NIpDSQBje7RZuByU4Oh_syoaaXT8CCcCUIq=s0)** **Clicking on the now familiar Tag Icon will bring up the Tag Drawer, which can be used for selecting existing tags or creating completely new tags for use here.** **![](https://lh5.googleusercontent.com/rTw1163q2WsKSnLprtMj2jjX32rU1_MV9rjsO3-RU_AunB55D6lnJs4HouwKaJaCPigCwcCcJ6tql5ep-r7qXZbY1ro8y4Z276lNqiTX9sKSsoEFUrF4rjqZHHhcgwfQOU1El6Tj=s0)** INTERCEPT CHANNELS **- Intercept Channels allow admins to create logical conditions once satisfied, and will deactivate existing meeting instances. This is useful when a method other than Kronologic has been successful in getting a response from the prospect and the seller or BDR wants to stop further meeting attempts that Kronologic has planned for that Contact. From the Sep ‘21 release onwards, the team admin can choose to associate such meetings and contacts with specific tags, just like in Import Channels, so such meetings and contacts can be identified later.** **![](https://lh3.googleusercontent.com/rxTUAy7J6u-eRFjxfbQt5m_dGCMidSxW2FIFxT8L_Y-ZK36zMQT8-c2H_NJH8iLBT7qaxnMVGjgYKvUujroyMZcK5HqMdiq2QJDf3ptX269yaTiCORa0AOrG2YkpBxzYRvAFlUiJ=s0)** UPDATE CHANNELS **-  Update Channels facilitate the flow of information from Kronologic to the CRM. An update channel allows admins to create logical conditions that once satisfied, allow Kronologic to update the relevant Salesforce object with pertinent information, such as updating the status, stage, or owner fields. Again, when creating such channels, it is now possible to “auto tag” these Channels, so that every Instance & Contact about which information is updated in the CRM, can carry their own, specific tags.** **![](https://lh3.googleusercontent.com/HomtnMetnoxp4vFuzbVp0cLg2vLGu8HG6o3McE7Rer2AlX3bYONYUufd-uMQkQrG3jz6R6r2_k7bamp0pVZKlxihjmZjcE9ZrfS1P0Jfra1PX1dZAhnrkP-gd7OylFncDVBV7Yqn=s0)** **These Auto Tagging buttons are available in the Channel edit pages as well, so that the user need not always create these tags when creating a channel. After creating a channel, the user can choose to apply these tags at a later stage or remove existing tags from the Channels as well. We think this feature continues the Kronologic tradition of enabling meaningful automation, which is completely traceable. Do let us know your thoughts about this through feedback@kronologic.ai. We’d love to hear from you.** ***Instance Creation simplified* In the Instances page, the manual creation of Instances has been simplified now. The user can provide just one of the three attributes to create an instance - Meeting type, Host or Guest - and a Meeting Instance is created. All validations are carried out when the Instance is activated.  This helps the User to create Instances manually at any time they choose. It is no longer necessary to create a meeting type first and a contact, before creating a meeting instance. If the user wants to create a meeting with a specific contact, they create a meeting with the contact and later realize that they do not have an appropriate meeting type for what they have in mind. At this stage, the user can save the meeting with just a contact, go ahead and create the meeting type and come back to complete the instance creation.** Just makes our User’s life a little bit easier, using Kronologic. Start creating a meeting instance … **![](https://lh5.googleusercontent.com/vtc9xtisuBKgDLkAc5xNtk6D8dScc5Ky4-iE1yZhdKlQLR6Vgt4K3HbT5WWaaivJxH2ohZ3bnBgk9o3bZssn5vBAtIpNdpnR7eL_yTAm2xDQzjBsBCI6AeTzorJDSqOPcvxrxr6P=s0)** **Meeting instance saved with just the Guest selected!** **![](https://lh3.googleusercontent.com/q-lmcHgoei8uQj3yX0LX_kf66dfySmB1lGO6X9QOSdR-MScjToq8TWQKKVQJtNOVBWhw8BnkCfyGspGnRsMhNfM-pYgORr9b9uOpcVlBMOvfGqi922zjF1AUsDk_20h6adJUS9aG=s0)** ## **EXPERIENCES** ***Collapsible Invite Details*** **In the Instances page, clicking on the Last Activities cell of the Instance table brings up the Instance details dialog. This dialog contains all the details of the Meeting Instance, like the Meeting Invite, the System Notes detailing each stage and status that the Meeting Instance went through, the email exchange with the Guest. It also provides the host the ability to override some stages of the Instance. Clearly, there is a lot of information in this dialog. We realize that this dialog can get to be fairly long with multiple attempts, and so we have re-organized this dialog. Now, the meeting invitation text is displayed separately in the dialog. The user can then close the meeting invitation to see the rest of the System notes and email exchanges. ** **![](https://lh4.googleusercontent.com/PlfOCsNo_GyCoCTBvmnDflwdNGql69p6_FGEdtevStcP4uTZXG6BkPU5-OWqmEsXQ9VQPh1qVPr0ldFVv4-c0fFFSEGEjj35STncYHRrAQZsgtig_5oW9j7chG-bKEiOHm52F71l=s0)** **If at some point, the user wants to refer to the meeting invitation again, there is a handy inverted caret icon on the top right corner of the dialog, which the user can click to pull down the meeting invitation.** **![](https://lh3.googleusercontent.com/VIdbgPX-tI0paKSM5m4-tedBO6nuDlX3UrJHlHFc7JLAWo-30nKBoyIhPGZ5RV-16BRQaC9EuC57qT145SWspAev6nU6s9pHjHbozFvFpCg46-I7VvasZLUg_mC9LkEEZrbV9QIc=s0)** We continually improve our product based on your feedback. If you would like to provide insights in a short interview, please contact feedback@kronologic.ai. [![](https://knowledge.kronologic.ai/hubfs/2021-08-06%2001_11_27-Release%20Notes.pptx%20-%20Google%20Slides.png)](https://knowledge.kronologic.ai/product-release-notes-june-21-0-1) ## [Product Release Notes - June 2021](https://knowledge.kronologic.ai/product-release-notes-june-21-0-1) Welcome to the June ‘21 Product Release Notes! This month is special - We are excited to announce the upcoming New UI for Kronologic. While all the functionality will be the same, the current Kronologic interface will be lifted and shifted to the new UI.  Why are we doing this? The New User Experience will be snazzier (We think so! We’d love your feedback...). It will also lay the foundation to support exciting new functionality that will be soon released. It also introduces new concepts and supporting vocabulary.  New Concepts and Vocabulary The Individual who is assigned to host the meeting is no longer referred to as the “User” but as “Meeting Host”. The “Contact” invited to a meeting is now referred to as the “Meeting Guest”. We now have independent Meeting Stages and Guest Statuses. The New Meeting Stages and how they map to the old are listed below: ![](https://lh4.googleusercontent.com/QugKMSONqdHDIgyjsOOLlf1TyFuED50WwFqUvNMxsLi1suAih1Bqi6Zj_dy6zapYuDt4gXhy5C4X-APSmu2N9ULHjsSPTHZeGGr0Qb88V9Y8TWtuR05M-_3peowvPfXMMxZzz6--) ![](https://lh3.googleusercontent.com/GFfohXVomm_JIDTcY0yRdjJLmM_3McsblFSP5d16Bg0rl16AGh43xlM2UzreQjJZwFTw_5ZRF8-BLuZSekmoxQW3M8e39oR98zgWWkEHvGJBX_kfqng6nZviXz73d-5IdcHs8z3w) ![](https://lh3.googleusercontent.com/lquf597hPe1ISLYXr2Iss0m8z2tgGePqtdfATUZZcjvjpuQaHr1PxeW4jylQJTYOPKUB4z1hPRGypz8Aa9kAnXoCcUUsUmn4__-uiWvvpLPx4_qijaAGyyoei9M_JR5Ne8IW0BhV) ![](https://lh5.googleusercontent.com/0KssuptvB7EEU4MVnK6QNJRp4HeYW9VSr6m0QsGqu74r5u_aG3AGvKrpYGFrdDriHAhoIQijt9nyAOC7xqpis83CBz1Nl7OCUhr6YlOSILSQgAEK4IEZMOSDglz44UofGfUtjUD3) Here’s a quick snapshot of Guest Stages and how they map to Meeting Instance Stages. ![](https://lh5.googleusercontent.com/KMAqVzkRV56vgsb_saftLoQcE1nI_kwVsDmXIg7rgpNB_DP6zx9M_SsmlVpNvE6-5CtU_AyuuKy8N5uIec-QWdUdruJqHFcLbn8l4R9BVVHJOqTzOke9-TmDW2qXBR7Iu2okP8mZ) Here’s a screenshot of the New UI: ![](https://lh3.googleusercontent.com/hHiGxSG2e2XAb_kf7k_XcHUJ6gR-sHmkl5UqHlZUIYUroy1l2oy6kxHToYkcST5YNbtzdsbGlCoG7yZBE2hRxQ9PLJLSmdVIzdt7pMziVNedBx2lv_8yjw2H9qYz7UsDvOg4Z1Pk) The Guest Status Summary reports in the top row of the Instance table page: ![](https://lh3.googleusercontent.com/LJLQsr2wYRsQ-erVzkGf1Dp17i6ZPWVE0xspXfSlaWF5O81Gl38om2YLmlVvmy5O_LtiIEk-HsKcdGEq4QXQWHAhCoY2FoUFEQhpjEtVLaF_KzJ-K_Q-erZqoTP-LfACLi4fSH_C) The next row is the Instance Stages Summary reports: ![](https://lh5.googleusercontent.com/_WJkXd2CQg9V5MYUUzNnHM7qNhwTPIWBDtWCLJxAZjROGrOPV9sxdSD_1XJBDjJTZP7XMezxEJ23jBFdTh_XUjJO5Z03ctIyjVZ07KCHyyVMbY0NR0zbKMAvc_5ZBgAzszN0eNsj) The new Meeting Instances table will look like this: ![](https://lh3.googleusercontent.com/zqR_X5qmtfYRvOCAgyQHpmJtQR1fiHBq_Gw4wbg5g8MYzjWNfPYfgAf6BkOM9wLoLU-wXPhcaTvBW-lWNVUS8HhKhG9QgmMqejM2Rx_wX8E0QiEuX9J6hIHN5v4BFr7RUTfYhKhc) Once our users are familiar with this new UI, moving on to more advanced meetings will be a breeze. The rest of the Release Notes detail the enhancements and the new functionality we released in the month of June ‘21, true to our credo of continuous improvement. ## **OPERATIONS** *Hubspot Update Channels* In CRM Integrations, the Update Channel function was extended to Hubspot from June ‘21. The Channel Update feature enables the Kronologic Customer to update the CRM when a meeting event happens. This can help in reporting from the CRM or as a trigger for further follow-up. Using the Channel Update feature, a Kronologic Customer can instruct Kronologic to update a field in a specific record in the CRM with some predefined value, when a defined Kronologic event happens. Check out this link to understand the [Update Channel](https://knowledge.kronologic.ai/creating-an-import-channel-0) feature in Kronologic in detail. This feature was available for our customers using Salesforce CRM. Now, our customers using Hubspot can use it too. ![](https://lh4.googleusercontent.com/pOjEi5zG6VGkiDiPSlX2nrb7_TdHFuYE_HYlzpmMKuo1lv4-W4sT1MM2w7lnYJHwj3zKPVoZ20NF_s0bNYqgM1IeanCXQRVN1L0HQ_nXKNno8Ok63bcFTQ4brhmmGW1IwBxvykOT) For example, in the screenshot below, a new channel update rule is being set up for Hubspot. ![](https://lh5.googleusercontent.com/ZRCRBsKp4Ka6Ym5_uhpCXVyVIW4OEyOByRv9b3LbMPxplE9t4Oya9GDTfuT9gg_V-FOmm4dHBIGizOpfcXcjIszKCja-Zskn9S9vJof-iGhbCc2zlFBkKR59uB2Syinrwsv7KWz8) For meetings of Meeting Type = “MG Type ROI”,  - When any Guest accepts, - Update the field “ID of first engagement” with  “Kronologic” AND  - the field Lead Status is set to “CONNECTED” on the Contact object in Hubspot for that Guest. Once this is set up, every time a guest accepts a meeting of type “MG Type ROI”, the corresponding Contact object will be updated in Hubspot. *Extract Sample Data from CRM to Test Import Channel Setup* When creating an Import Channel to import Contacts from the CRM, Kronologic now gives users the ability to get a quick preview of what data is going to be imported. A new “Sample” button on the Import Channels page will pull out and display contacts that satisfy the rules, for the last 3 days.  ![](https://lh3.googleusercontent.com/fztPfLzRsHa26YHRFcZ6uRA7G1X2-J2h2pp-7NxZXI2-isQfTJmJHj0p0vyzbbzlPpnalVHniQ_-0sWicMWf4a271CrMyW0FIawfgvv6cbwOiwB-IE2Fp_HHJ-jEEjBc1Pi0bZ5z) The data extracted from the CRM is displayed on the bottom of the page. ![](https://lh4.googleusercontent.com/YJ9_EZ23jc7-TKPrLpxSa4EO5S9ytYclXbnOWqxmse5bj6e332_HgcmMuSlO6GCK_OVi8RHMhjybEcomNgAzkXnfp2fURu_DaqPUKEg0kGrva_n6lDY54Ie3wZXDaikqu1CG2ubV) Please note that this data is not actually imported, but only displayed.  ## **EXPERIENCES** *CSV Upload Function on the Instances Page to Create Multiple Instances * Kronologic Users can import multiple contacts from a CSV file and initiate meetings in Kronologic from the Contacts Page. This functionality has been extended to the Instances page as well. In the Instances page, clicking the “Upload CSV”  brings up the familiar upload dialog. The User can select a CSV file to upload and map the headers to the columns in the CSV file. ![](https://lh3.googleusercontent.com/F8vRgC-S3_zYZJgOlX2KryMEXV3P9C2ru3km_izga_OfrhLRpI4mHd8bqO1o4jESJt70Gd2W0q2a21Laymh5CreenkwgWvz4nzHJhEeVe06fha3lSPH5R-okKdXZGiMc2VHmeVFv) ![](https://lh5.googleusercontent.com/oIltEJCzFxXEaReJTBywHdM4ldCVdoN3QJA-cAGRgVYPep7gsLFb2CleD-diWg1WTZkzALG7pJ8guDexkPKq6nNpja63PrGxRyZRxO_mT7OrpE_38MwNc-B0MXKz7jvsibKq0Q4F) After mapping the columns to the headers to help Kronologic make sense of the uploaded data, a meeting type has to be selected. This meeting type will be applied to all the uploaded rows. The user can also apply tags to the meetings to track them later. Once these selections are made, the CSV file can be uploaded. ![](https://lh6.googleusercontent.com/Kci5vR9U3ZR0yvR-Pp6lmx511gge2bLCtEGtpxzk14PsQgWbUbacqktZEFAEvZArgheL_QJVuED4YS7T4lChiTEXP2_UauMi1of38zj22HtjA26KcRHsQuAryU5iKBogeb6mvyFi) -------- We continually improve our product based on your feedback. If you would like to provide insights in a short interview, please contact feedback@kronologic.ai.  © 2022 Kronologic Inc.  |   Austin, TX    |    [Support](https://academy.kronologic.ai)    [Terms](https://www.kronologic.ai/terms)    [Trust](https://www.kronologic.ai/trust)    [Privacy](https://www.kronologic.ai/data)