Record calls with non-customer contacts?

We are starting to think about CRM and have played around with it some.

Question: is it possible to store call log information about a contact who is not associated with a customer? We don’t want to go through the whole customer set up process just to record a conversation we had with someone, but we also do not want to record all such interactions outside the system.

Anyone run into this?

If I understand what you are asking
Then yes… you should be able to enter new calls directly thru “CRM Call Entry” without specifying a customer.

Where it might get tricky is later, when you want to search for and list those calls.
A couple things you could try

  • add a “Call Type” for non-Customer calls?
  • or maybe a BAQ Search where CustID is blank.

I can enter a call without specifying a customer, but it won’t let me choose a contact without having chosen a customer first.

That said, the system does not filter the results of the customer search by the customer you entered, so I can probably create a dummy customer for all the prospects until they become real prospects.

Or go ahead and enter the customer as a real entry but set it as a “suspect” or “prospect” as these are two additional customer types allowed in addition to “customer”.

Could do that, but we have a bunch of fields that are required when setting up a customer (even if suspect or prospect as the logic is in the Extended Table Properties or whatever it is) and we don’t want our customer set up team to get involved until there is a reason to.

Plus, our customer set up folks are not the same people making the calls.

Thanks.

Setup a customer named “Not Really A customer, but one we can attach a contact to, so that we can record call info for, INC.”

Edit:
Forgot the :wink:

Yep. That’s kind of where I was headed. I think we can later associate the contact with the customer so we don’t lose (or somehow have to re-create) the history.

Sam, have you investigated Epicor’s extended solution “CRM Lead Management”? Your description of your use case is essentially what the extended solution is designed to address.

Nope. will check it out. Thanks.