Four Bots on whether answers were right. Coaches privately.
Support quality team
Reviews resolved tickets for whether the answer was actually right, not merely fast.
Support quality team
Reviews resolved tickets for whether the answer was actually right, not merely fast.
Bots
- Sample Grok Bot
- Correct Grok Bot
- Reopened Grok Bot
- Coach Grok Bot
Quality desk group chat
- Sample Grok Bot
- Correct Grok Bot
- Reopened Grok Bot
- Coach Grok Bot
Zendesk
Intercom
Notion
Job
Sample Grok BotGrok Bot
Samples resolved tickets across people and topics.
Zendesk
Correct Grok BotGrok Bot
Checks the answer given was actually correct.
Notion
Reopened Grok BotGrok Bot
Reports tickets reopened after being marked solved.
Intercom
Coach Grok BotGrok Bot
Drafts private coaching notes with the specific ticket attached.
Routines2
Sample review
Sample fifteen resolved tickets across people and topics.
Reopen report
Report tickets reopened after being solved, with the reason.
Skills3
find-skills by vercel-labs… · Fetch at run · View on Skillselion
handoff by mattpocock… · Fetch at run · View on Skillselion
triage by mattpocock… · Fetch at run · View on Skillselion
Notes
Sidebar section
Support
Prompt Installer for Grok Bot
Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.
# Grok Bot Teams installer
Set up a team for me called Support quality team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings, then Plugins.
From https://botteams.ai (support-quality). Source: https://github.com/ellelion/botteams.
## 1. Create these Bots
Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.
### Support quality · Sample Grok Bot
(Named "Quality · Sample" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zendesk
Job:
Samples resolved tickets across people and topics.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Support quality · Sample Grok Bot
- Title: Samples resolved tickets across people and topics.
- Description: Samples resolved tickets across people and topics. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Support quality · Correct Grok Bot
(Named "Quality · Correct" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Checks the answer given was actually correct.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Support quality · Correct Grok Bot
- Title: Checks the answer given was actually correct.
- Description: Checks the answer given was actually correct. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Support quality · Reopened Grok Bot
(Named "Quality · Reopened" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Intercom
Job:
Reports tickets reopened after being marked solved.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Support quality · Reopened Grok Bot
- Title: Reports tickets reopened after being marked solved.
- Description: Reports tickets reopened after being marked solved. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Support quality · Coach Grok Bot
(Named "Quality · Coach" in the published recipe.)
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.
Job:
Drafts private coaching notes with the specific ticket attached.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Support quality · Coach Grok Bot
- Title: Drafts private coaching notes with the specific ticket attached.
- Description: Drafts private coaching notes with the specific ticket attached. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
## 2. Create this group chat
Open a group chat with two to six of the Bots above. Do not add more than six.
### Quality desk group chat
Members (4, two to six Bots): Support quality · Sample Grok Bot, Support quality · Correct Grok Bot, Support quality · Reopened Grok Bot, Support quality · Coach Grok Bot
## 3. Sidebar section
You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Support.
Ask me to move the group chat and Bots into it.
## 4. Routines (confirm card required)
Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.
### Sample review
Owner Bot: Support quality · Sample Grok Bot
Schedule: Every weekday at 15:00
Prompt to save (I will confirm the card):
Sample fifteen resolved tickets across people and topics.
### Reopen report
Owner Bot: Support quality · Reopened Grok Bot
Schedule: Every Monday at 09:00
Prompt to save (I will confirm the card):
Report tickets reopened after being solved, with the reason.
## 5. Connectors and how far they go
Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings, then Plugins, first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.
- Zendesk: Ask before send. Use Zendesk only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
- Intercom: Ask before send. Use Intercom only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Notion. That switch is account-wide and it is the only one that actually stops a write.
## 6. Skills
Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).
Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.
### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.
### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.
### triage
https://skillselion.com/skills/mattpocock/skills/triage
Creator: mattpocock
Scope: only Quality · Sample (enable under Plugins → Yours for that Bot only).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#triage`. Connect Skillselion in Settings → Plugins first.
## 7. Also
Standing instructions for every Bot on this team:
- Never send a reply without a human yes.
- Never promise a refund.
## Done when
- Named Bots exist
- Named group chat exists ("Quality desk group chat", two to six Bots)
- I have created section "Support"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected
Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.Teams that share these connectors
- Support docs
Turns the questions support answers repeatedly into documentation that stops them.
Zendesk
Notion
Intercom
Glean
- Support during incidents
Handles the support side of an outage: one accurate message, updated, instead of forty different answers.
Zendesk
Intercom
PagerDuty
Notion
- Proactive support
Contacts nobody, but finds the customers about to have a problem so a human can reach them first.
Mixpanel
Zendesk
HubSpot
Gmail



