System and method for vehicle loan lead generation

Abstract

A system and method for generating loans is provided. The system and method of the present disclosure are generally designed to encourage previous and current customers of a financial institution to use the services provided by the financial institution as well as attract new customers to the financial institution. The system generally comprises a computing entity, a processor operably connected to said computing entity via a network, a server operably connected to the processor via the network, and a non-transitory computer-readable medium having instructions stored thereon, wherein said instructions include multiple user interfaces. The user interfaces allow customers to research vehicles in which they may buy. The system also provides users with information about vehicle financing as well as providing financial institutions with information they may use to promote their services.

What is claimed is: 
     
         1 . A system for identifying new leads comprising:
 a first computing entity having a user interface configured to access a vehicle finder application and a lead widget,
 wherein said vehicle finder application presents a vehicle details page via a display of said first computing entity, 
 wherein said lead widget acquires user data and vehicle data from a user; 
   a processor operably connected to said first computing entity;   a server operably connected to said processor via a network; and   a non-transitory computer-readable medium coupled to said processor,
 wherein said non-transitory computer-readable medium contains instructions stored thereon, which, when executed by said processor, cause said processor to perform operations comprising:
 receiving a session identifier code obtained by said vehicle finder application; 
 receiving said user data and vehicle data from said lead widget; 
 creating a lead based on said session identifier code and said user data; and 
 creating a plurality of targeted leads based on said user data and said vehicle data,
 wherein said plurality of targeted leads are at least one of said lead being targeted for a loan to purchase a particular vehicle, 
 wherein said particular vehicle was viewed within said vehicle finder application, 
 wherein each said lead comprises said session identifier code and said user data that is unique to said lead. 
 
 
   
     
     
         2 . The system of  claim 1 , wherein said user data and vehicle data are saved within a user profile associated with a user. 
     
     
         3 . The system of  claim 2 , further comprising a second computing entity having said user interface and a lead management application,
 wherein said lead management application presents said user profile as said lead.   
     
     
         4 . The system of  claim 3 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 creating a plurality of offer emails for said plurality of targeted leads using an email template chosen within said lead management application,
 wherein said plurality of offer emails pertains to said loan for purchasing said particular vehicle, 
 wherein said email template contains at least one place holder variable relevant to said user data of a targeted lead of said plurality of targeted leads. 
   
     
     
         5 . The system of  claim 4 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 placing a tracking tag within each offer email of said plurality of offer emails,
 wherein said tracking tag causes an email client to send a request containing an offer ID associated with said targeted lead to said server, 
 wherein said server parses said request for said offer ID in order to generate a vehicle upgrade page using said user data and said vehicle data that is specific to said targeted lead. 
   
     
     
         6 . The system of  claim 5 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 sending said plurality of offer emails to said plurality of targeted leads via said email client.   
     
     
         7 . The system of  claim 6 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 waiting for said request from said email client.   
     
     
         8 . The system of  claim 7 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 noting within said lead when said tracking tag causes said email client to send said request to said server.   
     
     
         9 . The system of  claim 1 , further comprising permission levels, wherein said permission levels are configured to limit access to said user data and said vehicle data of said lead. 
     
     
         10 . The system of  claim 1 , further comprising a script on a webpage, wherein said script requests said lead widget from said server, wherein said webpage is accessible via said user interface of said first computing entity. 
     
     
         11 . A system for identifying new leads comprising:
 a first computing entity having a user interface configured to access a vehicle finder application and a lead widget,
 wherein said vehicle finder application presents a vehicle details page via a display of said first computing entity, 
 wherein said lead widget acquires user data and vehicle data from a user, 
 wherein said user data and vehicle data are saved within a user profile associated with said user; 
   a second computing entity having said user interface and a lead management application, wherein said lead management application presents said user profile as a lead;   a processor operably connected to said first computing entity and said second computing entity;   a server operably connected to said processor via a network; and   a non-transitory computer-readable medium coupled to said processor,
 wherein said non-transitory computer-readable medium contains instructions stored thereon, which, when executed by said processor, cause said processor to perform operations comprising:
 receiving a session identifier code obtained by said vehicle finder application; 
 receiving said user data and vehicle data from said lead widget; 
 creating a lead based on said session identifier code and said user data; 
 creating a plurality of targeted leads based on said user data and said vehicle data,
 wherein said plurality of targeted leads are at least one of said lead being targeted for a loan to purchase a particular vehicle, 
 wherein said particular vehicle was viewed within said vehicle finder application, 
 wherein each said lead comprises said session identifier code and said user data that is unique to said lead; 
 
 creating a plurality of offer emails for said plurality of targeted leads using an email template chosen within said lead management application,
 wherein said plurality of offer emails pertains to said loan for purchasing said particular vehicle, 
 wherein said email template contains at least one place holder variable relevant to said user data of a targeted lead of said plurality of targeted leads; 
 
 placing a tracking tag within each offer email of said plurality of offer emails,
 wherein said tracking tag causes an email client to send a request containing an offer ID associated with said targeted lead to said server, 
 wherein said server parses said request for said offer ID in order to generate a vehicle upgrade page using said user data and said vehicle data that is specific to said targeted lead; and 
 
 sending said plurality of offer emails to said plurality of targeted leads via said email client. 
 
   
     
     
         12 . The system of  claim 11 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 waiting for said request from said email client.   
     
     
         13 . The system of  claim 12 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 noting within said lead when said tracking tag causes said email client to send said request to said server.   
     
     
         14 . The system of  claim 11 , further comprising permission levels, wherein said permission levels are configured to limit access to said user data and said vehicle data of said lead. 
     
     
         15 . The system of  claim 11 , further comprising a script on a webpage, wherein said script requests said lead widget from said server, wherein said webpage is accessible via said user interface of said first computing entity. 
     
     
         16 . A system for identifying new leads comprising:
 a first computing entity having a user interface configured to access a vehicle finder application and a lead widget,
 wherein said vehicle finder application presents a vehicle details page via a display of said first computing entity, 
 wherein said lead widget acquires user data and vehicle data from a user; 
   a second computing entity having said user interface and a lead management application, wherein said lead management application presents a user profile as a lead;   a webpage containing a script,
 wherein said webpage is accessible via said user interface of said first computing entity; 
   a processor operably connected to said first computing entity and said second computing entity;   a server operably connected to said processor via a network,
 wherein said script makes a request for said lead widget from a server; and 
   a non-transitory computer-readable medium coupled to said processor,
 wherein said non-transitory computer-readable medium contains instructions stored thereon, which, when executed by said processor, cause said processor to perform operations comprising:
 receiving a session identifier code obtained by said vehicle finder application; 
 receiving said user data and vehicle data from said lead widget; 
 creating a lead based on said session identifier code and said user data; and 
 creating a plurality of targeted leads based on said user data and said vehicle data,
 wherein said plurality of targeted leads are at least one of said lead being targeted for a loan to purchase a particular vehicle, 
 wherein said particular vehicle was viewed within said vehicle finder application, 
 wherein each said lead comprises said session identifier code and said user data that is unique to said lead. 
 
 
   
     
     
         17 . The system of  claim 16 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 waiting for said request from an email client configured to send a plurality of offer emails to said plurality of targeted leads.   
     
     
         18 . The system of  claim 17 , wherein said non-transitory computer-readable medium contains additional instructions, which, when executed by said processor, cause said processor to perform additional operations comprising:
 noting within said lead when a tracking tag of said plurality of offer emails causes said email client to send said request to said server.   
     
     
         19 . The system of  claim 16 , further comprising permission levels, wherein said permission levels are configured to limit access to said user data and said vehicle data of said lead. 
     
     
         20 . The system of  claim 16 , wherein said user data and vehicle data are saved within a user profile associated with said user.