> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/study-basics/design-a-mission/piping-recall-logic.md).
# Piping (recall) logic
| Study type | Availability |
|---|
| Screeners | true |
| Usability tests | true |
| Media surveys | true |
| Intercept studies | true |
| Diary studies | false |
Piping logic, also known as recall logic, lets you dynamically reference a participant’s answer from a previous question into a later question. This keeps your missions feeling custom, personalized, and engaging.
Maybe you’ve asked participants their favorite fruit. Later, instead of asking every participant generically, “Why is that your favorite fruit?” you can use piping logic to insert their indicated favorite directly into the question. For example, if one participant indicates strawberries are their favorite fruit, you can automatically ask them “Why are strawberries your favorite fruit?” thanks to piping logic.
{% hint style="info" %}
Piping logic in Dscout is different from branching studies. For information on how to send participants to certain questions depending on their answers, see [Skip logic](https://help.dscout.com/hc/en-us/articles/360038668491).
{% endhint %}
## Add piping logic to a question
You can add piping logic to any question type, including photo and video questions. However, you can only pipe responses *from* closed-ended question types:
* Multiple choice
* Ranking
* Scale
* Number
{% hint style="info" %}
You cannot recall answers from a question that already uses piping logic. For example, if Question 2 recalls a response from Question 1, you cannot recall a response from Question 2 in another question.
{% endhint %}
{% stepper %}
{% step %}
In your mission, add your source question (the question you want to recall an answer from).
{% endstep %}
{% step %}
Add your destination question (the question where you want to recall responses from your source question).
{% endstep %}
{% step %}
In the prompt of your destination question, type an **@** symbol. A list of available questions is displayed.
{% endstep %}
{% step %}
Select your source question from the list.
{% endstep %}
{% step %}
Type the rest of your question.
{% endstep %}
{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}
Now, when you launch your mission, participants’ responses from your source question will automatically be placed where you’ve inserted piping logic into your destination question.
{% hint style="success" %}
“Other” responses can be recalled with piping logic. They’ll be added to your destination question exactly as entered by the participant. However, we do not recommend allowing for “None of the above” options in source questions as piping this response will likely not work in the context of your destination question.
{% endhint %}
## View piping logic in analysis
When viewing responses, you’ll see piping logic displayed in one of two ways.
Viewing responses at the question or activity level, you’ll see your source question mentioned in the prompt of your destination question:
However, viewing responses at the participant level, you’ll see that participant’s piped response anywhere you’ve used piping logic:
---
# 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://help.dscout.com/study-basics/design-a-mission/piping-recall-logic.md?ask=&goal=
```
`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.