# Overview #### Overview After you've made a simple GET request (see [Quick Start](/implementation-guides/quick-start.md)), and tried a few [List request](/basic-concepts/list-request.md), you can send a *Crowdsourcing Report.* This is a way for end users to send feedback on MRS results. Examples that your users may wish to report: * Incorrect merchant ("This is Jacob's Bakery not Jacob's Mechanics") * Incorrect location ("This is not in Bristol, it is in London") * Incorrect logos ("This is the logo for Mandy's Flowers not Mandy's Pizza") As a goal, it continually improves the clarity and accuracy of the information and further reduces the calls to the call centre + match rates + user trust. Crowdsourcing is listed as a separate step because it requires extra user interface development (e.g. prompt to fix/report error at bottom on transaction details). Here's an example of how you might implement a crowdsourcing sequence: 1. Your app enriches a transaction, using the `/merchant/list` or `/merchant` endpoints (see [Quick Start](/implementation-guides/quick-start.md)). It records the `X-Request-Id` and `X-Timestamp` headers that are returned for each enriched transaction. It also records the `transactionId`. 2. This enriched transaction is shown to the end user in your banking app. 3. The user notices that the merchant name is wrong - it's Peter's Pizza, not Peter's Pezza! 4. They click on the transaction in your app, taking them to a 'Detail' screen (see [Recommended UX](/implementation-guides/recommended-ux.md)). 5. The Detail screen has a button - 'Improve name, location or logo'. The user clicks this button. 6. They specify the correct name in a dialog - "Peter's Pizza", and click 'Send'. 7. Your app takes the `X-Request-Id` and `X-Timestamp` headers that were originally recorded for that transaction and sends them to the `/crowdsourcing` endpoint, along with the User's Feedback. Next, let's see how to implement this in [Crowdsourcing Example](/advanced-use-cases/crowdsourcing/crowdsourcing-example.md). --- # Agent Instructions: 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: ``` GET https://devs.snowdropsolutions.co.uk/advanced-use-cases/crowdsourcing/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.