PRE-ENROLLEE VERIFIER / ROTATOR / POSTER & ROTATOR ADMIN

PRE-ENROLLEE VERIFIER / ROTATOR / POSTER & ROTATOR ADMIN What is a Pre-Enrollee? A Pre-enrollee is a lead the has elected to be placed into a free Concorde Group Powerline by submitting their information. See [login to view URL] Please DO NOT enter your information since this is a live website. Purpose of “PRE-ENROLLEE VERIFIER / ROTATOR / POSTER?? Program: This program will 1) receive the proposed Pre-enrollee information then verify that the email actually exists, 2) select the rotator member that will receive the next Pre-enrollee, 3) post the information to a variable siteid at the above mentioned website, and 4) record then notify interested parties of the new Pre-enrollee. Purpose of “ROTATOR ADMIN?? Program: This program will is a way to add to or change necessary aspects of the Rotator Database. For a better idea of the program functions, please see the “non-operative?? interface that I have place at: [login to view URL] The program will written in VB Script (ASP) and HTML. The database will be made using Access. The platform is Win 2000. ## Deliverables I. The “PRE-ENROLLEE VERIFIER / ROTATOR / POSTER?? program will do the following functions: 1. VERIFY - Receive leads from an input form with the post method and positively verify the email the email address. It will function very much like the excellent program written by Zaid Farooqui at: [login to view URL] The only major addition, that the program must take into account, is that some people do not have HTML or may view their email offline. If this modification can be adequately performed automatically with ASP mail, then this is the preferred method. If not then the incoming input form will query if the user views his email via HTML, TEXT or Off Line. If they have HTML, then use the method in the example. If they have TEXT ONLY, then send them a confirmation letter. ·Standard Post Inputs: Email, Fname, Lname, Phone, City, State, Country, TimeZone, Calltime, Income, Participate, AdID, Campaign, ReferID, RotateID, Etype, OrigEmail, OrigFname, OrigLname, OrigFullname, Background, Record ·Calculated Input: LeadLevel (If Participate is not a number, then Participate is 0. If Income is equal to (“LT50?? or “Select?? or “NOYB??) and Participate is less than “2000?? then LeadLevel is “1??, else Lead Level is “2??.) ·Server Inputs: Date, Time, IP [login to view URL] ??" Read the Rotator Database to determine recipient of pre-enrollee. Based upon AccountID input from the form, pre-enrollee will either go to a recipient as determined by two levels of pre-enrollee rotators. While reading this description, please refer to the “non-operative?? interface that I have place at: [login to view URL] There will be four database tables for the Rotator Database; Account, Rotators, RotatorMembers, and MemberInfo. ·Account ??" The account table will have a seven digit numerical AccountID composed of a six digit number plus either a “1?? or “2?? based upon Account Type selected/used. It will also contain fields: DefaultSiteID, TotalDelivered, TotalPurchased, ActiveRotators and CurrentRound. ·Rotators ??" This table will contain fields: AccountID, RotatorNum, Round, Shares, NumDel, TotalDel, MaxDel, StartDateTime ·RotatorMembers ??" This table will contain fields: AccountID, RotatorNum, SiteID, Round, Shares, NumDel, TotalDel, MaxDel, StartDateTime ·MemberInfo ??" This table will contain fields: SiteID, Fname, Lname, Email To determine the Rotator recipient of the current pre-enrollee, the active rotators will be sorted by “Round?? then “NumDel?? and the top Rotator will be chosen. To determine the RotatorMember recipient of the current pre-enrollee, the chosen Rotator will be sorted by “members with more than 0 shares where TotalDel is less than MaxDel??, then “Round??, then “NumDel??, then “StartDateTime??. The top member will be selected and the NumDel & TotalDel fields will be incremented by 1 and then if the NumDel equals Shares then Round will be incremented by 1 and NumDel set to zero. Pass necessary variables to POST. [login to view URL] - Post verified lead to recipients website. This portion of the program is complete and tested. It will be the duty of the programmer to merge this code into this program. [login to view URL] ??" Once the POST has completed successfully: ·Indicate completion in the Verify Database ·Send email to Member & MasterList. (this programming item is complete, just needs to be merged with list program.) If POST does not complete: ·Decrement the rotator database ·Send error message to Admin II. The “ROTATOR ADMIN?? program will be web based and do the following functions: 1. Interface with all aspects of the Rotator Database. Please refer to the “non-operative?? interface that I have place at: [login to view URL] 2. The screen view will vary base upon the number of rotators chosen. 3. The members of only one rotator will be displayed at once as determined by the “Display?? radio button. ## Platform In summary, the majority of original programming will deal with the rotator database, rotator interface and rotator logic. Most of the other programming is already completed and only needs to be merged into a coherent project. If minor details change in the above, it will not affect the overall requirement that two useable programs as generally described above must be delivered for the contract to be considered complete. Support if needed will be included for three months. Programmer must use MSN Messenger for communication purposes. Platform is Win 2K with ASP. The Rotator Admin interface need only work with IE6+. The email must work with either TEXT or HTML as described above