Here is a PHP lead that I got. If anyone is interested in it, contact Ash Kumra ([email protected]).
Roger ---------- Forwarded message ---------- From: Ash Kumra <[email protected]> Date: Jan 29, 2007 4:28 PM Subject: PHP and E-Mail Position(s) To: Roger, My friend is looking for someone that is an expert in PHP and E-Mail for our CRM application. Below is an outline of they are trying to accomplish with their e-mail integration.They have a LAMP configuration. Single e-mails from each lead ¶ This would allow the end user to send a single e-mail when they are looking at a specific customer record. This is already partially integrated. * Templates for the end user to chose from. (See Template system) * Attachments. As part of a template, uploaded by the end user, or selected from a list of pre-uploaded documents. * Reporting (sent, opened, bounced, etc.) Event Triggered e-mails ¶ These can be marketing or informational in nature and sent either to customers, end users, or partners. * Event Examples: o New Leads - Leads that have just entered the system. o Date Triggered - B-Day, Closing Date (6 months after closing), Pre-Pay Penalty is expiring in 30 days. o Status Change - Moved from Open to Dead, Moved to Open, Processing Milestone Completed. o Daily, weekly, monthly management reports. * Utilizes templates (See Template system) * Events can start a marketing campaign (See Marketing Campaigns) * Reporting (sent, opened, bounced, etc.) Template system ¶ There is a basic template system missing the features below. * Utilize attachments. o Dynamic PDF creation based on customer information. * More advanced scripting. o Replacing more then just a single field. o Advanced calculations. o Rotating active sales agents info into the messages sent. * Security to restrict template access to specific groups. * Upload HTML templates or utilize built in editor. Newsletters and Announcements ¶ * These should utilize templates (See Template system) * Select customers on an add-hoc basis * Utilize tracking and reporting. Lead Management with regards to e-mail ¶ * Maintain a list of do not send e-mail addresses to check against on lead entry or import. * Each lead should be able to opt-out of each type of e-mail sent from the system (Newsletters, Event informational, Event marketing, Single, Announcements, etc.) * Double opt-in procedures for online newsletter signup. Bounce Handling ¶ The system will need to be able to read from a bounced e-mail box and interpret. * Hard bounces (mailbox does not exist) should automatically mark the lead for no e-mails. * Soft bounces (mailbox is full) will need to be handled based on the type of e-mail sent. * Unknown should be available for manual review and interpretation. Tracking and Reporting ¶ Should be able to identify standard e-mail marketing metrics including sent, open, bounce, clicks, unsubscribe, etc. Marketing campaigns ¶ This should allow for the setup of multiple e-mails to be sent. An example would be after a customer is marked as "dead-lost to competitor" they would receive a series of e-mails, a different one, once a week for 2 months following up to make sure they are being taken care of. * System events can trigger a marketing campaign. * Easily identify leads in a marketing campaign. * Easily remove leads from a marketing campaign. * There needs to be a good system to make sure a lead is not overloaded with e-mails because they got put into several marketing campaigns at the same time.
