support bot: escalate to team when Grok's reply contains /team#6968
Merged
Conversation
Detect the substring /team anywhere in Grok's AI reply (per-message and the initial post-join reply) and run the same escalation as a customer /team: invite the team members and switch the conversation to TEAM-PENDING. The reply itself is still posted to the chat.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Grok answers customer questions in the support bot, but until now it had no way to hand a conversation to a human — the customer had to notice and type
/teamthemselves. This change lets Grok escalate by simply including/teamanywhere in its reply (per-message replies and its initial post-join reply): the bot then runs the exact same escalation as a customer/team— invites the team members and switches the conversation to TEAM-PENDING — while still posting Grok's reply. Detection is on Grok's generated text only, so the/teammention in the API-error fallback message can't trigger a false escalation.