-
Notifications
You must be signed in to change notification settings - Fork 1
Contact object
The contact object is used by both location and property objects under the primary_contact attribute. It has the following attributes:
{
"name": "Anders Andersen",
"email": "anders@andersen.dk",
"phone": "12345678"
}Due to the internal structure of our system, contacts are stored as separate entities with a uniqueness constraint on the e-mail address. Because of that it is not possible for info@example.com to appear under different names or phone numbers in our system. When processing your feed, we group contacts by email address and use the first record. So if info@example.com appears under one location with "Sales department" as name, but under another location(or property) with "Jane Doe" as name, both locations will be saved in our system with "Sales department" being the contact.
In our system, contact entities are also users of our CRM system (which is why we enforce a uniqueness constraint on e-mail for sign in purposes). Contacts are never deleted from our system, so if a contact is no longer listed in any of your locations and/or properties, the contact is still able to sign into the CRM system.
Since contacts must have a password to exist in our system and since password is (deliberately) not part of the contact object specified above, we set a default password when creating new contacts encountered in your feed. Please let us know what default password you would like us to use, when we set up the Psync task for your feed. The contact may sign in after creation and change the password as he/she sees fit.