> For the complete documentation index, see [llms.txt](https://docs.lightpost.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lightpost.app/core-concepts/groups/messaging-policies/communication-use-policy.md).

# Communication Use Policy

### Overview

Lightpost offers the ability to send emails, SMS/MMS messages and voice calls to groups created in your congregations' account.

The users added to these groups are **not required** to be **members** of your congregation to be able to send communication using these methods.

A great use case for this is creating a "Former Members" group that you can send occasional emails to, with news and updates about events and things happening with your congregation.

### Known Users Only

However, you **may not** use the group messaging features to:

* send **unsolicited** communication to **anyone**
* send messages to users who **would not expect** to be in your Lightpost account
* send messages to **email lists** acquired by any means
* send messages to **phone lists** acquired by any means
* send messages to people who have **requested** to **not receive messages**

The people you send messages to **must** be added by an admin of your congregation, and **must** have or had a **direct and intentional affiliation** with your congregation, to the extent that they **would not be surprised** to receive any type of communication from you.

### Violations

Any congregation found to be adding users based on lists acquired for marketing or outreach purposes risks immediate account closure. &#x20;

**Lightpost is not a marketing or advertising tool.**

If you're in need of a marketing tool to send communication to users from lists (email, phone, etc), please reach out to Lightpost support for suggestions on the best way to do this using industry tools built specifically for this purpose.

The reputation of Lightpost is of upmost importance in this regard and there are no exceptions to this rule.


---

# 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://docs.lightpost.app/core-concepts/groups/messaging-policies/communication-use-policy.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.
