Contacts vs Accounts
We do business with Accounts, NOT Contacts. Invoices go to Accounts, they pay bills, products are linked to Acounts. Contacts come and go, they get hired or fired, they change departments.....
But, for new request I have to choose, mandatory, Contacts, while Accounts are automatically populated, but vice versa does not work. For example, person from company ABC calls that PBX extension 234 does not work. If company has 200 employees, should I have 200 Contacts? I have to dedicate the requirement to that company, and send technician to solve the problem, period.
The problem is also connected with Outlook integration, as Name and Surname are criteria for Contacts, and Company for Accounts. So, now I have too many Contacts, private, non private, over 1500, and need to know every person by name.
My suggestion:
- let administrator choose whom to dedicate the requirement, to Accounts or Contacts
- allow selective Outlook synchronisation, i.e. choose which Contact to synchronise
But, for new request I have to choose, mandatory, Contacts, while Accounts are automatically populated, but vice versa does not work. For example, person from company ABC calls that PBX extension 234 does not work. If company has 200 employees, should I have 200 Contacts? I have to dedicate the requirement to that company, and send technician to solve the problem, period.
The problem is also connected with Outlook integration, as Name and Surname are criteria for Contacts, and Company for Accounts. So, now I have too many Contacts, private, non private, over 1500, and need to know every person by name.
My suggestion:
- let administrator choose whom to dedicate the requirement, to Accounts or Contacts
- allow selective Outlook synchronisation, i.e. choose which Contact to synchronise