How do you track all the info?
7 RepliesJump to last post
I am cold calling a list of 2,500 names and trying to manage all the info.Call date, last live conversation, info learned, spoke with husband/wife, purpose of call, outcome of call, etc. Does anyone have some suggestions for managing the information? I am usining Excel, but find it a little cumbersome. Thanks.
I use index cards until someone becomes a prospect, then put them into ACT!. If money is tight, there are all sorts of free CRMs out there. SugarCRM is one, Zoho I believe has one as well (I could be wrong), but you should be able to find one without much effort.
I use Salesforce.com ( excellent ) and best of breed.
for clients and serious prospects.
I use the calendar function on Gmail; for all new prospects and client meetings.
I put all of my leads on the Sunday before the week and if you call someone and they’re not in it is super quick to move them up a week or 2.
No one falls through the cracks.
It works great and is free.
You can use Tasks to keep a list of all A prospects etc. and show tasks on the right of the calendar.
Once they become a client and go through the interview etc. I keep all serious notes in Salesforce. I still track of an appointment with them on Gmail Calendar though.
I understand how you are using gmail for appts and A prospects.
Tell me more about how you are managing the cell activity to 2,000+ contacts.
Is each one a separate contact, appt, or task?
I would have all names in a list or card
After a contact if there is any possible reason to call back ; their name goes on the calendar together with their contact info; and they get scratched off the list.
If disqualify prospect; scratch name off list.
Try to get all the names on the list scratched off or on the calendar… low iq theory.
If you meet with prospect from a call back from the calendar ; add notes to your crm/act/salesforce.com (best)
If you’re using ACT you can create a 2nd database to use while coldcalling. Then when they become a prospect move them to your main database.