Lead Management

We began working through the use of the NEW Leads Management feature  this morning. It feels like a "lead" is designed exclusively around a NEW contact and when we convert a lead to an opportunity, a new contact is created.

How can we ensure it is not a duplicate contact for a customer who has purchased already from us (meaning the lead is for a deal with an existing client).

 

Could the Dev team consider adding 2 features to this console...

  1. Checking Cache of existing contacts when entering a NEW lead?

  2. Could the Lead be for an organization (not for a contact)?

 

1

Comments

9 comments
  • Hi Dan. So glad to hear you're delving into our leads feature. I'm checking with Engineering to learn what processes are in place regarding lead duplication. I hope to report back shortly. Thanks! 

    0
    Comment actions Permalink
  • That addresses #1, thanks. what about #2? 

    Could the Lead be for an organization (not for a contact).. as we have many clients already and they have many staff, so they are an organisation who buys OFTEN from us and many different items?

    0
    Comment actions Permalink
  • I agree with you Dan on point 1.

    About point 2 actually I don't understand why you can use opportunities with those organizations with many staff that are already buying from you, am i wrong?

    0
    Comment actions Permalink
  • Perhap's I have not explained well enough. We are a staffing agency. The organisations we staff into have a procurement officer that controls the deal for all buyers in the company. Thus to enter that name (procurement person) it... a) makes 10 duplicate contacts when they buy 10 items per year. AND as this company is a major account for us, we assign account managers and thus to write a lead for that account as a Contact, its not indicative of the account activity nor indicative of the opportunity nor organisations LEAD. Example - we hear that Google is hiring 10 software testers (but as of yet we don't know the department nor the hiring manager) and to enter the lead we must put in a procurement person name (that we already have). Thus we cannot create a workflow nor action plan. Does this help?

    0
    Comment actions Permalink
  • Hi Dan & Daniele,

    As the last name field is required when creating a Lead there's no way to bypass a contact being created when that Lead is converted. However, another customer commented about this on a post here. Anthony Smith, our CEO and Founder, is also on that thread and paying close attention to everyone's feedback. And don't forget to vote up these posts and comments. Thanks!    

    0
    Comment actions Permalink
  • How can I convert a contact I've already entered into Insightly into a lead. They were entered as contacts before the lead module was opened up on my account

    0
    Comment actions Permalink
  • Hey everyone. Just a quick update regarding duplication when converting a lead. Right now, if a lead is converted and the individual already exists as a contact then a duplicate contact record will be created. Generally, a CRM workflow is linear - meaning if you have a contact you wouldn't have that person as a lead -this is why a duplication check isn't in place. However, this feedback has shown us this needs to be done so our development team will put in a fix in the future. 

    0
    Comment actions Permalink
  • Great Brenda! I guess the main problem is that most of us started using leads after having used only contacts for some time ...

    0
    Comment actions Permalink
  • Hi bruce! Our CEO and founder, Anthony Smith, has been noting the community requests to convert pre-existing contacts into leads and we plan to implement this in an upcoming release. You can see his comment on this post here. Thanks!

    0
    Comment actions Permalink

Please sign in to leave a comment.