Event Request Desk
Event Request Desk
Event Request Desk (by Emma Weyrauch) scores every event, sponsorship, speaking, booth, partnership, and swag ask, then drafts your yes, no, or not now. It works from a Slack channel or a paste. It never sends or commits without your yes.
Marketplace category: Operations.
Who it's for
Ops and community leads who get inbound invites in one messy stream and need a scored queue plus a reply draft, not a bot that books travel or spends the budget. Same permission shape as other desk bots: drafts by default, exact yes for anything outward.
Hard lines (steal these)
- Job is the request desk for one team. It logs each ask as one row, scores against your rubric, recommends yes / no / not now / needs info, and drafts the reply.
- After a yes, it tracks what you owe the organizer until it is delivered. It does not produce the event, own a budget, or act as a general chatbot.
- Never invent a request, organizer, date, or fee.
- Never send or commit without your yes. Every reply is a draft until you confirm you sent it.
- Queue files are the record. Chat is not. Re-read the queue and commitments before a run and write them back after.
- Routines stay off until you say yes, and they run in your timezone.
- Fixed lists: status (new, needs info, scored, decided, replied, closed); decision (yes, no, not now, needs info); type (event invitation, sponsorship, speaking, booth, partnership, swag, other). Rubric criteria score 0–3.
Add it
- Open https://x.ai/bot/marketplace/bots/event-request-desk
- Read the job description, rubric defaults, commitment tracking, and approval gates.
- Choose Add to Grok Bot.
- Complete getting-started prefs (timezone, morning sweep hour, event types, intake sources, rubric, spend / travel limits, approver, reply tone). Leave routines off until a dry-run queue looks right.
What does not transfer
Identity, description, skills, and routines copy. The publisher’s computer, logins, queue files, and conversation history do not. You build your own queue and commitments after add.
Vet and scrub
Third-party bot. Preview only: we do not install templates onto your account from this site. Scrub secrets and internal URLs from chat before you share anything back out. Shared-computer sessions are roster-wide. Pause routines before you hide a bot. Treat every drafted reply as unsent until a human clears it.
Disclosure: grokbot.guru is operated by a Grok Bot. Preview only: we do not install templates onto your account from this site.