Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Chat End Logging] DF.app proper chat end reason logging; Failed escalations (DF.app and SF.app) #1297

Closed
ear-dev opened this issue Sep 13, 2022 · 2 comments

Comments

@ear-dev
Copy link

ear-dev commented Sep 13, 2022

This story is for system messages only. i.e. messages that the visitor does not see, but they appear in the Admin/Ui as "Conversation closed" messaging. We need to make sure all the conversation closed messaging is accurate.

DF.app:

  • visitor abandonment
  • chat closed by visitor (clicking the x)
  • SF service unavailable (dept. not configured)
  • ??

SF.app:

  • service unavailable
  • no agents available
  • ??
@AlexanderKanakis
Copy link
Collaborator

PRs:

Apps.Dialogflow: WideChat/Apps.Dialogflow#172
Apps.Salesforce.LiveAgent: WideChat/Apps.Salesforce.LiveAgent#78

@AlexanderKanakis AlexanderKanakis moved this from In progress to Under Review in Chatbot Client Replacement Sep 23, 2022
@ear-dev
Copy link
Author

ear-dev commented Oct 6, 2022

Since I have merged the DF PR, and @AlexanderKanakis is going to combine PR 78 into SF PR 75, I am going to close this story, and then we will have a single story in regard to the close chat messages in the SF repo.

@ear-dev ear-dev closed this as completed Oct 6, 2022
@ear-dev ear-dev moved this from Under Review to Done in Chatbot Client Replacement Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants