Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Hi Veronica.As far as I can tell. I only did a Convert. However there is another factor at play. The convert was not done in SF manually.I performed the Convert through RingLead, which is configured to "Convert Lead to Contact at Matched Account". Which (as far as I know) doesn't do a merge, even if...
Hi Steven,That's what I'm trying to say. The activity logged a "Convert Person", AND through that conversion, it appears that it also Merged a two records. So you, this makes sense that it then added the scores together, and also re-triggered the score campaigns, as the exclude reason didn't match t...
Hi Sant Singh Rathaur, Thanks for taking the time to respond. Yes, I agree that is an obvious test to conduct, however I am looking for expert community knowledge of these "reason" values and what exact situation they occur in. E.g. the reason "Merge lead" occurs when two people are merged. But que...
I just converted a lead to a contact in Salesforce, and then the record triggered a score update:This is despite having a criteria on our score triggers (which are global, not campaign specific) to exclude the "Lead merge" reason.Funny enough as I write this I've noticed that the Reason value in thi...
If we learn a person is no longer at the company, we must preserve their history at their previous location.If we do not know where they movedMark person record inactive Leave email address in tact along with all other dataIf we know where they have movedMark person record inactive Create a new pers...
Yeah I think that the dream of a single record for each person on the planet is flawed. You need to snapshot records and create new records if they move to a new account.
I think this has really helped. Thanks guys.We're adding an "Inactive" field. As we grow and we inevitably integrate our back office ERP with CRM, I have to consider that you have a record of a person at a customer account, linked to sales orders. Well it then becomes obvious, you can't update their...
Here is another one:A new event generates a new email address for the same person, at the existing company. The old email has bounced as invalid, the new one is good. Do you merge and keep the new email, or mark the old lead as invalid and keep the new dupe, attributed to the new event?
Or are you saying, only if the new information came from a marketing campaign? So dependent on source, take a different action.I am sure a solution like bizible would want to preserve the old inactive record, like you mention.
Hi Jay I agree with your thinking. That said, here is another thought.Imagine an account manager is on the phone to a customer and they find out some person is no longer there. Do they update the record to a holding company "whereabouts unknown" OR to the new account if they know what it is, or do t...