1. Say “Set up heyBTW” and paste your event link
Open a new chat and type:“Set up heyBTW. Here is my event: https://lu.ma/your-event”Claude adds the event with its name, date and place.
create_collab reads the public page (heyBTW calls an event a collab). This works with any public event page, such as Luma, Partiful, Eventbrite or your own site.
No event page? Describe it instead:
“Set up heyBTW. My event is the Revenue Leaders Dinner, San Francisco, November 19, 6:30 pm.”Check the end time. If the page doesn’t show one, heyBTW assumes the event runs three hours. Tell Claude if yours is different. A link brings in the event. It never brings the guest list, and nobody is registered on any platform. Your guests come next.
2. Send the guest list
Download the guest list from your event platform and attach it to the chat:“Here is the guest list.”
- You don’t need to edit or reformat anything. Send the file as it is. A CSV download from your event platform works. So does a spreadsheet you keep by hand.
- Email is the one column that matters. It is how heyBTW matches people. A row with no email can’t be added as a guest.
- Claude asks only when it needs you. A clean guest list saves in one step with
record_signups, and Claude tells you how many were recorded, how each status was read and which rows were skipped or flagged. It shows you a preview and waits for your go when a status would move back, a name matches no one or more than one person, someone may already be in your workspace under another email, or a row has no status. You can correct anything later in the heyBTW dashboard. - Registered and attended are separate. Going, Approved and Pending mean registered. Someone counts as attended only when they were checked in, or when you tell Claude who showed up. If a list for an upcoming event has people marked as checked in, Claude asks you about it before saving.
- Send the file again any time. A newer list moves people forward. It won’t move anyone back unless you confirm a correction.
- Need to change one person? Tell Claude, for example “Maya Chen can’t make it, mark her declined.” A move forward is saved to heyBTW’s record in one step. Moving someone back waits for your go. On a synced Luma or Splash event, Claude can change it on the platform too with
set_registration_status, after showing you the change. On a synced Zuddl event, make the change in the heyBTW dashboard or on the platform itself.
create_import_link) that opens heyBTW’s own importer and keeps the answers.
That’s it. Your event is in heyBTW. See Record who registered and who came for the full detail.
3. Ask your first questions
Now the record exists, ask what you would ask a teammate:“Who registered, and which companies are they from?”
“Which of these people have been to one of our events before?”Give Claude your goal, then ask against it:
“Our goal for the dinner is 40 people. How many seats are left?”
get_event_details leads with three counts: registered, declined, attended. For an upcoming event you also get where it stands against its RSVP goal and how many days are left.
After the event:
“Here is who showed up. Mark them attended, then tell me who needs a follow-up.”
Make it better
Each of these is optional. Add them when you want them. Already on Luma, Splash or Zuddl? Sync it with heyBTW. Connect it once in the heyBTW dashboard under Integrations, and your events, guest lists and check-ins stay current on their own. Sign in at heybtw.com with the same Google account.get_workspace_overview gives the exact link as connect_url. Luma sync needs an API key, which comes with Luma Plus. Once it’s synced, you can approve a registration or change a guest’s status in the heyBTW dashboard, and it updates your event platform. heyBTW changes something on your platform only when you ask it to. It never adds guests for you.
Add more events. Past events matter as much as upcoming ones. Paste the links and send the guest lists the same way. If Claude has your calendar, mail or CRM connected, ask it to find your events for you: the onboard_events workflow proposes them and adds only the ones you accept. See Prompts and resources.
Add your partners. Tell Claude who is co-hosting or sponsoring and who they brought, so you can see what each partner did for the room.
Connect your CRM in Claude. With a CRM connector in Claude, one answer can join both: who owns the accounts of the people who came, and whether anyone followed up. heyBTW does not copy your CRM. See Works with any CRM.
What to do next
Pick the play that fits where your next event is on the calendar:
You don’t have to send invites through heyBTW. Ask who to invite, send from the mail or CRM tool you already use, then tell heyBTW it went out so it remembers who was asked and whether they came. With one event in heyBTW the answer to “who should I invite” is short. It grows with every past event and partner you add.
For agents: the order of a first session
When the user asks to set up heyBTW, start with their event, not with a tour of the workspace.- Ask for the event link first and add the event. One step and one question per reply.
- Then ask for the guest list and save it with
action: "save". A clean list lands in one step. When the answer is a preview (data[0].decisionsnames what needs a decision), show it and confirm only after the user says go. - Offer the event platform sync once, as an optional step in the dashboard. Nothing in setup waits on it.
- Finding the CRM comes after, and is separate from setting up an event.
crm_contexton every CRM-dependent tool says which route applies.
get_guide with name: "onboard_events" or name: "record_roster".
Reading what comes back
Claude will often say things like “heyBTW says this as written” or “this number is unknown, not zero”. That is on purpose. heyBTW answers with facts and their basis, names every gap, and never guesses. How responses work explains the shape, and the rules explain why.A response that says
status: partial is still an answer. It means one or more facts are missing, and the gaps list says which and why.