botteams.ai

Escalation path team

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

Verified4 Bots· 2 routinesBounce checkEvery weekday at 11:00 · Escalate · SpotList tickets reassigned more than twice without resolution.Context briefEvery weekday at 11:30 · Escalate · ContextFor escalated tickets, assemble the history into one summary.Watch this team

Escalation path team

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

Bots

  • Spot Grok Bot
  • Context Grok Bot
  • Engineering Grok Bot
  • Update Grok Bot
Group chat

Escalation desk group chat

  • Spot Grok Bot
  • Context Grok Bot
  • Engineering Grok Bot
  • Update Grok Bot
Connectors
  • Zendesk
  • Linear
  • Intercom
  • Gmail
Job
  • Spot Grok BotGrok Bot

    Names tickets that have bounced between people without progress.

    • Zendesk
  • Context Grok BotGrok Bot

    Assembles the history so the next person does not start from nothing.

    • Intercom
  • Engineering Grok BotGrok Bot

    Drafts the Linear issue when a ticket is really a bug.

    • Linear
  • Update Grok BotGrok Bot

    Drafts the holding update for the customer. Never sends it.

    • Gmail
Routines2
  • Bounce check

    Owner: Spot Grok BotEvery weekday at 11:00

    List tickets reassigned more than twice without resolution.

  • Context brief

    Owner: Context Grok BotEvery weekday at 11:30

    For escalated tickets, assemble the history into one summary.

Skills3
Notes

Sidebar section

Helpdesk

Four Bots on escalations. Assembles context, contacts nobody.

Run Escalation path 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 Escalation path 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-escalation). 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.

### Escalation path · Spot Grok Bot
(Named "Escalate · Spot" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zendesk

Job:
Names tickets that have bounced between people without progress.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Escalation path · Spot Grok Bot
- Title: Names tickets that have bounced between people without progress.
- Description: Names tickets that have bounced between people without progress. 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.

### Escalation path · Context Grok Bot
(Named "Escalate · Context" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Intercom

Job:
Assembles the history so the next person does not start from nothing.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Escalation path · Context Grok Bot
- Title: Assembles the history so the next person does not start from nothing.
- Description: Assembles the history so the next person does not start from nothing. 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.

### Escalation path · Engineering Grok Bot
(Named "Escalate · Engineering" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear

Job:
Drafts the Linear issue when a ticket is really a bug.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Escalation path · Engineering Grok Bot
- Title: Drafts the Linear issue when a ticket is really a bug.
- Description: Drafts the Linear issue when a ticket is really a bug. 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.

### Escalation path · Update Grok Bot
(Named "Escalate · Update" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Drafts the holding update for the customer. Never sends it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Escalation path · Update Grok Bot
- Title: Drafts the holding update for the customer.
- Description: Drafts the holding update for the customer. 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.

## 2. Create this group chat

Open a group chat with two to six of the Bots above. Do not add more than six.

### Escalation desk group chat
Members (4, two to six Bots): Escalation path · Spot Grok Bot, Escalation path · Context Grok Bot, Escalation path · Engineering Grok Bot, Escalation path · Update 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.

### Bounce check
Owner Bot: Escalation path · Spot Grok Bot
Schedule: Every weekday at 11:00

Prompt to save (I will confirm the card):
List tickets reassigned more than twice without resolution.

### Context brief
Owner Bot: Escalation path · Context Grok Bot
Schedule: Every weekday at 11:30

Prompt to save (I will confirm the card):
For escalated tickets, assemble the history into one summary.

## 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.
- Linear: Draft. Use Linear for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- 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.
- Gmail: Draft. Use Gmail 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 Linear, Gmail. 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 Escalate · Spot (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 ("Escalation desk 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

  • 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
  • Support voice

    Keeps support replies consistent and human, and catches the ones that read like a form letter.

    • Zendesk
    • Intercom
    • Notion