You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatic answers should contain a button "talk to human". This will be normal HTML and the app has to render it as a button that triggers a specific message (i.e. "User wants to talk to human").
Zammad can use this text with a trigger to forward the issue to a human.
The text was updated successfully, but these errors were encountered:
Do we need other buttons as well? We should probably discuss some kind of "actions schema". Currently, the API response contains a messages attribute. We could add an available_actions attribute?
Alternatively, we could add a new attribute to our Zammad issues, which indicated that the chat bot should not answer at all. We can then add an info to the first automatic answer that the user can always request to talk/write to a human. We can have an LLM evaluate each message if the user wants that and in such a case set the "silence bot" attribute in Zammad. Zammad can then have a trigger bumping this issue to a human.
Automatic answers should contain a button "talk to human". This will be normal HTML and the app has to render it as a button that triggers a specific message (i.e. "User wants to talk to human").
Zammad can use this text with a trigger to forward the issue to a human.
The text was updated successfully, but these errors were encountered: