> ## Documentation Index
> Fetch the complete documentation index at: https://docs.theharvest.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting help

> How to reach us, and what to include so it gets solved first time.

## Two ways to reach us

<CardGroup cols={2}>
  <Card title="From inside Harvest" icon="headset">
    The contact form in the app. Use this one where you can, because it arrives with your church already identified.
  </Card>

  <Card title="From the website" icon="globe" href="https://theharvest.site/contact">
    The contact form on theharvest.site. Use this if you cannot sign in.
  </Card>
</CardGroup>

<Note>
  Harvest is built by a small team. You are not writing to a ticket queue — a real person reads it and answers.
</Note>

## Before you write

Check [Troubleshooting](/help/troubleshooting) first. Most of what churches report turns out to be one of about eight things, and each has an answer you can apply in two minutes rather than waiting on a reply.

In particular, if a **number looks wrong** — an empty dashboard, a member with no giving history, a campaign bar that will not move — that page almost certainly has it.

## What to include

The difference between one reply and four is usually these.

<Steps>
  <Step title="Your church's address">
    `yourchurch.theharvest.app`. Without it we cannot look at anything.
  </Step>

  <Step title="What you expected, and what happened">
    "The dashboard should show 400 of giving; it shows 0." That is enough. We do not need a diagnosis.
  </Step>

  <Step title="Where you were">
    The screen, and whether you were on a phone or a computer. Several things behave differently below a certain width.
  </Step>

  <Step title="A screenshot">
    More useful than any description. If there is an error message, capture all of it — the long code in the middle is the part that identifies the fault.
  </Step>
</Steps>

<Tip>
  If it affects one particular person — a member who cannot see something, a volunteer who did not get an email — include **their email address**. Almost every problem of that shape comes down to which email is on their record.
</Tip>

## What we will never ask for

<Warning>
  We will never ask for your password, and we will never ask you to send card or bank details. If anything claiming to be Harvest does, it is not us.
</Warning>

We may ask you to add a temporary admin so we can see what you are seeing. You can remove it the moment we are done, and you are free to say no.

## Things we cannot help with

Being clear about this saves you writing.

* **Your congregation's payments.** Harvest never sees them. If money is missing, late or disputed, your payment provider — PayPal, Revolut, Wise — is the only one who can look. See [How giving works](/giving/how-giving-works).
* **Whether a gift is tax deductible**, or what your year-end statements must say. That is your accountant, or your jurisdiction's rules.
* **Your safeguarding process.** Harvest records who registered and who attended. It is a register, not a safeguarding system.

## Reporting a security problem

If you think you have found something that exposes data — yours or another church's — write to us through either form and say so in the first line. Please do not post it publicly. We will not treat it as an ordinary support ticket.

## Asking for something that does not exist yet

Feature requests are welcome through the same forms.

<Note>
  We do not publish a roadmap, deliberately. A roadmap is a set of promises, and we would rather ship than promise. What we do publish is [what we have shipped](/changelog), updated as it happens.
</Note>


## Related topics

- [Set up your church](/getting-started/set-up-your-church.md)
- [Glossary](/help/glossary.md)
- [Troubleshooting](/help/troubleshooting.md)
- [index](/index.md)