> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/other/archived-pages/archive-social-and-community-events-guide/archive-event-role-checklists/archive-greeter.md). # \[ARCHIVE] Greeter As the greeter, you are responsible for greeting community members as they arrive at the event so they feel welcomed and comfortable. ## **Greeter Checklist** * [ ] **Welcome community members** as they come through the door * [ ] Stand by the door towards the beginning of the event * [ ] As the event goes on, try to notice new people that arrive and introduce yourself * [ ] **Have name tags and Sharpies** ready by the door for people to put on as they enter (the organizer will provide these). Name tags make the event more accessible to newer people, and help create an environment of belonging even for those who don’t know anyone * [ ] Ask people to fill them out & put them on as they enter * [ ] **Give extra time and attention to people who are new to the community** to help them feel welcome and comfortable * [ ] If this is their first campaign social event, spend some extra time connecting with them * [ ] Introduce them to another community member you think they might connect with * [ ] **Be vigilant throughout the event:** if you see any attendees who are alone or having a hard time connecting with others, talk to them and introduce them to others * [ ] **Remind people to take photos at the event!** Kick things off by taking a few yourself --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://handbook.proanimal.org/other/archived-pages/archive-social-and-community-events-guide/archive-event-role-checklists/archive-greeter.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.