Introducing the all-new email parser!

Greetings,

We are pleased to introduce to you, a brand-new, upgraded version of the Zoho CRM Email Parser, which is packed with fresh features and has been completely redesigned to meet latest customers needs and their business requirements.

On that note, the Old Email Parser will reach end-of-life on June 1, 2023. After EOL, old email parser will not be available in your CRM account. In the spirit of preparing for this deprecation, we encourage all of you to try the all-new email parser at the earliest. In this post, we will discuss key pointers on the following:

— the improvements made in the New Email Parser

— how to prepare for deprecation of the Old Email Parser

What is the email parser?

Email parser is a data extraction tool in Zoho CRM that helps an organization in various business functions such as lead generation and information updates. It is designed to automate the process of adding records to Zoho CRM by extracting information from incoming emails.

Now, let's have a detailed look at the functionalities that we have brought with this enhancement.

Enhancements in the New Email Parser

The following are the enhancements you can now see when you switch to the latest version of the email parser:

1. Single parser email ID for all parser rules

Previously, for each parser rule there was a different parser address. It was often tedious to assign and keep track of a new parser ID for each individual vendors. The logistics involved in tracking and maintaining these parser IDs was itself often time-consuming. However, in the new version of the email parser, there's only a single, common parser email ID for all rules, meaning that regardless of how many vendors you're working with or how many rules you create, you can use one parser ID for all. This makes working with the email parser much easier and cuts down your setup and maintenance time significantly.

Also, a maximum of five approved parser addresses can be set up in common for all rules early on during the configuration.

2. A more powerful and intuitive configuration interface

In the latest version of email parser, the entire configuration interface allows free parsing and is highly intuitive, powerful, and, most importantly, user-friendly—unlike the previous version, which demanded rigid adherence to delimiters.

The email parser interface automatically gives you a preview of the parsed data on the same screen where the field mapping occurs, so it's easier to get a snapshot of all the fields that are being parsed.

There's also an advanced configuration tab which involves options for filtering emails applicable to the parser based on criteria and associating automated actions, such as sending for approval, updating fields, and assigning records to certain users based on assignment rules.

You can also parse HTML emails directly, as opposed to converting them to plain text emails first—which was necessary for the old parser. You can also create email parser rules for each layout in a module.

3. Custom functions: Configure the email parser without associating a module

The new email parser now supports the execution of custom functions based on parsed data. In this case, the parser rule is not associated with 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, let's say that based on an incoming email inquiry, a property management company called Zylker wishes to update both Contact and Account records in CRM. The email sender's name, phone number, and address will go to the Contacts module, whereas their company information will go to the Accounts module.
Let's say also that the same company has another requirement: Based on an incoming email from a customer regarding the status of their property, they want to update corresponding information on a third-party listing website automatically. They can achieve this by using the email parser to execute 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.

4. Update records and send them for approval

Update Record is a function by 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 named Jane Evans. Normally, a new lead record would be created for a new inquiry 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 can check the Update Record option in the parser rule's Advanced Configuration settings.

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, records parsed via email parser need to be reviewed and approved from the Waiting for Approval tab in the selected module in order to become a part of the CRM system.

5. Informative parser reports

In the new version of the email parser, you're presented with accurate, detailed insights on the number of emails being parsed per rule, the fields extracted, and a list of customized actions associated with the records the parser has created. This detail summary 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 those insights.

Detailed weekly performance reports can be sent to the creator of these rules or a custom email ID. Email reports are also sent upon record creation failure so that the appropriate users can take immediate action.

6. Reorder and filter

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

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

7. Contextual access to parsed emails

You can view not only the Configuration Info for each parser rule, but also insights based on parsed emails.

This way, from the perspectives of both parser rules and parsed emails, you can derive useful insights.

The "Email" tab lists the most recent email in your parser inbox, where you can check properties like parsing status, the rule used to parse it, and more. If the email has not met any rule, you may also create a new parser rule contextually from this email page.

You can also re-run an email in the event of parser failure if there's no match found, as well as parse emails in bulk. (Note that this is applicable only for the emails that have a template match and for which the parsing was unsuccessful.)

Preparing for deprecation of the Old Email Parser

For existing users:

Existing users, who have not already switched to the new parser can do so by clicking on the Switch to New Parser button. Rules available in both the parsers will be working simultaneously until the Old parser is deprecated, but the rules available in the Old parser will not be displayed in the New parser view, and vice versa.

It's essential to manually create the existing rules in the New parser because once the Old parser is deprecated, only the rules present in the new parser will function. Since there won't be any rules from the previous parser available, the new parser will require that you create all rules from scratch.

Please note:

Until the deprecation of the Old Email Parser on June 1, 2023, both the old and new versions will co-exist, after which, the New Email Parser will become the default version. .
The rules in the Old Email Parser parser won't be available once it has been deprecated. Therefore, if no rules are added to the New Email Parser , there won't be a parser to run. So be sure to write rules in the New Email Parser before the deprecation. Additionally, keep in mind that once your old rules have become obsolete, they cannot be recovered.

For new signups

For new signups, only the new parser will be available as the default feature, and not the old parser. There is no action required from users in new signups.