Recent Enhancements in Zoho CRM

Recent Enhancements in Zoho CRM

Hello everyone,
In this post we will give a brief description about the list of enhancements that were recently released.

Additional configurations in Assignment Rule
  • Selecting users based on condition  
     In addition to selecting users based on category, you can define conditions based on which records will be assigned to the users such as, profile, country etc. For instance, you can set criteria that all records from India and US should be assigned only to users from USA.

  • Check user's availability before assigning a record  
     This is an optional step, which allows you to check the availability of the user based on online status (logged in to CRM) and/or shift timing before assigning the records.

  • Assigning Default User  
    A record may not be assigned to the selected users, if: 
    • The selected user is unavailable (not logged in or unavailable in shift).
    • The user has deactivated or deleted the CRM account.
      To avoid such situations, you can select a default user who will be the assigned the records in absence of the selected user. A default user can either be a logged in user (who has initiated the record action) or any other CRM user. 

      Refer to our        help document  for more details.


Updates to the data importing process 
  • Replacing empty values
     If any field in your import file is empty (does not have a value), and in case you have marked that field as mandatory in CRM; the record will not be imported. To address this, we let you define a value for the empty field while you are importing the records.


  • Changes in assigning lead source, record owner and adding tags
    Earlier, you were choosing values under assigning lead source, record owner and adding tags after completing the field mapping process. Now, we have moved these options under the Assign Default Value tab. From here, you can assign values for these fields as well as other fields. Refer to our help document for more details.

     
View and merge the duplicate records in unique fields 
You can arrest the creation of duplicate records by defining unique fields. Now, you will be notified if the value in any of these unique fields matches with an existing value. By clicking  view [record] you can check the existing entry, also if there are more than one duplicate entries, you will be notified to merge the records. Refer to our help document for more details.
 

Find out how Zia answers your questions
Explore in Zia, will help you trace the route that is taken to find out your answers. For example, it will show you the module from where she retrieved the answer, the criteria applied to sort the relevant answer and more.
 
Like, if you want to know the upcoming tasks, you will ask Zia, " Show my upcoming tasks ".  Explore will show you the module where Zia looked for the answer, in this case the Tasks module and since you want the upcoming tasks, Zia specifies the duration as criteria for getting the relevant answer. Refer to our help document for more details.


Additional groupings to view Dashboards
In addition to the existing categories:  Favourites ,  Created by Me and Shared with Me , the following have been added to view the dashboards. They are:
  • All - All the dashboards will be displayed.
  • Public - Dashboards that are accessible to all the users.
  • Favourites - Dashboards that the user has marked as favorite will be listed here.
  • Created be Me - User can view the dashboards that are created by them.
  • Shared with Me - The dashboards that are shared by other users.
  • Other Users' dashboards - Only the Admin or Super Admin can view dashboards created by other users.

    Refer to our help document for more details.

     
Mapping the fields in the subform for lead conversion
In Lead Conversion Mapping, the fields of a subform present in the Leads module can be mapped with the fields of a subform present in the Contacts, Accounts, or Deals module. The mapping can be done among fields with similar data type and field length. Refer to our  help document  for more details.


Sandbox refresh time has been reduced 
Earlier, you could refresh the sandbox account once in 30 days, now we have reduced it to three days. Also, earlier upon refreshing the  Deployment Logs the changes were not displayed, now the logs for the last six months will be retained. Refer to our help document for more details.