An event RSVP Bot that answers 'is X coming?' in Slack

How this helps you

You stop being the only person who can see the guest list, and your team gets answers without waiting for you.

✦ Try it

Every weekday at [time], check registrations for [event] in [event platform]. Post in #[channel] who is attending, one person per line, grouped by account, and tag each account owner from [owner list]. When someone in #[channel] asks whether a person has registered, reply in the thread with their status, company and title, and start the reply with 'Automated by Grok Bot'. Don't approve or decline anyone until I give you a rule.

Fill in: [time] is when the daily post goes out. [event] and [event platform] are the event and where it lives, such as Luma. [channel] is the Slack channel. [owner list] is a doc or sheet mapping accounts to people.

What they did

In the official Grok Bot for Marketing webinar, Jenna from SpaceXAI's field growth team explains a problem with Luma: only she could see who had registered, so account executives kept asking her. Her Green Light Bot reads the registrations and, every day at a set time, posts in Slack who is coming for each account and tags each account executive. When someone asks in the channel whether a person has registered, it replies with their status, company and title. During the session she added a rule to approve registrants with a VP or higher title. She also had it say its replies are automated by Grok Bot, because teammates didn't realise the Bot had answered for her. To show it live she had it check every two minutes; that was for the demo.

Who it's for: Event marketers, community managers, and anyone who keeps getting asked who's coming.

Before you start

Your event platform reachable by the Bot. Jenna signs in once on the Bot's computer and it remembers the login.
Slack connected, and a channel for the event.
A list of accounts and who owns each one.

How to try it

Take over the Bot's computer and sign in to your event platform yourself.
Tell the Bot which event and Slack channel it covers, and give it the account owner list.
Paste the prompt below.
Check the first daily post. Ask it to list people one by one, grouped the way your team thinks (Jenna groups by account tier).
Ask a test question in the channel and check the reply is labelled as automated.
Only after several days of correct posts, add an approval rule, such as approving VP and above. Keep everyone else for you to decide.

What to expect

A daily post listing VP and above registrants for each account with the owner tagged, and a threaded reply such as: yes, she's registered, here's her company and title, status pending.

Common mistakes

Leaving a two minute check running after testing. That burns usage; once a day plus answering questions is usually enough.
Letting it approve everyone. Start with no approvals, then a narrow rule.
Unlabelled replies, so people think you answered.
One long paragraph instead of one person per line.

Related tips

Let a team Bot answer requests in Slack: Install a team Bot in Slack so colleagues tag it directly, and give it a routine to catch missed tags.
Make routines cheaper: events, slow schedules, change checks: A 5-minute routine wakes 8,640 times a month. Use an event trigger, the slowest schedule that works, and a cheap change check.
Put quiet hours inside the routine itself: Have the routine re-check the clock right before it acts, and skip itself if it's too late.