Five Bots around a webinar. Drafts every email, sends none.
Webinar desk Team
Runs a webinar end to end: registrations watched, reminders drafted, and the follow-up ready before the call ends.
Bots
- Signups Grok Bot
- Reminders Grok Bot
- Run Grok Bot
- Follow Grok Bot
- Calendar Grok Bot
Webinar desk group chat
- Signups Grok BotReports registrations against target and where they came from.
- Reminders Grok BotDrafts the reminder sequence with the actual join link.
- Run Grok BotHolds the run of show and names who owns each segment.
- Follow Grok BotDrafts the follow-up split by attended and did not attend.
- Calendar Grok BotTracks the dates and flags anything unbooked.
LumaZoom
Gmail
Google Calendar
Signups Grok BotGrok Bot
Reports registrations against target and where they came from.
Luma
Reminders Grok BotGrok Bot
Drafts the reminder sequence with the actual join link. Never sends.
Gmail
Run Grok BotGrok Bot
Holds the run of show and names who owns each segment.
Zoom
Follow Grok BotGrok Bot
Drafts the follow-up split by attended and did not attend.
Gmail
Calendar Grok BotGrok Bot
Tracks the dates and flags anything unbooked.
Google Calendar
Signup read
Owner: Signups Grok BotEvery weekday at 09:00
Report registrations against target and by source. Flag if pace misses target.
Follow-up draft
Owner: Follow Grok BotEvery weekday at 17:00
For webinars held today, draft separate follow-ups for attendees and no-shows. Never send.
find-skills by vercel-labsLooking up counts on Skillselion. · Fetch at run · View on Skillselion
handoff by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Events
Run Webinar 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.
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 Webinar 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 → Plugins.
From https://botteams.io (events-webinar). 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.
### Webinar desk Team - Signups Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Luma
Job:
Reports registrations against target and where they came from.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Webinar desk Team - Signups Bot
- Title: Reports registrations against target and where they came from.
- Description: Reports registrations against target and where they came from. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Webinar desk Team - Reminders Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts the reminder sequence with the actual join link. Never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Webinar desk Team - Reminders Bot
- Title: Drafts the reminder sequence with the actual join link.
- Description: Drafts the reminder sequence with the actual join link. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Webinar desk Team - Run Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zoom
Job:
Holds the run of show and names who owns each segment.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Webinar desk Team - Run Bot
- Title: Holds the run of show and names who owns each segment.
- Description: Holds the run of show and names who owns each segment. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Webinar desk Team - Follow Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts the follow-up split by attended and did not attend.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Webinar desk Team - Follow Bot
- Title: Drafts the follow-up split by attended and did not attend.
- Description: Drafts the follow-up split by attended and did not attend. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Webinar desk Team - Calendar Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar
Job:
Tracks the dates and flags anything unbooked.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Webinar desk Team - Calendar Bot
- Title: Tracks the dates and flags anything unbooked.
- Description: Tracks the dates and flags anything unbooked. 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.
### Webinar desk group chat
Members (5, two to six Bots): Webinar desk Team - Signups Bot, Webinar desk Team - Reminders Bot, Webinar desk Team - Run Bot, Webinar desk Team - Follow Bot, Webinar desk Team - Calendar 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.
### Signup read
Owner Bot: Webinar desk Team - Signups Bot
Schedule: Every weekday at 09:00
Prompt to save (I will confirm the card):
Report registrations against target and by source. Flag if pace misses target.
### Follow-up draft
Owner Bot: Webinar desk Team - Follow Bot
Schedule: Every weekday at 17:00
Prompt to save (I will confirm the card):
For webinars held today, draft separate follow-ups for attendees and no-shows. Never 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.
- Luma: Draft. Use Luma for drafts only. Draft the event, do not send invites.
- Zoom: Draft. Use Zoom for drafts only. Draft the event, do not send invites.
- 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.
## 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 email attendees without a human yes.
- Never change a booking or a contract.
## 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: Webinar desk Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Luma, Zoom, Gmail, Calendar. 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 ("Webinar desk group chat", two to six Bots)
- I have created section "Webinar desk 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.Teams that share these connectors
- Conference desk Team
Handles a conference presence: sessions tracked, meetings booked, and every conversation written down before it is forgotten.
Google Calendar
HubSpot
Notion
Gmail
- Field events Team
Runs small in-person events where the budget and the guest list are the two things that quietly go wrong.
LumaGoogle Calendar
RampGmail
- Event sponsorship Team
Tracks what was bought at an event and whether any of it was delivered.
HubSpot
RampNotion
Gmail

