> 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/learn/build-relationships/organizing-meetings-with-external-invitees.md).

# Organizing Meetings with External Invitees

7 minute read

It is important to ensure that when inviting people outside of your company to meetings all logistics and details get into both of your calendars, so everyone remembers to be there and has the information they need. Daylite allows you to add external people as invitees to the appointments you create, sends them an invitation by email, notifies you of their responses, and records their replies in Daylite - keeping everything in one place so nothing falls through the cracks!

The Meeting Invite functionality within Daylite -

* [x] Is compatible with all popular services including Outlook and Microsoft 365
* [x] Notifies you when someone replies to the meeting invitation
* [x] Allows customization of the invitation emails

{% hint style="success" %}
Remember - When adding other Daylite users as invitees known as internal invitees, they are invited directly with a push notification and the appointment will show in their calendar. They will not receive an invitation by email.
{% endhint %}

Invite external meeting participants with confidence and ease. Here’s how!


---

# 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/learn/build-relationships/organizing-meetings-with-external-invitees.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.
