Webhooks Transmission Issue Update

We encountered a temporary issue where updates to customer information (e.g., contact details, marketing preferences) and customer deletion data were not being transmitted via webhooks. Here’s an overview of the issue and the steps taken to resolve it.

• Issue Occurrence Time: November 1st, 2024, 12:40AM – November 12th, 2024, 3:37PM KST

• Scope of the Issue: Only channels using webhooks were affected, and customer information changes (contact details, advertising preferences) and customer deletion data were not transmitted to the registered webhooks.

• Cause of the Issue: The issue was caused by an error during a recent deployment.

• Action Taken: The code in the affected area was corrected, and measures have been implemented to ensure the information is now transmitted correctly.

As of November 12, 2024, 3:37 PM KST, webhooks are functioning normally. We sincerely apologize for the inconvenience caused by this Channel Talk deployment issue.

We kindly request your development team to execute the non-operated webhook once by referring to the guide provided below, using Channel Talk's Open API.

Please note that deleted customer (user) information is no longer retained by Channel Talk, so we ask for your understanding in processing this matter directly.

1. Gather your internal userids corresponding to Channel Talk users' memberId

2. Use the client's internal id to call the Get user by memberId OpenAPI

3. After receiving the response for the user, compare the following fields to ensure they match with the user's data stored by the client:

   (Note: The mobileNumber field appears in both user.mobileNumber and user.profile.mobileNumber. Both values are the same. email field is also the same.)

   1. mobileNumber

   2. email

   3. unsubscribeEmail

   4. unsubscribeTexting

4. If the values differ, assume that a webhook request with the following request body value: “event”: “upsert”has been triggered from Channel Talk. Proceed with the webhook logic registered in Channel Talk.

1. Collect the client’s internal user IDs corresponding to Channel Talk User (Customer) memberId.

2. Call the Get user by memberId OpenAPI using the client’s internal user id.

3. Check if the user's type field in the response is “unified”.

4. If it is “unified”, assume a webhook request with“event”: “delete”has been triggered from Channel Talk, and proceed with the webhook logic registered in Channel Talk.

1. Collect the client’s internal user IDs corresponding to Channel Talk User (Customer) memberId.

2. Call the Get user by memberId OpenAPI using the client’s internal user id.

3. If a 404 Not found response is received, assume a webhook request with “event”: “delete”has been triggered from Channel Talk, and proceed with the webhook logic registered in Channel Talk.