> ## Documentation Index
> Fetch the complete documentation index at: https://heybtw.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Your first session

> What to ask Claude first, what heyBTW answers, and where to go from there.

Once heyBTW is [connected](https://heybtw.com/docs/mcp/connect.md), you work in plain language. Claude picks the tools. This page shows a good first session, in order, with the tool behind each answer so you know what you are looking at.

## 1. Orient

> "What can you see in heyBTW?"

Claude calls [`get_workspace_overview`](https://heybtw.com/docs/tools/get-workspace-overview). You learn your workspace, whether a CRM is connected inside heyBTW (`crm_context`), which event platforms sync (`configuration.integrations.event_platforms`), how many events and sign-ups heyBTW holds, and whether you have saved a target spec (who your rooms are for).

If the answer says no event platform is connected and you run events on Luma, Splash or Zuddl, connect it in the dashboard first: the overview gives you the exact link. It is the one setup step that keeps guest lists and check-ins current on their own.

## 2. See your events

> "List my events."

[`list_events`](https://heybtw.com/docs/tools/list-events) returns each event with its `channel_id`, start date, `event_tense` (upcoming, live, past) and how many people signed up. Every other tool takes either the event name or its `channel_id`.

## 3. Put an event in, if heyBTW has none

> "Set up our SF dinner on the 19th at 6pm Pacific, for 12 revenue leaders."

[`create_collab`](https://heybtw.com/docs/tools/create-collab) creates the event (heyBTW calls it a collab). Or paste the event's public Luma or Partiful link and Claude creates it from the page. Then bring the guest list in:

> "Here's the guest export from Partiful." (attach the file)

[`record_signups`](https://heybtw.com/docs/tools/record-signups) previews the file first: which columns map where, who counts as registered, declined or attended, and which rows were skipped. Nothing is saved until you confirm. See [Record who registered and who came](https://heybtw.com/docs/playbooks/record-who-came.md).

## 4. Ask about one event

> "How did the Austin dinner go? Who came?"

[`get_event_details`](https://heybtw.com/docs/tools/get-event-details) leads with three counts: registered, declined, attended. Only checked-in people count as attended. For an upcoming event you also get where it stands against its RSVP goal and how many days are left.

## 5. Ask what to do next

Pick the play that fits where your next event is on the calendar:

| Where you are | Say | Playbook |
| - | - | - |
| Two weeks out | "Who should we invite to the SF dinner, and who on the team knows them?" | [Fill the room](https://heybtw.com/docs/playbooks/invite-sprint.md) |
| The day after | "Let's debrief the Austin dinner." | [The morning after](https://heybtw.com/docs/playbooks/morning-after.md) |
| A week after | "Did sales follow up with the Austin attendees? What did it do for pipeline?" | [Follow-up and ROI](https://heybtw.com/docs/playbooks/follow-up-and-roi.md) |

heyBTW also serves workflow prompts for these moments: `invite_sprint`, `debrief`, `follow_through` and `record_roster`. Your client lists them with the connector. See [Prompts and resources](https://heybtw.com/docs/mcp/prompts-and-resources.md).

## 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](https://heybtw.com/docs/mcp/responses.md) explains the shape, and [the rules](https://heybtw.com/docs/mcp/rules.md) explain why.

> [!NOTE]
>
> 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. On the heyBTW demo workspace, for example, every read notes that some partner events are restricted by the host's Sponsor Mode.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.