02-09-2011 02:22 PM
02-10-2011 08:41 AM
I am contemplating this same scenario.
I have an Act DB with 1000 customers and I don't want to pollute it with a bunch of dead, cold or even mild leads.
Do we create a whole separate DB to deal with them?
Or do you use something like Constant Contact?
Not sure what you found on this.
02-10-2011 09:19 AM
I do know this, you want to always use 1 DB. You should be grouping them and "working" leads through the sales process. So you should have even the cold and mild leads in there. You can always delete them if you know for sure they will never be customers but that is what a CRM is for. To work leads, have records, stay in touch with them.
Constant Contact is simply an autoresponder which has the primary function of staying in touch with the client via email and setting up premade emails so you can have that running on autopilot.
Hope this helps.
Can anyone please help regarding my issues I have?
02-11-2011 06:59 AM
Definitely one database is the best practice. Use Groups and dynamic membership to categorize your contacts and make it easy for you to see hot, warm, active contacts. With dynamic membership, they can move between groups based on their status.
Sage ACT! also has an e-mail/drip marketing tool (similar to but better than Constant Contact) that is embedded in ACT! that would help you stay in touch with those less than active contacts.
Havea great day.
02-14-2011 12:19 PM
Leanne hit the nail on the head.
Categorize the lead as appropriate.
Groups that are dynamically populated based on any contacts lead status can let you easily build outbound mail campaigns in which the message is targeted for the appropriate lead status (eg Cold leads get the "we haven;t heard from you in nine months" email, etc.
Only challenge will be ensuring people assign leads to the appropriate category. Making sure there are pre-defined guidelines as to what constitutes cold/warm/hot will be important. If people don't so this it isn;t Act's fault.
Expect once a year or six months you'll probably want to go through the entire databse and ensure nothing has been overlooked. Also, the Lead Status field you may want to define it as a required field, or at the least limit the options people can put into it.