> For the complete documentation index, see [llms.txt](https://docs.usereach.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usereach.ai/take-action/community.md).

# Community

Community finds relevant public discussions where your team can contribute useful, credible answers. It combines discussion discovery with context and reply preparation so opportunities can be reviewed before anyone participates.

## Review discovered discussions

The Community table shows the conversation, source, engagement, relevance, status, and available response context. Use search and filters to focus on discussions connected to your audience, products, or monitored topics.

Open a discussion to read the original post and available comments before deciding whether the brand should participate.

## Decide whether to engage

A good community opportunity:

* asks a question your team can genuinely answer;
* is relevant to the brand's expertise or users;
* is recent enough for a response to be useful;
* allows a helpful contribution without forcing a product mention; and
* does not require claims or experience the responder cannot support.

Skip discussions where the only possible contribution would be promotional, repetitive, or disconnected from the question.

## Prepare a response

Reach can help prepare a draft using the discussion and workspace context. Treat every draft as a starting point:

1. Verify that it answers the actual question.
2. Remove unsupported claims and unnecessary promotion.
3. Add first-hand expertise or evidence where appropriate.
4. Match the norms and tone of the community.
5. Review the final response before posting it on the source platform.

## Track the outcome

Update the status as the opportunity is reviewed or completed. Clear statuses prevent duplicate work and help the team understand which discussions were useful.

Community participation should build trust. Prioritize accuracy and usefulness over the number of replies published.


---

# 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.usereach.ai/take-action/community.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.