# Customer journeys

Voor de nieuwe situatie heb ik weer customer journeys gemaakt. Door de 'blije punten' kun je concluderen dat deze app verschillende behoeftes op het gebied van grofvuil en upcyclen van mijn doelgroep vervuld. De [pijnpunten en problemen](/design-rationale/1.-onderzoek/doelgroep/customer-journeys.md) die er eerst waren zijn nu opgelost door de app. 

### Hergebruiken grofvuil <a href="#mira" id="mira"></a>

![Customer journey 2 - Mira](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPOI6OdJW8ArowyqW02sp%2Fuploads%2FZGzSDWPczxci9JiuXYe9%2FCustomerJourney_Mira_Nieuw.png?alt=media\&token=fb0f46a3-6b83-4ca6-9d7a-d7c015abccaf)

### Upcyclen grofvuil <a href="#bob" id="bob"></a>

![Customer journey 2 - Bob](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPOI6OdJW8ArowyqW02sp%2Fuploads%2FlH2H2frs5x1VqCw3KZue%2FCustomerJourney_Bob_Nieuw.png?alt=media\&token=6b308551-1ff0-46ac-9d1d-e4ffe83bcf99)


---

# 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://kim-garrard.gitbook.io/design-rationale/5.-valideren/customer-journeys.md?ask=<question>
```

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.