08-08-2016 02:59 PM
We've stumbled through using APFW2013 for the last few years by keeping separate Leads and Customer databases. It does cause duplication in data entry when a lead becomes a customer, but I never could see my users being happy with the way the Company thing works in ACT.
Now I really need to find a way to put leads and customers in the same database. I've searched the KB and the forums, and everything I find about using it this way uses the Company feature (which is cumbersome and counter-intuitive imo) and doesn't do a good job of explaining how best to set this up and use it.
My concerns : Salespeople typically work with leads, only occasionally needing to look up a customer, so it probably won't change the way they use ACT much, BUT - I use the Leads database each week to run a lead report to get a lead count for all the salespeople (query by create date). I don't see how I could keep new customers out of this report?
Office staff work primarily in the Customer database. I'm seriously worried about retraining them to use Company (they've been using Contacts since ACT 6.0 - they've NEVER used the Company feature of ACT).
Is there a "quick and easy" way to separate leads from customers and easily tell the difference? I added a "Is Customer" checkbox in the Leads database so salespeople can at least see that when looking at a lead but it's
I guess I'm looking for you guys to either confirm my suspicions that this will be a nightmare and nobody will be happy - OR - tell me I've overlooked something wonderful that will make this easy for everyone LOL (well I can dream)
I guess what I've dreamed of is two databases in one - a link or button for "customers" and "leads" and something on each contact record that tells me whether it's a "customer" or a "lead". Seems so simple, yet so far out of my reach...
ANY suggestions, links to "how to", etc. GREATLY appreciated.
08-08-2016 11:46 PM
08-09-2016 07:29 AM