Zend.Com
Tue 6 June 2006, 11:20 pm GMT +0200
we need to build a CRM campaign system based entirely on file naming.
For example, the file
current_file/purpose_purchase/state_NV/Borrower/Friday_001.htm
Would result in an email to the Borrower, the first friday after creation, IF the current file is a purchase (vs. refinance) in the state of Nevada.
So the system checks for existence of files at a user-defined location and/or our default internal file system. Whatever is found is then logged and later sent via a cron job.
Please let me know a time/cost estimate to build this, it fits into a much larger program specific to the mortgage industry.
There are several file-naming conventions FYI
root>>>
lead / current_file / closed_file
a variety of category subtypes, all the specs are in a word doc, there are about 5 subtypes which are all based on an easy user-defined variable i.e. source (newspaper ad? realtor referral? etc.), state (california, nevada, FL...), occupancy (2nd home? investor/rental?), etc.
there are also folder defining WHO gets the message, i.e. the processor working on the file, or the appraiser, or the borrower, or realtor, etc. - these are all party_01, etc. but also need to support aliases i.e. party03 = Listing Realtor
and then timing is defined just by file name, i.e. day_006.htm = 6 days after creation regardless of weekday, but friday_012.htm = 12th friday after creation; also status is used i.e. status01_plus_002.htm = 2 days after the appraisal is ordered (status01).
We support html based email, SMS as formatted email, fax as formatted email, and tasks which are txt files and get inserted into a type of to-do list.
For more info about this job offer click here
For example, the file
current_file/purpose_purchase/state_NV/Borrower/Friday_001.htm
Would result in an email to the Borrower, the first friday after creation, IF the current file is a purchase (vs. refinance) in the state of Nevada.
So the system checks for existence of files at a user-defined location and/or our default internal file system. Whatever is found is then logged and later sent via a cron job.
Please let me know a time/cost estimate to build this, it fits into a much larger program specific to the mortgage industry.
There are several file-naming conventions FYI
root>>>
lead / current_file / closed_file
a variety of category subtypes, all the specs are in a word doc, there are about 5 subtypes which are all based on an easy user-defined variable i.e. source (newspaper ad? realtor referral? etc.), state (california, nevada, FL...), occupancy (2nd home? investor/rental?), etc.
there are also folder defining WHO gets the message, i.e. the processor working on the file, or the appraiser, or the borrower, or realtor, etc. - these are all party_01, etc. but also need to support aliases i.e. party03 = Listing Realtor
and then timing is defined just by file name, i.e. day_006.htm = 6 days after creation regardless of weekday, but friday_012.htm = 12th friday after creation; also status is used i.e. status01_plus_002.htm = 2 days after the appraisal is ordered (status01).
We support html based email, SMS as formatted email, fax as formatted email, and tasks which are txt files and get inserted into a type of to-do list.
For more info about this job offer click here