# Target audience

***

Always specify your intended audience. This helps DeepWriter tailor the language, tone, depth, and examples to suit the reader’s level of understanding and interests. Let's compare the following examples:

> &#x20;<mark style="color:purple;">"Explain quantum physics for high school students."</mark>&#x20;

versus...

> <mark style="color:purple;">"Prepare a research brief on quantum entanglement for graduate-level physicists."</mark>

The difference in audience changes everything—from the vocabulary used to the complexity of the arguments. DeepWriter uses this context to decide whether to simplify concepts, include technical jargon, or adopt a certain level of formality.

{% hint style="info" %}
**Pro tip:** Include both the audience type and their intent. For example:

* "Create a review for HR managers evaluating new payroll software."&#x20;

versus...

* "Write a persuasive pitch for startup founders considering payroll automation for their growing teams."
  {% endhint %}

This extra layer of context gives DeepWriter a clearer direction and increases the chances of generating something that actually works for your end goal.

If you're unsure how to describe your audience, try answering a few quick questions:

* What is their expertise level on this topic?
* Are they reading this to be informed, convinced, or educated?

Once you've answered these questions, you can also set the tone for the generation.


---

# 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://docs.deepwriter.com/tips-tricks-and-hacks/prompt-elements/target-audience.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.
