We added features to improve how your users manage customer contact preferences. Use the contact point address field to record customer mailing address information and consent. Store consent records for new contact point channels, or create your own, with the Engagement Channel field. Use the Policy option for Consent Read API calls to require explicit consent for contact channels in an object.
Store a New Contact Point and Customer Consent Information
To help you store more information about customers, you can now specify multiple addresses for an individual or person account. Use the Contact Point Address field to specify multiple mailing addresses, and add details about a customer’s contact preferences. You can also reference these records from a contact point consent record to store a customer’s consent to being contacted this way.
Customize and Store More Customer Consent Channels
To help your org better communicate with customers, you can use the Engagement Channel field to manage consent records for more contact point channels. For example, you can use the Engagement Channel Type field to specify a customer’s consent to be contacted through SMS or fax, when previously you could only indicate the contact point type phone. Even better, you can create your own Engagement Channel type to meet customers’ unique needs.
Improve the Accuracy of Consent API Calls
Use a new value on the Policy parameter to require explicit consent for any object where explicit consent can be recorded. With the new value on the Policy parameter, the API returns an infoNotFound response when consent for a contact point isn’t specified. Consent is only returned in the API response when your customers specify that they opt in to a contact point channel.