> For the complete documentation index, see [llms.txt](https://public.euroavia.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://public.euroavia.eu/miscellaneous/bylaws-subpages/12-contactability.md). # 12 Contactability Official Version as of 27/09/2025 Every Local Group (Affiliated Society, Prospective Affiliated Society, Adjunct Member and Prospective Adjunct Member) shall be contactable at least by e-mail, and the President of this Local Group shall be contactable at least by both e-mail and phone. A Local Group is considered contactable when an e-mail sent to their *@euroavia.eu* distribution list reaches its destination (Local Group inbox, President and/or Treasurer) and is answered within three (3) working days after being sent. Moreover, a message sent by phone or any previously agreed instant messaging service (e.g., WhatsApp, Telegram) must be answered by the President of Treasurer within three (3) days after it is sent. Furthermore, the President must be able to answer a predetermined date agreed by both EUROAVIA and the Local Group. As the internal organisation of each Local Group may differ, the Local Board may define another PoC instead of the President or Treasurer, having to inform the International Board about this decision and provide all the necessary contact information. The board of the Local Group is responsible for providing the necessary data (email addresses, address and phone number) to the Secretary of the International Board or other representative appointed by the International Board for such effect. --- # 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://public.euroavia.eu/miscellaneous/bylaws-subpages/12-contactability.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.