> For the complete documentation index, see [llms.txt](https://jmperafan.gitbook.io/meetups/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jmperafan.gitbook.io/meetups/the-week-before/talk-to-your-attendees.md).

# Talk to your attendees

## More aggressive marketing <a href="#more-aggressive-marketing" id="more-aggressive-marketing"></a>

Most people decide to join a meetup relatively last-minute. Not only that, but people who sign up last minute are more likely to show up. So you really don’t want to miss out the opportunity to advertise your meetup on the last week.

Ask marketing to make a poster/banner for you with the names of the speakers

## Reach out to RSVPs <a href="#reach-out-to-rsvps" id="reach-out-to-rsvps"></a>

Reach out to everybody. Some of them might have forgotten they signed up for a meetup. Also kindly ask to cancel if they can’t make it. That way, you can actually give a chance to somebody in the waitlist. Here is an example I have used in the past:

> Fellow {{ name }},\
> \
> It is an honor to announce that our next meeting will take place in {{ X }] days. Here are some practicalities.\
> \
> **What if you can't come anymore?** Update your attendance. We have a waiting list and somebody might appreciate the opportunity to come.\
> \
> **Where?** We meet at {{ name\_of\_venue }} ({{ address }}). It is walking distance from the {{ point\_of\_reference }}.\
> \
> **When?** Doors open at {{ opening\_at }} for those who want to network and have a drink. But we start with the program at {{ start\_at }}.\
> \
> **What?** We have a lineup of remarkable speakers:
>
> * {{ speaker\_1 }}: {{ topic\_1 }}
> * {{ speaker\_2 }}: {{ topic\_2 }}<br>
>
> Afterwards, you are welcome to have a drink with us!\
> \
> If you have any questions, feel free to message me.\
> \
> To finish, I would like to thank the sponsor for this meetup: {{ sponsor }}! {{ describe what the sponsor does }}. If you have any {{ sponsors\_expertise }} questions, make sure to speak to any of their consultants.\
> \
> See you all on {{ day\_of\_meetup}}!

## Reach out to waiting list

Cancellation rate for a meetup can range between 20% to 60%. So it is not a bad idea to reach out to the people in your waiting list. I generally mention something like:

> Some of our guests are not coming anymore and we have some tickets available. Please DM me if you want them.&#x20;

It doesn't even have to be true, but I know that anybody willing to DM for tickets has an almost 100% chance of arriving and they are maybe one of the most enthusiastic attendees. You really don't want to miss on those.

\ <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jmperafan.gitbook.io/meetups/the-week-before/talk-to-your-attendees.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
