We have a situation where we are constantly running ad and tradeshow campaigns and seem to be in a bit of a quagmire.
All leads are imported in via CSV as sent to us from ad agencies and tradeshow hosts.
First, we import the company record as required by NetSuite importing rules. On the company record is the "Lead Source" pointing to the list of available campaigns. The import template includes the name of this campaign (lead source). If NetSuite finds the company record to already exist it skips it.
Problem #1: There is no way for us to know that we had this company at the most recent tradeshow or ad response since NetSuite did not add it since it already existed.
Next, we import the contacts. The contacts get sourced to the appropriate company record. If the contact already exists, NetSuite skips it.
Problem #2: There is no way for us to know that this contact was at this most recent lead generating event.
I know from the true sense of a "lead" that these should not necessarily be counted and that data integrity requires things to work a certain way.
1. Given the number of leads, I would think knowing we have interest generated from multiple campaigns would indicate a much higher priority lead to put attention to.
2. When reports are run on the capture of leads from the lead-generating event, it is inaccurate and I find myself explaining why the tradeshow host's says they gave us 1200 leads and yet NetSuite only shows 1053.
What would be ideal is NetSuite's import feature to allow a contact or company that already exists to be 'updated' with the new information. Even though the unique ID exists, allow for example, a multi-select field to add an additional line to the list. We could identify the lead source in this list and then perform searches on leadsource = today's lead source + any others to get high priority leads and we would know that the lead was properly captured when we look at results from any particular campaign.
I know we could possibly do things with duplicate records flagging but seems a very questionable way of handling this. Does anyone else have this problem? Has anyone figured a way around it given the current importing limitations? Could we do this better using XML importing or web services versus straight CSV importing?
Appreciate any insight or ideas.
Thanks.
-Steve