This page has been made for the benefit of the Zoho support team to understand how we are inserting leads from our websites, facebook and unbounce landing pages and get them into the Zoho CRM.

Any questions about this page can be sent to craig@jucra.com

Firstly: we are using WEB FORMS to insert to Zoho, not the Zoho api.

Secondly: we DO NOT use the physical embedded webforms generated by Zoho system, rather we take the html generated by those forms and use our own forms and then pass the form data over to Zapier via webhook which then passes it to our own api which then posts the form data directly to: https://crm.zoho.com/crm/WebToLeadForm using the html from the original zoho form.

The diagram below outlines the basic flow of leads from point of generation to insertion.

API DOCS FOR YOUR READING PLEASURE
Our api docs for the ZOHO_INSERT_LEADS is here: https://api.arcticspascore.com/docs/zoho_insert_lead/

POSTMAN Script
If you need us to share our POSTMAN script (getpostman.com) to test our api, please ask craig@jucra.com and he will send an invite.

WHY DO WE USE WEBFORMS AND NOT ZOHO API?
It was required by Arctic that all leads go through the leads approval flow however at the time (early 2018) the zoho api did not support lead approval so after testing we found that the web forms allowed lead approval settings.

WHY DO WE NOT USE EMBEDDED WEB FORMS ON OUR SITES?
We have around 20-30 forms multiplied by 150 +  dealers and on our sites we use Gravity forms which allows a certain amount of flexibility, look and feel. The webforms do not offer that. Also, we are generating leads from sources not supported by the Zoho webforms such as facebook and unbounce. Also, when a lead is generated we want to send a copy of the lead to our backup repos and customised emails to our sales team. The webforms do not allow complex customisations.

WHY DO WE USE OUR OWN API TO INSERT LEAD THROUGH WEBFORMS
When a lead is generated, our api will parse the lead. For example, if we grab the ip address, we are able to obtain the geodata such as country, so when we dont ask for the country, our api tells us the country name. In addition we can populate the description field with certain data not supported by the Zoho web forms.

WEBFORM SETTINGS
Here is the settings for the ZOHO_INSERT_LEAD web form at 10th of December 2019. This is logged here in the event that someone changes the settings without telling us.

Special Observations

  • OPEN ISSUE – On  4th of June 2020 have added the function to the zoho_insert_lead which shows the closest three dealers in the lead email that goes to salessupport.  Arctic is saying that the leads are being assigned incorrectly, however, this new function does not assign the leads as the zoho webform we are using merely assigns them to Sales Support as it did before, so there must be rule or workflow auto assigning the leads.
    Below is a screenshot of settings for the ZOHO_INSERT_LEAD form in WebForms in CRM (taken on 6th if June 2020)Below is a screenshot of a test lead email from get pricing now form showing the accuracy of the closest dealer function.
  • On 10th dec 2019 it was found that its possible to turn off the “do not allow duplicates” rules via the leads module which overrides the rule in the webforms, so when a duplicate lead is entered into the CRM it causes the lead entry to be handles differently.
  • On 1st of April 2019 there was a worldwide issue with SSL certs associated with Sectigo which provides all the Open SSL certs for Cpanel. This caused the webforms on Zoho to not work as we were trying to post to ssl pages on zoho which were not working and were sending back the wrong thank you message so all attempts to insert to zoho through webforms failed.  The issue with Zoho persisted for two days.