> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voyager.so/llms.txt
> Use this file to discover all available pages before exploring further.
# Write a useful request
> Describe the result, attach references, and guide Voyager while it works.
Tell Voyager what someone should see, hear or understand when the work is finished. You can describe the result in ordinary language.
Start with a connected chat account and any files you want to use. You do not need to choose a creative tool unless you have a preference.
## Give the agent a clear starting point
Say what you are making, who it is for, and where it will appear. Include the duration and shape when they matter: “a 15-second vertical video for people seeing our product for the first time.”
For an image, give the size or intended use. For an edit, say which footage to use and which moment or message matters most.
Include exact words that must appear, the order of the main ideas, and the visual style. Describe references by role: “Use this photo for the product, and this other image for the colors.”
Say what to preserve during a revision. “Keep the music and timing; replace only the final title” gives the agent a clear boundary.
Use **Add attachment → Attach files**, drag files into the message box, or paste an image. Check the attachments before sending.
To refer to a file already in the working folder, type `@` and choose the file. You can also drag it from **Files** into the message box; this adds a reference and does not move the file.
Name anything the agent needs to respect: an existing editor, approved footage only, no voiceover, a required file format, or a budget.
Press Enter or click **Send**. Use Shift+Enter to add a new line without sending.
## A request you can adapt
```text theme={"system"}
Make a 15-second vertical product teaser for first-time customers.
Use the attached bottle photo and logo. Keep the product's shape
and label accurate.
Start with “Meet your daily companion.” End with “Made to go places.”
Use cream backgrounds, dark green type and calm, deliberate motion.
Keep text away from the top and bottom edges.
Use the supplied assets and local motion graphics only, with no
new paid media or audio generation. Show me a draft before the final
render. Deliver an MP4 and keep the editable source.
```
You can also start small: “Trim this clip to the strongest 20 seconds and add readable captions.” Add details when the first result shows what needs changing.
## Choose a workflow when it helps
The **Making:** choices describe the kind of output, such as **Motion graphics or explainer**, **AI-generated video**, **Image**, or **Edit existing footage**. Choose one if it matches your task; you can also describe the task without choosing a chip.
For a specific workflow, type `$` to open the skill picker. Type `/` to see available commands. These are optional shortcuts; an ordinary request is enough to begin.
The model picker chooses the agent answering your chat. To request a particular image or video model, name it in your message. [Chat accounts and generation accounts](/account/accounts-and-agents) pay for different parts of the work.
## Guide work already in progress
You can send a follow-up while the agent is working. **Settings → General → Follow-up behavior** controls what happens:
| Choice | Behavior |
| - | - |
| **Steer** | Send the follow-up into the current turn. This is the default. |
| **Queue** | Hold the follow-up until the current turn finishes. |
Queued messages are not kept after a reload or quit. Wait for important queued instructions to send, or copy them before closing Voyager.
Use **Stop** if you need the agent to stop its current turn. Check **Jobs** as well if it has already started a generation or render; stopping the chat is not a promise that submitted work has been cancelled.
## Check that Voyager understood
Read the first response or plan. Check the format, source files, text and paid work before continuing. If you want to answer every question yourself, set **Question answers** to **Always ask**.
## Common problems
Image attachments can be up to 10 MiB each; other file attachments can be up to 50 MiB each. For larger footage, put the files in the project folder and reference them from **Files** or with `@`. Tell the agent which files to use.
Add a concrete audience, exact wording and one visual reference. Describe what makes that reference useful, such as its lighting or pacing, rather than asking only for something “professional.”
Say which existing assets it should use and whether paid generation is allowed. For text and shapes, ask for [motion graphics](/guides/motion-graphics). Set your [approval and spending preferences](/guides/approvals-and-spending) before continuing.
Decide when questions wait for your answer.
Give feedback on the exact frame or moment.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.