Re: Creating a workable cold call list
We use Sugar in a similar manner, but our database has about 15,000 names (working our way quickly to 186,000 names). We typically perform mail merge outside of Sugar, then our staff uses Sugar to perform calls (cold calls) to those we mailed and create a history with the client (schedule call, schedule meeting, history notes, etc.). We also use Sugar to perform our Email Campaigns (we elected to use it instead of DADA mail even though we licensed the pro version - I'm an old Mojo mail fan).
So, our workflow goes like this....
1. We acquire our data via subscription, list brokers and some handy dandy scripts that I wrote.
2. We merge all three data sources in a third party program.
3. There's some manual checking we do on the files (which are in CSV format).
4. The CSV files are used to mail merge (PRINT letters and envelopes - bulk mail, bar coded, CASS'd, duplicate checked, etc.)
5. The CSV files are imported into Sugar as LEADS. We chose LEADS (over targets) because it was easier for our staff to sign on and view the names (get phone numbers, etc.). If you view LEADS as a LIST, you can see the phone numbers to call. You can also modify the List template to show other data.
Note: anticipate how you will categorize your names before you import them into Sugar. We added three custom fields (source, target city, etc). It helps when you need to sort them out in Sugar. It also helps when searching/assigning the names to a staff person. You'll need to create the custom fields in Sugar.
6. We add the leads (by sort) to TARGET LISTS.
7. We create an email campaign and select one or several of the TARGET LISTS to send to.
8. After we see that many people have been opening our emails and clicking through (via trackers), we start calling them.
9. Our staff follows instructions to change the status of the Lead whenever 'something' happens with it.
Regarding your question about "Prompts..." We have it set up to email user upon assignment of a record. So, when we assign leads, the user is emailed (notified). Also, the next time they log in, they have a whole new list of names to pour through.
Sugar does a good job at displaying reminders for meetings and calls.
Our workflow has all new names imported as LEADS, then converted to Contacts or Accounts. It's a logical progression for us.
Misc. Notes:
a. Our staff experience varies. Some of them will take a list of names, call them, make handwritten notes and then input those notes into the computer later. Some of them will do everything via Sugar's interface.
Note: We've installed the Asertiva Firefox Extension for Sugar which some use as well. I customized the plug-in to accommodate our custom fields and include links to some of our web pages.
b. Using the Sugar interface was doggedly slllooooowwwww until we upgraded our hosting service to a Virtual Private Server and I got to tweak the PHP settings. Now it runs acceptably fast- fast enough to be on the phone with a call and enter data on the fly without burdening the tempo of the call.
Stuff we live with:
a. Importing is a bear. We are unable to import more than 1000 records at a time without 'something' messing up (although I think I'm close to figuring out how the planets need to be aligned in order to import more successfully).
b. Exporting data can be a bear. I usually do a mySQL dump to get large amounts of data back out of Sugar.
c. Look in the forums for other prevailing issues. What people are talking about is the rest of what we live with.
michaelest
sugarCRM OS 4.5.1e (build 1049)
PHP Version 5.2.3
Apache 2.2.4
FreeBSD 6.2-RELEASE #0:
Bookmarks