Email parser now supports execution of custom functions based on parsed data. In this case, the parser rule is not attributed to a particular module. Using custom functions helps you with extensibility and interoperability in Zoho CRM. You can extend the email parser function to more than one module within Zoho CRM, and even to connect with other Zoho services. You can also perform ad-hoc actions in third party applications based on the parsed data.

For example, based on an incoming email enquiry, a property management company called Zylker wishes to update both Contact and Account records in CRM. The name of the email sender, their phone number and address will go to the Contacts module, whereas their company information should go to the Accounts module. The same company has another requirement — based on an incoming email from customer regarding the status of their property, they want to update corresponding information on a third party listing website automatically.

They can achieve this via email parser using custom functions. Once you have the required custom functions written, you can associate them to the parser rule and have the action executed for subsequent incoming emails.

You can now configure email parser rules for different layouts under the same module. For example, if you have two layouts — Product enquiries and Service enquiries — under the Leads module, you can now parse data in the respective layouts and have your data organized right from the enquiry source. 

Update Record is a function using which you can update the latest information on a record from an incoming parsed email.

For example, say you receive an incoming email from a prospect called Jane Evans. Normally, a new lead record would be created for a new enquiry email but, if Jane is already in the CRM system, you want the CRM to update Jane's information on the same record as opposed to creating a duplicate record. If this is your expectation, you may check the Update Record option in the Advanced Configuration settings of the parser rule. Note: CRM will use the email field to detect duplicate records.

For the Update Record option to show up, you must have first mapped the "Email" field from the email content, which serves as the primary identifier or a "unique field" for a record. 

You can also choose the Send for Approval option, in which case, the records created via email parser will not enter active CRM database unless they are manually "Approved". To approve records, go to the respective module (Say, Leads) > Actions > Approve Leads.

In the Leads Approval page, select EmailParser records from the dropdown list. All the records created via email parser are listed. You can manually approve the ones desired, and these records will now be a part of the CRM database. 

In the new version of email parser, you are presented with accurate, detailed insights on the number of emails being parsed per rule, the fields extracted and a list of customized actions associated to the records created via the parser. This summary of details gives you a clear picture of how effective your rules have been and indicates the revisions you may need to make to those rules based on the insights. Detailed weekly performance reports can be sent to the creator of these rules or a custom email ID. Email reports are also sent on record creation failure, so that immediate action can be taken by the users.

You now have an option to reorder the list of parser rules based on order of preference. This is important because, the email parser system is designed to execute the first rule whose criteria is met by an incoming email. Therefore the order of the parser rules becomes essential for effective performance email parser. 

\

You can also filter rules by status (active/inactive) and also by module.