Lead Conversion with Contact parent and not Acount

(0) Share

Report

Posted on by Community Member

We have a situation where a new (cold) Lead comes in and is worked on in the Lead entity in order to warm the contact up.

The next stage of our Sales process is to either Disqualify the Lead or hopefully qualify the Lead into both an Account and Contact. Once we have done this, we then manually create an Opportunity for the Contact and progress with the sale.

The question I have is about the conversion of the Lead and I can see that the system has the following options:

- Create a Contacts and Account (this is what we currently do)

- Create an Opportunity and Contact - this assignes the Opportunity to the Contact record

- Create an Opportunity and Account - this assignes the Opportunity to the Account record

- Create an Opportunity, Account and Contact - this assignes the Opportunity to the Account record

- Create only the Opportunity and assign it to a Contact or Account (usd for existing accounts)

What we would like to do is convert the Lead into a Opportunity, Account and Contact but assign the Opportunity to the Contact record. Is there a setting anywhere, where we can set this as we only ever have opportunities with Contacts and not Companies.

I do hope someone can help.

Thank you.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

ScottDurow 21 on at

Like (2)

Report

Hi,

There isn't a setting to do this, but you can create a real time workflow that runs on create of an opportunity that sets the potential customer field to the value of the Contact field.

Hope this helps,

Scott

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Scott,

i was hoping for a setting and had not throught of the workflow option, I will have a look a this now as i am unsure how I will be able to selet the contact, once the opportunity has been created.

G

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Scott.

I though I would let you know that this 2was a lot easier than I thought, thank you.

For anyon else with this issue, I simply created a workflow with the following rules:

1. Check if the Opportinity 'Potential Customer (Account)', Customer = Contains data

2. If it does, update the opportunity potential Customer field with the Primery Contact of the account.

3. If not, close the workflow

Thank you

g

Was this reply helpful? Yes No
Sandy Devin on at

Like (0)

Report

We have a related issue. We notice if you have duplicate detection on, when you qualify a lead that would create a duplicate account or contact, a notification is presented allowing you to select an account and contact. If the you already have the account, but the contact is new, you would select the account and click continue, without selecting the contact. What results is that the Opportunity is created, and linked to the existing account; a new contact is created, but it is NOT related to the Opportunity; I built a background workflow that pulls the parent contact of the originating lead into the contact field of the opportunity and this works; However I really need this to be synchronous. Converting to a synchronous workflow fails. I suspect it has to do with the order of things done by the lead conversion. My workflow is triggered on create of an opportunity. Any ideas?

Was this reply helpful? Yes No
Suggested answer

Nuno 2,005 on at

Like (0)

Report
It can be done with a plugin on QualifyLead message on post-operation where the created entities can be accessed. Then those entities may be updated.

// created record from qualifyin lead EntityReferenceCollection erc = context.OutputParameters["CreatedEntities"] as EntityReferenceCollection; // get contact and opportunity EntityReference erContact = erc.Where(x => x.LogicalName == "contact").FirstOrDefault(); EntityReference erOpportunity = erc.Where(x => x.LogicalName == "opportunity").FirstOrDefault(); // update opportunity just created Entity opportunity = new Entity { Id = erOpportunity.Id, LogicalName = erOpportunity.LogicalName }; opportunity.Attributes.Add("customerid", erContact); service.Update(opportunity);

Was this reply helpful? Yes No