In iOS, the PreChatForm and VisitorInfo objects work together to gather user information before starting a chat. The SDK uses the ChatAPIConfiguration's visitorInfo and department properties, along with the ChatConfiguration's preChatFormConfiguration data requirements. If any of these properties are nil or empty, and their corresponding data requirements are not hidden, the form will prompt the user to fill in the details. Users can skip optional fields, and the SDK will merge the entered data with the API configuration. If fields are skipped, the SDK falls back to the configuration details, and if those are empty, no details are sent.
The SDK then assigns the department and calls chat.profileProvider.setVisitorInfo(visitorInfo) with the VisitorInfo details from the form. This process ensures that the chat is initiated with the most complete visitor information available. For more details, you can refer to the originalZendesk article.
Before SDK Chat 3.2.0, Android handles PreChatForm and VisitorInfo differently compared to iOS. When the PreChatForm is enabled, the VisitorInfo gets erased entirely, regardless of whether the fields are required, optional, or hidden. To work…
From Android SDK 3.2.0 onward, the use of PreChatForm with VisitorInfo has become more flexible. The latest SDK allows for a more seamless integration of these features, enabling you to set visitor information more effectively during a chat…
Yes, in iOS, you can use both PreChatForm and VisitorInfo simultaneously. Initially, the idea was to use one or the other, but this has been updated to allow both to be used together. The SDK will show the form to the user if the underlying…
If you encounter issues with the code provided in the Zendesk article, it's important to note that the article is for instructional purposes only, and Zendesk does not support or guarantee the code. You can post any issues you have in the comments…