Target list population and Sugar logic

[tsivula]

Hi,

I have been using Sugar mainly for customer database and sales forecasting purposes. Yesterday I succeeded in sending my first email campaign. As I am not a power user, I would need some advice on some of the conventions and use cases involved with Sugar.

1. What is the default use case that the Target List population function is designed for?
I have in total about 15 accounts and 100 leads. I created 5 separate target lists according to the industries of my customers. This use case seems badly supported by Sugar as when selecting leads only the Lead Source and Source description fields are displayed. One would expect that the fields shown would identify the LEAD, not the Lead Source so one could select the right lead. There must be something I am missing in the use case logic here, please advice.

2. What is the difference between a Case and a Project?
My company is a consulting firm. My sales process goes like: Lead - > Prospect -> Tender -> Project. Projects become Accounts. Of some reason I find this process rather badly supported by Sugar. How do other consultants use Sugar?

br, Timo
a newbie Sugar user.

[andopes]

Hi,

I have been using Sugar mainly for customer database and sales forecasting purposes. Yesterday I succeeded in sending my first email campaign. As I am not a power user, I would need some advice on some of the conventions and use cases involved with Sugar.

1. What is the default use case that the Target List population function is designed for?
I have in total about 15 accounts and 100 leads. I created 5 separate target lists according to the industries of my customers. This use case seems badly supported by Sugar as when selecting leads only the Lead Source and Source description fields are displayed. One would expect that the fields shown would identify the LEAD, not the Lead Source so one could select the right lead. There must be something I am missing in the use case logic here, please advice.

2. What is the difference between a Case and a Project?
My company is a consulting firm. My sales process goes like: Lead - > Prospect -> Tender -> Project. Projects become Accounts. Of some reason I find this process rather badly supported by Sugar. How do other consultants use Sugar?

br, Timo
a newbie Sugar user.

Hi Timo

1. What is the default use case that the Target List population function is designed for?

You can modify the columns of the Popup of Leads by copying the file modules/Leads/metadata/popupdefs.php into custom/modules/Leads/metadata/popupdefs.php and adjust the fields in there.

2. What is the difference between a Case and a Project?

A Case is an issue or a doubt asked by a customer, also known as a Ticket. Using Cases you can manage the Issues, Support life cycle and make sure all customers doubts and issues are being closed.
A project is a PROJECT. . For example: a project for an ISO consulting, a project for a software development, for a training and so on. Using project you can manage its tasks and life cycle.

Cheers