Four Bots around demos. Records promises, makes none.
Demo desk team
Prepares demos against the prospect's actual problem, and records what was promised in the room.
Demo desk team
Prepares demos against the prospect's actual problem, and records what was promised in the room.
Bots
- Prep Grok Bot
- Plan Grok Bot
- Promises Grok Bot
- Follow Grok Bot
Demo desk group chat
- Prep Grok Bot
- Plan Grok Bot
- Promises Grok Bot
- Follow Grok Bot
HubSpot
Google Calendar
GongNotion
Job
Prep Grok BotGrok Bot
Assembles what is known about the account before the call.
HubSpot
Plan Grok BotGrok Bot
Drafts the demo plan around their stated problem, not the standard tour.
Notion
Promises Grok BotGrok Bot
Pulls commitments made during the call from the recording.
Gong
Follow Grok BotGrok Bot
Drafts the follow-up covering exactly what was promised. Never sends.
Google Calendar
Routines2
Prep brief
For today's demos, assemble what is known and what to ask.
Promise pull
From today's calls, list every commitment made to a prospect and who owns it.
Skills2
find-skills by vercel-labs… · Fetch at run · View on Skillselion
handoff by mattpocock… · Fetch at run · View on Skillselion
Notes
Sidebar section
Sales
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 Demo 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 (sales-demos). 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.
### Demo desk · Prep Grok Bot
(Named "Demo · Prep" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot
Job:
Assembles what is known about the account before the call.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk · Prep Grok Bot
- Title: Assembles what is known about the account before the call.
- Description: Assembles what is known about the account before the call. 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.
### Demo desk · Plan Grok Bot
(Named "Demo · Plan" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Drafts the demo plan around their stated problem, not the standard tour.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk · Plan Grok Bot
- Title: Drafts the demo plan around their stated problem, not the standard tour.
- Description: Drafts the demo plan around their stated problem, not the standard tour. 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.
### Demo desk · Promises Grok Bot
(Named "Demo · Promises" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gong
Job:
Pulls commitments made during the call from the recording.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk · Promises Grok Bot
- Title: Pulls commitments made during the call from the recording.
- Description: Pulls commitments made during the call from the recording. 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.
### Demo desk · Follow Grok Bot
(Named "Demo · Follow" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar
Job:
Drafts the follow-up covering exactly what was promised. Never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk · Follow Grok Bot
- Title: Drafts the follow-up covering exactly what was promised.
- Description: Drafts the follow-up covering exactly what was promised. Never sends. 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.
### Demo desk group chat
Members (4, two to six Bots): Demo desk · Prep Grok Bot, Demo desk · Plan Grok Bot, Demo desk · Promises Grok Bot, Demo desk · Follow 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: Sales.
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.
### Prep brief
Owner Bot: Demo desk · Prep Grok Bot
Schedule: Every weekday at 08:00
Prompt to save (I will confirm the card):
For today's demos, assemble what is known and what to ask.
### Promise pull
Owner Bot: Demo desk · Promises Grok Bot
Schedule: Every weekday at 17:00
Prompt to save (I will confirm the card):
From today's calls, list every commitment made to a prospect and who owns it.
## 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.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Gong: Draft. Use Gong for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- 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 Calendar, Gong, 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.
## 7. Also
Standing instructions for every Bot on this team:
- Never email a prospect. Draft only.
- Never discount without a human yes.
## Done when
- Named Bots exist
- Named group chat exists ("Demo desk group chat", two to six Bots)
- I have created section "Sales"
- 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
- Outbound desk
Runs outbound where the research is real and the sequence stops the moment someone answers.
Apollo.ioGmail
HubSpot
LinkedIn
- Proposal desk
Keeps proposals accurate and consistent, and stops silence being mistaken for consideration.
Salesforce
DocusignNotion
Gmail
- Territory planning
Splits accounts so coverage is even and no account sits unowned for a quarter.
Salesforce
HubSpot
Notion
Google Cloud BigQuery



