> 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-3.md).

# Email Templates

## Email templates

### **Request availability email template**

Now that you've setup conditions for the group, you'll need to craft the emails that will go out to your staff. The left hand side of the screen is your editor and the right hand side your preview.

This is the first email that your staff will receive regarding availability, so it pays to be as clear as possible.

We've dropped in some generic text to get you started, feel free to edit or delete as you will in order to craft the message that you believe your staff need to see. You can use the insert mail merge field to pull certain data from the instructors profile.&#x20;

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043043584101/original/c9E2ZKSn6x3ys4CkBQabspgcaDY9y_DjFA.png?1567098083)

### **Reminder email template**

Once you've got the initial email up and running, you can move on to the Reminder Email. This is the one that'll go out automatically to folks that haven't completed their availability calendars.

We've again dropped in some generic text to get you started but feel free to edit, delete and start again. You know your staff best and to what pressures they respond.

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043043584127/original/oZ2Bo0DoxrGPp1eEK7MUe0askRixgwh65Q.png?1567098089)

***

### **Introduction cover letter**

After you've created your emails, you then have an opportunity to craft the cover letter. The cover letter is the webpage that your staff will see after clicking on Submit my Work Availability from the email they received.&#x20;

This is a good opportunity to outline your expectations and how the process works. We've crafted some generic text to get you started based on what we've seen over the years. Feel free to adjust if you want to highlight different areas for your staff.

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043043584152/original/E0CUolrfQsvmEk2xKK2pCwPCCsndVZBnbA.png?1567098095)

Once you've completed the cover letter, hit <mark style="color:blue;">**Save**</mark>.&#x20;

{% hint style="success" %}
**🎉 That's it!** You've got a calendar and a group set up. You can create as many as you'd like, but if you're happy with the number of calendars and groups you've built already, it's time to [move onto mailout](/flaik-knowledge-base/for-sups-managers/availability/mail-out.md).&#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://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/availability/creating-your-group/creating-your-group-3.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.
