3 ms·
The intended difference between contact and lead is that a contact is someone who you have some sort of a business relationship with -- either you are trying to
by kube-system 6y ago
The intended difference between contact and lead is that a contact is someone who you have some sort of a business relationship with -- either you are trying to sell them something, you are working with them, or have worked with them in the past. Leads are supposed to be wholly separate from that -- they might be a person, they might be a company, they might just be a rumor.
They way leads is originally intended to be used, is that you'd dump a bunch of garbage into that table -- b2c data from web forms, incomplete records, mass-imported lists from affiliates/events/etc -- and then it would be the job of sales to sort through it to find the records that are of any value. You wouldn't turn them into a contact until it was determined that there was an opportunity to sell them something.
But, leads as a concept really don't make sense in some industries. In many b2b industries, by the time you interact with anyone at a company, it's already well determined who you are and what product you're interested in. This is properly entered as a contact/opportunity.
- inthewoods 6y agoOh I get it. But as I said in another response below, what you're describing is the stage of a contact, not separate objects (in my opinion). You could just as easily have a single object but where the status was "lead" (no company name needed) and "contact" where you add the company information and the ability to add them to an opportunity.
- kube-system 6y agoYou’re right, it could be done that way, but for the orgs that do use leads, it would mean a lot of repetitive filtering on pretty much every business process. The difference in functional concept between a lead and a contact are great enough that processes (both software and human) between the two rarely overlap. A foreign key does all of this for free. For this reason, I think they made the right choice, especially since the orgs that do not like the concept of leads can just simply not use them.
- inthewoods 6y agoSadly it is not that easy if you do not want to use them - if that would true I would not be complaining.
- fellowniusmonk 6y agoAgree. I've built CRM's for multiple industries now, starting prior to any interaction with salesforce. There are many reasons to keep leads out of contacts, messy imports and the unstructured nature of what a "lead" can be are big ones, traceability, unauthenticated data capture issues and ease in reporting are a few others. It's always less of a kludge to have a system that keeps them separate but lets you seamlessly convert or associate a lead object into a contact object, when it makes sense (for lead objects that have sufficient similarity to a contact), and has an option to bypass the lead table and create a contact directly. In my experience trying to shoe horn into a _contact only_ abstraction creates more problems because the abstraction is too simplistic or even flat incorrect for many businesses. edit: From a sales agent "user" perspective you do often want to hide these abstractions from the UI depending on the industry and/or lead type, too many systems force their users into unnecessary duplication of effort.