> For the complete documentation index, see [llms.txt](https://docs.joingather.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.joingather.org/roadmap-kickoff-to-launch/enrolling-members-your-recipe-for-success.md). # Enrolling members: Your recipe for success The extent to which an app is effective in facilitating-- or providing new-- community support is dependent on its rollout and use by both staff and members. We've gathered insights from our partners to help set you up for a successful launch. ## 3 Ingredients... ### 1. Enrollment during onboarding When you onboard new members to the organization, have them download the app and enroll while they're with you or on the phone. This will make them comfortable in the app from Day 1, and allow them to ask any clarifying questions that might impede use. ### 2. Trust building Members need to directly associate the app with their participation in the organization. To foster this, you can: 1. Send individual, personalized messages in the app (such as birthday wishes and graduation milestones) 2. Communicate through the app whenever possible (rather than email or text) 3. Directly send resources— find a resource you know is a great fit for a member? Copy the link (in app) and send it to them without ever leaving the platform ### 3. Member engagement tracking Keep your eyes on engagement. Not only will it help you know who to encourage to use the app more proactively, but engagement tracking can also give you insights into member needs, community involvement, and more. We've built in the ability to monitor resource viewing and event enrollment by member, as well as on the community level, so that you can tailor your programming to your members most effectively. --- # 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://docs.joingather.org/roadmap-kickoff-to-launch/enrolling-members-your-recipe-for-success.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.