> For the complete documentation index, see [llms.txt](https://docs.stawishadada.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stawishadada.org/policies/complaints-and-feedback.md).

# Complaints and feedback

How to give feedback or make a complaint to Stawisha Dada Women Group, and what happens next.

{% hint style="warning" %}
**Draft awaiting committee approval.** Approved on: \_\_\_\_\_\_\_\_\_\_\_\_ · Next review: \_\_\_\_\_\_\_\_\_\_\_\_
{% endhint %}

We want to hear from you, whether you have praise, an idea or a complaint. Your feedback helps us improve.

## Who can use this

Trainees, parents and guardians, members, customers, partners, donors and anyone in the community.

## How to give feedback or complain

* **Speak** to a trainer or any official.
* **Phone or WhatsApp:** +254 796 969 603
* **Email:** <info@stawishadada.org>
* **Write:** P.O. Box 120, Endebess, 30201, Kenya

If your complaint is about a particular official, you can raise it with another official.

{% hint style="danger" %}
**If someone is at risk of harm,** do not wait for this process. Follow the [Safeguarding policy](https://docs.stawishadada.org/policies/safeguarding.md), or call the police on 999 or 112.
{% endhint %}

## What happens next

1. We **acknowledge** your complaint within **3 working days**.
2. A person not involved in the matter **looks into it**.
3. We **reply** with what we found and what we will do, usually within **14 days**.
4. If you are not satisfied, you can ask for the **full committee** to review it.

We keep complaints confidential, and no one will be treated badly for raising a concern in good faith.

## How we learn

The committee reviews complaints and feedback at its meetings and uses them to improve our work.


---

# 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.stawishadada.org/policies/complaints-and-feedback.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.
