botteams.ai

Response times team

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

Verified4 Bots· 2 routinesApproaching breachEvery hour during working hours · SLA · ClockName tickets within one hour of their promised response time. Never reply for anyone.Weekly recapEvery Monday at 09:00 · SLA · RecapReport last week's response times by plan. Show the worst day, not the average.Watch this team

Response times team

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

Bots

  • Clock Grok Bot
  • Breached Grok Bot
  • Load Grok Bot
  • Recap Grok Bot
Group chat

Response desk group chat

  • Clock Grok Bot
  • Breached Grok Bot
  • Load Grok Bot
  • Recap Grok Bot
Connectors
  • Zendesk
  • Intercom
  • Plain
  • Gmail
Job
  • Clock Grok BotGrok Bot

    Names tickets approaching their promised response time.

    • Zendesk
  • Breached Grok BotGrok Bot

    Reports what was missed, by how long, and on which plan.

    • Zendesk
    • Plain
  • Load Grok BotGrok Bot

    Shows queue volume against people available.

    • Intercom
  • Recap Grok BotGrok Bot

    Writes the weekly response-time recap without smoothing the bad days.

    • Gmail
Routines2
  • Approaching breach

    Owner: Clock Grok BotEvery hour during working hours

    Name tickets within one hour of their promised response time. Never reply for anyone.

  • Weekly recap

    Owner: Recap Grok BotEvery Monday at 09:00

    Report last week's response times by plan. Show the worst day, not the average.

Skills3
Notes

Sidebar section

Helpdesk

Four Bots on promised response times. Warns early, replies never.

Run Response times 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 Response times 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-sla). 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.

### Response times · Clock Grok Bot
(Named "SLA · Clock" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zendesk

Job:
Names tickets approaching their promised response time.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Response times · Clock Grok Bot
- Title: Names tickets approaching their promised response time.
- Description: Names tickets approaching their promised response time. 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.

### Response times · Breached Grok Bot
(Named "SLA · Breached" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zendesk, Plain

Job:
Reports what was missed, by how long, and on which plan.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Response times · Breached Grok Bot
- Title: Reports what was missed, by how long, and on which plan.
- Description: Reports what was missed, by how long, and on which plan. 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.

### Response times · Load Grok Bot
(Named "SLA · Load" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Intercom

Job:
Shows queue volume against people available.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Response times · Load Grok Bot
- Title: Shows queue volume against people available.
- Description: Shows queue volume against people available. 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.

### Response times · Recap Grok Bot
(Named "SLA · Recap" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Writes the weekly response-time recap without smoothing the bad days.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Response times · Recap Grok Bot
- Title: Writes the weekly response-time recap without smoothing the bad days.
- Description: Writes the weekly response-time recap without smoothing the bad days. 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.

### Response desk group chat
Members (4, two to six Bots): Response times · Clock Grok Bot, Response times · Breached Grok Bot, Response times · Load Grok Bot, Response times · 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.

### Approaching breach
Owner Bot: Response times · Clock Grok Bot
Schedule: Every hour during working hours

Prompt to save (I will confirm the card):
Name tickets within one hour of their promised response time. Never reply for anyone.

### Weekly recap
Owner Bot: Response times · Recap Grok Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Report last week's response times by plan. Show the worst day, not the average.

## 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.
- 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 Plain, 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 SLA · Load (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 ("Response 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

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

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

    • Zendesk
    • Intercom
    • Notion