Customer success Team

• find-skills by vercel-labs

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• handoff by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

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 Customer success 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 → Plugins.

From https://botteams.io (customer-success). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly. After create, set Name, Title, and Description on the profile.
A Bot is persistent and named. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Customer success Team - Health Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Stripe, HubSpot

Job:
Watches account health signals and failed Stripe charges that affect a customer. Alerts only. Does not refund. No site ops.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer success Team - Health Bot
- Title: Watches account health signals and failed Stripe charges that affect a customer.
- Description: Watches account health signals and failed Stripe charges that affect a customer. Alerts only. Does not refund. No site ops. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Customer success Team - Inbox Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail, Zendesk

Job:
Triages customer-success mail. Sorts. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer success Team - Inbox Bot
- Title: Triages customer-success mail.
- Description: Triages customer-success mail. Sorts. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Customer success Team - Renewals Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar, HubSpot

Job:
Tracks upcoming renewals on Calendar. Drafts renewal notes. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer success Team - Renewals Bot
- Title: Tracks upcoming renewals on Calendar.
- Description: Tracks upcoming renewals on Calendar. Drafts renewal notes. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Customer success Team - QBR Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar, Gong

Job:
Drafts QBR notes from Calendar.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer success Team - QBR Bot
- Title: Drafts QBR notes from Calendar.
- Description: Drafts QBR notes from Calendar. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Customer success Team - Follow-ups Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Drafts follow-ups for open success threads. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer success Team - Follow-ups Bot
- Title: Drafts follow-ups for open success threads.
- Description: Drafts follow-ups for open success threads. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Customer success Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Writes the success recap. Health alerts, renewals, drafts waiting on a human.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer success Team - Recap Bot
- Title: Writes the success recap.
- Description: Writes the success recap. Health alerts, renewals, drafts waiting on a human. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

## 2. Create this group chat

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

### Success desk group chat
Members (6, two to six Bots): Customer success Team - Health Bot, Customer success Team - Inbox Bot, Customer success Team - Renewals Bot, Customer success Team - QBR Bot, Customer success Team - Follow-ups Bot, Customer success Team - Recap Bot

## 3. 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.

### Health notes
Owner Bot: Customer success Team - Health Bot
Schedule: Every Friday at 11:00

Prompt to save (I will confirm the card):
Report health alerts and failed charges that affect customers. Do not refund. No site ops.

### Renewal drafts
Owner Bot: Customer success Team - Renewals Bot
Schedule: Every Friday at 15:00

Prompt to save (I will confirm the card):
Draft notes for renewals in the next 14 days. Never send.

### Success recap
Owner Bot: Customer success Team - Recap Bot
Schedule: Every weekday at 16:30

Prompt to save (I will confirm the card):
Recap health, renewals, and drafts waiting on a human send.

## 4. 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 → 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.

- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- Stripe: Read. Use Stripe read-only. Never move funds.
- Zendesk: Ask before send. Use Zendesk only after a human says yes in the chat. Say the post, wait for a yes.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. Say the post, wait for a yes.
- Gong: Draft. Use Gong read-only.

## 5. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Reference a skill with /.
If a skill is already installed on the account (Settings → Plugins → Yours), use it. Enable it for this Bot if / does not show it.
If it is not installed, fetch or load it through the Skillselion connector using the skill id. Do not install a second copy.
Connect the Skillselion connector only when a fetch is needed. Do not start OAuth from this prompt.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Skill id: `skill:vercel-labs/skills#find-skills`.
Scope: every Bot on this team (team scope).

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Skill id: `skill:mattpocock/skills#handoff`.
Scope: every Bot on this team (team scope).


## 6. Also

Standing instructions for every Bot on this team:

- Never send to a customer without a human yes.
- Never promise a date engineering has not agreed.

## Human steps

These are yours. The Bot cannot do them.

- Set each Bot avatar (Bot actions → Edit Profile). Attach an image if you want a custom one.
- Create a sidebar section named exactly: Customer success Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Gmail, Calendar, Stripe, Gong. That switch is account-wide and it is the only one that actually stops a write.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".

## Done when

- Named Bots exist
- Named group chat exists ("Success desk group chat", two to six Bots)
- I have created section "Customer success Team"
- 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.