Known issues and limitations

No push notification when chat ends on Agent Workspace

If your account is using Agent Workspace, you will not receive a notification for the end of the Chat session. This is due to the termination of the session being different. We recommend your agent send a message before closing the chat to avoid uninformed termination.

Queue Position

Disabling or changing the default queue message requires overriding the zch_queue_position string resource with your own custom queue message. See Localizing the UI for more information.

Agent Avatars

Agent avatars that come from the Chat backend don't appear in the conversation thread, for API levels 16-19.

Offline Form not using VisitorInfo

The Offline Form will only use known information when using JWT authentication. VisitorInfo will not be used to prefill the information of the Offline Form.

Chat UI blank after going in and out of chat multiple time

Going in and out of the Chat UI, can result in the UI being blank. If this occurs, the chat session is still working and the UI will come back after a new event is received by the UI such as a message received or sent.

Keyboard does not close when leaving the Chat UI

Sometimes when you are typing in the Chat UI and you exit out of the it, the keyboard remains visible and you must manually close it. See Why is my keyboard not closing for a workaround that force closes the keyboard.

Department not set when using triggers to send greetings

Chat triggers that send a greeting to the visitor can interfere with the SDK setting a department. You can add a 'Still on site' condition to the trigger with a value of '1' to avoid this. This is the number of seconds to wait.