back to top

Visual Analyzer Set Up (Part 5) The Leads KPI

Because we have run through the process a couple of times these posts on setting up the KPI spreadsheets start getting a little less repetitive and little more to the point.


I entered into my eval system as Lee Hogan and entered one Lead through the Insert Lead menu item. I refreshed the Visual Analyzer (VA) file and the Lead Dial now showed that Lee had 1 Lead in the database.



Seems simple enough, my next thought was what happens when I convert the Lead to a Contact in the database. I experimented around with my newly entered lead and used the Convert Qualified Lead wizard.  After the wizard operation was complete, I refreshed VA and noticed the Lead dial for Lee went back down to 0. I checked into the Leads table a little and discovered that my contact indeed did not exist and was completely transformed over to the Contact table.


Next, I did a search and found the newly entered Contact. The Contact record had a History record written in the database with a description of “Lead Conversion Notes”.  This provided the information I needed to draw the number of Leads a User enters into the system and also allows me to pull out the number of Leads that were also converted into Contacts.


For the client I am working with, I wrote the following SQL Script to help determine how many Leads had been converted to Contacts in the system.


SELECT     COUNT(sysdba.CONTACT.CONTACTID) AS ConvertedLeads, sysdba.USERINFO.USERNAME, YEAR(sysdba.CONTACT.CREATEDATE) as Year 
              
FROM         sysdba.CONTACT INNER JOIN
                   sysdba.HISTORY ON sysdba.CONTACT.CONTACTID = sysdba.HISTORY.CONTACTID INNER JOIN
                   sysdba.USERINFO ON sysdba.HISTORY.USERID = sysdba.USERINFO.USERID
WHERE     (sysdba.HISTORY.DESCRIPTION LIKE ‘%Lead Conversion Notes%’)
GROUP BY sysdba.USERINFO.USERNAME, sysdba.CONTACT.CREATEDATE


I then wrote this SQL Script to determine the number of Leads that the users had in the system by year.


 


SELECT     sysdba.USERINFO.USERNAME, COUNT(sysdba.LEAD.LEADID) AS UnConvertedLeads, YEAR(sysdba.LEAD.CREATEDATE) AS [Year]
FROM         sysdba.LEAD INNER JOIN
                   sysdba.USERINFO ON sysdba.LEAD.CREATEUSER = sysdba.USERINFO.USERID
GROUP BY sysdba.USERINFO.USERNAME, YEAR(sysdba.LEAD.CREATEDATE)


For each user, we looked at the number of Leads leads and the number of Leads converted to Contact for the last three years.  The clients top user had 905 Leads in the system for 2007, 127 were converted into Contacts.  This calculated out to 14% of the user entered as Leads had been converted to actual Contacts.  Using this information the client set the goal for each user at 600 leads for 2008/2009 with the hope that there would be a 10% conversion of leads to Contacts with a further hope that more then 50% of those Contacts will become customers.  This means 50 new Leads a month with 5 actually becoming Contacts and 2-3 becoming Customers while maintaining the Users current base.


We updated the Leads Spread Sheet as stated in previous posts.  Just remember the spreadsheet name within the Microsoft Excel file is KPI (4). Also, remember the evaluation users (like Lee Hogan) will continue to display until all of the KPI Spread Sheets are updated with your User base.


Tickets KPI is up next.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos