> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/building-relationships/bulding-relationships/organizing-meetings-with-external-invitees/sending-invitations.md).

# Sending Invitations

When you are done editing or creating the appointment, you are prompted to send the invitation email. You can customize this email before sending by editing the subject and message, choosing the language, whether to include the details field, and whether to show the list of invitees to everyone.

(a) If you do not wish to show the invitees, the email will include only the person organizing and the individual person who is receiving the email invitation;

(b) If you select ‘show invitees’, all invitees will be listed at the top.

(c) You can also choose to send reminder emails to external invitees before the meeting. Select **None** to skip reminders, **Default** to use your company's default reminder times, or **Custom** to set specific times for this appointment (up to 2 reminders)

(d)You may also choose not to send out invitations using the “Don’t Send” button, which you might do if you have already discussed when to meet by some other form of communication such as phone or messaging.

(e) Clicking the “Cancel” button will return you to editing or creating the appointment in case you want to make further adjustments before sending out invitations.

<div align="left"><figure><img src="https://content.gitbook.com/content/xGMajZOd0MK6qFz9gMhh/blobs/NqaLt8b2I6W2ZfHHj1Nm/send%20meeting%20invitation.png" alt="" width="563"><figcaption></figcaption></figure></div>

### Invitation Email

The invitation email will look like this to the invitee. They can use their calendaring service or application to reply.

<figure><img src="https://content.gitbook.com/content/xGMajZOd0MK6qFz9gMhh/blobs/5myz6dKsA7n9urs7LlvU/Mtg%20Invites%20Blog%5Cinvitation%20email%402x.png" alt=""><figcaption></figcaption></figure>

### Sending Status

The status can be seen for each invitee in the appointment detail card, and will change from (a) “Sending Invitation” to (b) “Invitation Sent” once the email is sent.

If you choose “Don’t Send”, then the status will show as “No Invitation Sent”.

<figure><img src="https://content.gitbook.com/content/xGMajZOd0MK6qFz9gMhh/blobs/EfleQu893rWRlastu5Jj/Creating%20and%20Sending%5Csending%20status%402x.png" alt=""><figcaption></figcaption></figure>

### Resend Invitations

On occasion, you may need to resend a meeting invitation to a participant(s).

To resend an invitation to **a single invitee**, click on the status text to the right of the invitee token, and choose “Resend Invitation…”

If the invitee(s) have not been sent an invitation before, their option changes to “Send” invitation (rather than “Resend”)

<figure><img src="https://content.gitbook.com/content/xGMajZOd0MK6qFz9gMhh/blobs/BuP41z9zGMX5Z2SQzGO1/Creating%20and%20Sending%5CResend%20Invitations%20single%402x.png" alt=""><figcaption></figcaption></figure>

To resend invitations to **all invitees**, click on the “invitees” label in the detail card, and choose “Resend Invitations…”

<figure><img src="https://content.gitbook.com/content/xGMajZOd0MK6qFz9gMhh/blobs/D2GKmuKjATLyZSOFQIbM/Creating%20and%20Sending%5CResend%20Invitations%20Group%402x.png" alt=""><figcaption></figcaption></figure>


---

# 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.daylite.app/help/building-relationships/bulding-relationships/organizing-meetings-with-external-invitees/sending-invitations.md?ask=<question>&goal=<user_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.
