06-23-2009 05:35 AM
A builder dealing mainly large projects has Contact records for: Client, Architect, Quantity Surveyor, sub-contractors, etc. However, some of these people will be involved in several projects. Correspondence for each of the projects needs to be kept separate.
The only way I can think of doing this is to have each Contact field set up as Projectname Firstname Lastname. This way, e-mail, letters, calls, etc. can be recorded against the specific project and a group created for the project to see a complete chronological History. However, each Contact may be in the database multiple times - once for each project they are involved in.
.....or is there a better way?
06-23-2009 06:17 AM
06-23-2009 06:17 AM
07-06-2009 05:16 AM
yes, using groups is one good way, but these projects are Opportunities. Use Opportunities.
Also correct, DO NOT use multiple contacts. Cheers - FSB
07-06-2009 05:24 AM
Hi Bill - yes that's another approach. I prefer to use Opportunities for all "pre sales" tracking. And Groups for all "post sales" tracking. It's an attempt to separate out the sales side of the business from the operational side. I guess you would set up a separate sales process called "Project" and track the work this way?
07-06-2009 05:54 AM
Yes you could prob do it that way.
Without knowing a few more specifics about these Projects, it seems to me that these Projects Are the Sales Opportunities?
And when one project is accepted or completed, then a Sale has hopfully resulted?
Seems like Each Project would possibly be a Product / Service?
Multiple contacts can be associated with each opportunity/product(Project).
That's basicly how it works for the Recruiting biz and our add-on product Fill Staff-10 For Recruiters Pro..
We created a Recruiting Sales Cycle(Not the ACT! sales cycle) and that may be what is needed here?
And then there is the Grouping option. Nice thing about ACT1 is: Options.
Often times, there are at least two ways of doing things.
Cheers - FSB