Customization of Sugarcrm.

Your missing and Can spam compliancy with your email marketing which is a major problem for all of your users. The coding requests here are real world examples based on my own experience of what I need programmed to effectively use your contact management solution.

Overview of use of the system:

Emphasis on email marketing and tracking. Team members Use data records that have emails. A typical record will have name, address, city, state, zipcode, birthdate, ip, date of recod, source of data. System has to be updated to accept these data fields and reference them. These data records we are using to convert leads into cases for insurance sales.

System is being used for my insurance agents that are all over the US. Email is primary means of initial lead generation.

Each agent purchases their own email pop accounts to distribute email and a hosting package. To avoid the spam issue having each team member buy their own domain, email and hosting package we defer the potential spam complaints that would cause the central sugarcrm server to taken off the web.

I have agents all over the US. Data for the system is imported by the ADMIN. Admin has the control to release data oldest data first to agent(team members) a specified number per a day. Our target was 10 a day. If there are not enough leads to meet the daily distribution that agent number increases as data comes intot he system that matches that matches their criteria. Hence if they are allows to get 10 a day and receive 5 one day and the next day if the leads matched up they would receive 15. The distribution of the data coincides with distance of the lead to the zip code of the team member. I will supply the zip code database that has the distance programming and formula. To determine this. Team member can select a minimum of All to 100 miles upwards of 50 mile increments for their states that select. Master reference point is the zipcode and state that is entered in their user account information. This is how the data will be distributed to the team members. The reason for the distance of the lead is that there is a physical meeting that takes place between the agent and the lead.

With their settings in place. Emails are sent automatically full name in the subject line and address in the body to the leads if the email is available. Emails are sent via their pop account they have supplied. The intial email is always a text based email.

Remove and bounce system. Custom subject line keywords for removes. Each agent can specify the keywords to look for in the subject lien to remove and email and never email that person again. Bounces read the emails message to indicate the email as a remove for the contact – hence lead moves to lead to call. Custom delete of email message in body and subject line. Email is deleted and not processed. Lets say aol gives a 554 blocking – email is good aol is just dumping us. Or they receive challenge response systems ect.

Custom email block as well where they can import emails that are to be removed.


The system will interpret if the email is opened if the email is opened then a follow up email is sent that contains a hyperlink (url). That goes to the domain name on the hosting package. An encrypted php code will reside on the basic hosting that collects information that is directly transmitted to the server. The code hides the ip address or location of the master server. This information collection enhances the lead for the Agent. The data to be collected and questions asked will follow. The lead form will be visible in sugarcrm and whatever the agent modifies in sugarcrm will reflect on the remote site they are hosting. Hence if they update values this occurs remotely. This gives the agent to modify the questions as they see fit.

Recap –
1. Email open tracking.
2. Remote php script collections. A simple php script that can be uploaded to an ftp. No database on hosting server is needed.
3. Automatic email and lead status updating for the Agent.
4. Email interpretation for bounce and removal.