botteams.ai

Ticket desk team

Runs a ticket desk across Zendesk and Intercom: triaged by urgency, aging conversations surfaced, and repeat tickets turned into bugs.

Verified5 Bots· 3 routinesTicket sweepEvery 2 hours during working hours · Desk · TriageSort new Zendesk tickets by urgency. Draft a first reply for the routine ones. Never send.Aging checkEvery weekday at 11:00 · Desk · ChatList Intercom conversations waiting more than four hours, oldest first. Never reply.Desk recapEvery weekday at 17:00 · Desk · RecapRecap ticket volume, aging conversations, escalations, bug drafts, and replies waiting on a human send.Watch this team

Ticket desk team

Runs a ticket desk across Zendesk and Intercom: triaged by urgency, aging conversations surfaced, and repeat tickets turned into bugs.

Bots

  • Triage Grok Bot
  • Chat Grok Bot
  • Escalation Grok Bot
  • Bugs Grok Bot
  • Recap Grok Bot
Group chat

Support desk floor group chat

  • Triage Grok Bot
  • Chat Grok Bot
  • Escalation Grok Bot
  • Bugs Grok Bot
  • Recap Grok Bot
Connectors
  • Zendesk
  • Intercom
  • Plain
  • Linear
Job
  • Triage Grok BotGrok Bot

    Sorts new Zendesk tickets by urgency and topic. Drafts a first reply, never sends it.

    • Zendesk
  • Chat Grok BotGrok Bot

    Reads Intercom conversations left waiting. Names who is waiting and for how long. Never replies.

    • Intercom
  • Escalation Grok BotGrok Bot

    Watches Plain for threads that crossed the escalation line. Drafts an internal summary, never contacts the customer.

    • Plain
  • Bugs Grok BotGrok Bot

    Turns repeated tickets into a Linear bug draft with the ticket links attached. Never files without a human.

    • Linear
  • Recap Grok BotGrok Bot

    Writes the desk recap. Volume, what is aging, what became a bug, what needs a human send.

Routines3
  • Ticket sweep

    Owner: Triage Grok BotEvery 2 hours during working hours

    Sort new Zendesk tickets by urgency. Draft a first reply for the routine ones. Never send.

  • Aging check

    Owner: Chat Grok BotEvery weekday at 11:00

    List Intercom conversations waiting more than four hours, oldest first. Never reply.

  • Desk recap

    Owner: Recap Grok BotEvery weekday at 17:00

    Recap ticket volume, aging conversations, escalations, bug drafts, and replies waiting on a human send.

Skills3
Notes

Sidebar section

Helpdesk

Example five-Bot ticket desk. Drafts every reply, sends none of them.

Run Ticket desk yourself

Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.

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 Ticket desk 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 (helpdesk). 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.

### Ticket desk · Triage Grok Bot
(Named "Desk · Triage" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zendesk

Job:
Sorts new Zendesk tickets by urgency and topic. Drafts a first reply, never sends it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Ticket desk · Triage Grok Bot
- Title: Sorts new Zendesk tickets by urgency and topic.
- Description: Sorts new Zendesk tickets by urgency and topic. Drafts a first reply, never sends it. 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.

### Ticket desk · Chat Grok Bot
(Named "Desk · Chat" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Intercom

Job:
Reads Intercom conversations left waiting. Names who is waiting and for how long. Never replies.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Ticket desk · Chat Grok Bot
- Title: Reads Intercom conversations left waiting.
- Description: Reads Intercom conversations left waiting. Names who is waiting and for how long. Never replies. 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.

### Ticket desk · Escalation Grok Bot
(Named "Desk · Escalation" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Plain

Job:
Watches Plain for threads that crossed the escalation line. Drafts an internal summary, never contacts the customer.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Ticket desk · Escalation Grok Bot
- Title: Watches Plain for threads that crossed the escalation line.
- Description: Watches Plain for threads that crossed the escalation line. Drafts an internal summary, never contacts the customer. 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.

### Ticket desk · Bugs Grok Bot
(Named "Desk · Bugs" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear

Job:
Turns repeated tickets into a Linear bug draft with the ticket links attached. Never files without a human.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Ticket desk · Bugs Grok Bot
- Title: Turns repeated tickets into a Linear bug draft with the ticket links attached.
- Description: Turns repeated tickets into a Linear bug draft with the ticket links attached. Never files without a human. 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.

### Ticket desk · Recap Grok Bot
(Named "Desk · Recap" in the published recipe.)
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Writes the desk recap. Volume, what is aging, what became a bug, what needs a human send.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Ticket desk · Recap Grok Bot
- Title: Writes the desk recap.
- Description: Writes the desk recap. Volume, what is aging, what became a bug, what needs a human send. 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.

### Support desk floor group chat
Members (5, two to six Bots): Ticket desk · Triage Grok Bot, Ticket desk · Chat Grok Bot, Ticket desk · Escalation Grok Bot, Ticket desk · Bugs Grok Bot, Ticket desk · Recap 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: Helpdesk.
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.

### Ticket sweep
Owner Bot: Ticket desk · Triage Grok Bot
Schedule: Every 2 hours during working hours

Prompt to save (I will confirm the card):
Sort new Zendesk tickets by urgency. Draft a first reply for the routine ones. Never send.

### Aging check
Owner Bot: Ticket desk · Chat Grok Bot
Schedule: Every weekday at 11:00

Prompt to save (I will confirm the card):
List Intercom conversations waiting more than four hours, oldest first. Never reply.

### Desk recap
Owner Bot: Ticket desk · Recap Grok Bot
Schedule: Every weekday at 17:00

Prompt to save (I will confirm the card):
Recap ticket volume, aging conversations, escalations, bug drafts, and replies waiting on a human send.

## 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.
- Plain: Draft. Use Plain for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Linear: Draft. Use Linear 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 Plain, Linear. 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 Desk · Triage (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 close a ticket on the customer behalf.

## Done when

- Named Bots exist
- Named group chat exists ("Support desk floor group chat", two to six Bots)
- I have created section "Helpdesk"
- 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

  • Escalation path

    Makes sure hard tickets reach the right person quickly, with the context already assembled.

    • Zendesk
    • Linear
    • Intercom
    • Gmail
  • Reply library

    Keeps canned replies accurate, because a wrong saved reply is worse than no saved reply.

    • Zendesk
    • Notion
    • Intercom
  • Response times

    Watches promised response times and warns before one is missed, not after.

    • Zendesk
    • Intercom
    • Plain
    • Gmail