> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-your-group/creating-your-group-2.md). # Availability Waves Create a group to define all the ways your staff interact with Availability. ## Availability waves - schedule your mail out We know you're busy, so we've created a way to automate sending out availability calendars and automating the follow-ups. **First wave** First up, a question: Do you want to schedule your first wave of requests? This means that you can send out the first wave of requests for this group of staff on a specific date. If you select "Yes", then you'll need to specify what date you want to send the first request on. After that, you can pick a submission deadline (you've got 4 options: 1 week, 2 weeks, 3 weeks, 4 weeks) and specify if the deadline is a hard or soft one. A hard deadline means that instructors can not submit their availability past this date. A soft deadline means that instructors can submit their availability after this date but they will be reminded to submit by the due date. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043043539692/original/1htAzmy-YfX-foPidaib-8MaXbSBA9vRqA.png?1567088413) **Other Availability Waves** Once you've setup your first wave, you can setup your Other Availability Waves. These other waves are for instructors that you add to the group after the initial wave goes out. You've got two options with these staff - you can automatically send out the availability request when the instructor is added to the group or you can choose to send the availability request manually after adding the instructor to the group. After you've selected this option, you can pick the deadline date and if you want to make it a soft or hard deadline as per the initial wave. **Reminders** The last part of automated notifications are the reminders. Here you can set after what period you want the first reminder to go out (1 through 4 weeks), how many weekly reminders should go (1 to 2) and when the deadline reminder should be sent out (1 to 5 days before the deadline closes.) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043043539720/original/d8ZciWcccTtB_AV62BOUiP3DVnqhD9_4_w.png?1567088419) Once you've selected all these options, you're ready to click Next and move on. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043043583825/original/MLjCq33KnTSQ2K-M02lFXxyaSkAKg82AHQ.png?1567097993) --- # 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://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-your-group/creating-your-group-2.md?ask=&goal= ``` `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.