Customer RelationShip Management application

RE: Customer RelationShip Management application

alexc0002 — Thu, 10 Oct 2019 09:29:30 GMT

Thank you very much for the reply

RE: Customer RelationShip Management application

alexc0002 — Thu, 10 Oct 2019 09:29:09 GMT

Thank you
I already found the answer

RE: Customer RelationShip Management application

ChristineLHutchison — Mon, 07 Oct 2019 13:51:39 GMT

I think it depends on the importance and need to see the info. For example,

- If you have a record for a customer and the competitors is something that everyone will want to see to tell that customer's story, and not necessarily take action, then put it on the record dashboard

- If you have a record for a customer and the competitors is something that NOT everyone will want to see and doesn't have a direct impact on that customer's story, and not necessarily take action, then put it on a related dashboard

- I would not recommend 'hiding' that info in a process (related action) if people may want to see and that is it or need to see to determine if they should take action or not

Hope that helps a bit

RE: Customer RelationShip Management application

Mike Schmitt — Mon, 07 Oct 2019 12:42:26 GMT

If you could provide a bit more detail into your use case (i.e. perhaps a specific example), we might be able to make better suggestions for you. At the moment I'm not sure what, in particular, you mean by "provide information about competitors", not knowing the starting point / context / "information" in question / who it might be going to / what it might be intended to be used for, etc.