CSM- identifying the risks associated with not using the OOTB Contact table (customer_contact)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi All,
From customer have been suggested to create a custom "Customer Contact" table instead of utilizing the existing OOTB Contact table (customer_contact) for the following reasons:
Want asked us to build a custom "Customer Contact" table instered on going with OOTB Contact table (customer_contact) table due to following reasons :
- Customer do not wish to include unregistered customers in the OOTB Contact table.
- Internal users also function as customers, and they share the same email address in both the User and Contact tables, which causes issues since their SSO is dependent on the email address.
Please help us in identifying the risks associated with not using the OOTB Contact table (customer_contact) and opting to develop a custom Customer Contact table.
0 REPLIES 0
