> 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/during-the-meetup/supporting-roles.md).

# Supporting Roles

You might need to assign your co-organizers punctual roles at the beginning of the meetup. This looks different for every occasion, but here are some common roles:

## Hospitality <a href="#hospitality" id="hospitality"></a>

One or two people to serve coffees, pizza, beer, you name. Also clean the venue after the Meetup is over.

## Tech Support <a href="#tech-support" id="tech-support"></a>

One colleague should be in charge anything tech. From operating the beamer, recording, setting up the microphone, or even help the speakers.

## Sign Up <a href="#hospitality" id="hospitality"></a>

One or two colleagues should be available to welcome guests at the door and ask them to sign up.&#x20;

## Timer

It is hard for speakers to know how much time they have left. So having somebody in the front row, either displaying the time or discretely gesturing how much time is left is a game changer.

{% hint style="info" %}
Visual prompts like a little sign saying `5 mins left` are better than interrumpting the speaker.
{% endhint %}

## Brief the speakers

One person to briefly engage the speakers. Show them the venue, offer them a drink, and ask if they need anything (e.g. some speakers might ask for a glass of water when they present or maybe even a table to place their laptop).

{% hint style="info" %}
Pro Tip: Ask the speakers how to pronounce they name and what name they want you to use. Some people might prefer a nickname or maybe a different version of their name.&#x20;
{% endhint %}


---

# 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/during-the-meetup/supporting-roles.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.