Jay
(@bluejay77)
Hi @kka3cx,
You’re right; for manual additions of Jetpack CRM contacts, email is not required. For the additions via API, however, email is required.
Generally speaking, we recommend requiring emails whenever you’re adding a CRM contact since the email serves as a unique key Jetpack CRM checks to avoid creating duplicate CRM contacts.
Requiring email and thus avoiding duplicates is even more relevant in case of API usage which allows bulk-adding. For example, imagine you are adding 300 contact records, but 100 of them turns out to be same contact. In this case, Jetpack CRM will be able to compare the email address and identify duplicates, so you’re not left combing through 100 duplicates and merging information.
In case that I don’t want to put random values to email field, are there any solutions?
If you’re treating phone numbers as unique values, you could put the phone number as the email, e.g.
[email protected].
I hope that helps! Let us know if you have any other questions.
Thread Starter
kka3cx
(@kka3cx)
Hi, @bluejay77
Thanks for advice, I’ve already made it like you said. But actually, It’s workaround solution. For example, if we fill users with incorrect emails, it could be unexpected behavior when crm owner will decide to export all contacts email addresses and make an email newsletter for all of them.
I know, that Jetpack is for small business mostly and email can be unique key in this case. But if you would like to expand the integration options for example for Voip and PBX, I advise you few features:
1. Make different unique key, like id or smt.
2. Add journaling for Chat and Calls with API support.
Jay
(@bluejay77)
Hi @kka3cx,
Thank you for your feedback! I’ll add your feedback as feature requests on your behalf.
Let us know if you have any other questions!
