chat-core-zendesk: workaround to inject ticket id to bot message #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is part of a workaround in order enable the bot message to include the ticket ID when live messaging session has ended.
Zendesk does not have native support to easily access ticket ID within Sunco system and Zendesk system also cannot easily access Sunco conversation ID. So the workaround is as follow:
This PR implements the first step of the workaround. Additionally, the closing message on CSAT message type is removed as it should be now handled by the bot webhook in the switchboard as well.
Thread context: https://yext.slack.com/archives/C01CSDL5US0/p1733870484402519
J=CLIP-1649
TEST=manual&auto
added unit tests
setup trigger and webhook in the zendesk sandbox account and spin up local test site. Verified that the created ticket for the live messaging session contains the conversation ID in the custom field