> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/get-started/anedot-101/contact.md).

# Contact Us

Find Anedot support contact options and hours, plus how to reach help for account setup or donation questions.

Anedot’s Support team is a U.S.-based group of product specialists for not-for-profit organizations. Hours: **Monday–Friday, 9 AM–5 PM CST**. Most requests receive a response within minutes; all inquiries are answered within **24 business hours**.

The Support team partners with Engineering and Product. Feature suggestions and extra context are welcome.

## Fastest Support

| Who                             | How                                                                                                                               |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Customers**                   | Email <help@anedot.com> or submit a request at [anedot.com/getsupport](https://www.anedot.com/getsupport)                         |
| **Donors**                      | Visit [DonorSupport.com](https://www.anedot.com/donorsupport) (also [donor.anedot.com/support](https://donor.anedot.com/support)) |
| **Applications / underwriting** | <accounts@anedot.com>                                                                                                             |
| **Legal**                       | <legal@anedot.com>                                                                                                                |
| **Copyright / DMCA**            | <dmca@anedot.com>                                                                                                                 |

Please do not submit multiple emails or requests for the same inquiry.

Anedot does **not** provide inbound phone support. Email-based support allows account verification, documentation, and accurate solutions. Where needed, the team may schedule a call.

## Additional Customer Support (Meetings)

[Schedule a meeting](https://www.anedot.com/meeting) for complex troubleshooting that needs screen sharing (Google Meet).

After you submit a meeting request, you receive an email with the meeting link and details. The team may follow up by email first to confirm account access or gather information. Some requests may still need to be handled by email—use the [Support Form](https://www.anedot.com/getsupport) before or after a meeting if needed.

{% hint style="info" %}
Only authorized users on the fundraising account may schedule an account-specific support meeting. You must have active login access. Requests from people who are not listed as users may be declined or need extra verification.
{% endhint %}

## Physical / Mailing Address

Anedot is fully remote and distributed in the United States. No employees report to this address. The address below is published for corporate, compliance, and mailing purposes ([anedot.com/contact](https://www.anedot.com/contact)):

```
Anedot Inc.
3723 Greenville Ave
Ste 41002
Dallas, TX 75206-5311
United States
```

**Related:** [Office Closure Schedule](/get-started/anedot-101/office-closure-schedule.md)


---

# 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.anedot.com/get-started/anedot-101/contact.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.
