# Add images and videos to your outreach

Sometimes a screenshot or a short demo explains your idea better than a long message. Here's how to use them in ReacherX.

By Salman · 2026-08-23 · tutorials

Canonical: https://reacherx.com/blog/outreach-with-images-and-video

I'm a designer and developer. A lot of the time, the easiest way to explain what I mean is to show it. That's why images, GIFs, and videos are part of outreach in ReacherX.

You can attach them while writing a message, or give them to △ Agent to use in a plan. You still need to explain what the person is looking at. A video with “thoughts?” next to it isn't much of an introduction.

## Show the part they asked about

Say someone has posted that collecting feedback from clients is taking too much time. If your app helps with that, record the part where the client leaves feedback. They don't need a tour of every feature.

For design work, a before-and-after screenshot might explain more than a long description. For a bug, show the steps in a short recording. Use whichever makes the point easier to understand.

Hide private details and unrelated tabs before sharing. Add captions if the recording needs speech to make sense.

## Attach it and say what it's for

Choose the file in the message composer and add a sentence. For the feedback example:

> This clip shows how a client can leave feedback without creating an account.

If you're asking △ Agent to prepare outreach, attach the file to your request and explain when to use it:

> Use this demo in the first message to the designers I selected. It shows the client feedback screen. Keep the message short.

Then check the draft and the attachment. Platform formats and file limits change often, so the composer is the source of truth for the current restrictions.

Interactive demo: Attach a relevant product clip. Attach a product walkthrough to your reply.

## Can I reuse the same demo?

Yes. You can include it when asking for [plans for several people](/blog/create-plans-for-several-people). Give △ Agent any instructions that differ from person to person, then read the resulting messages.

The file can be the same, but why you're sharing it may be different. One person might have asked about client accounts. Another might care about collecting comments in one place. Explain the relevant part.

For something you'd rather say out loud, you can also [send your own voice note](/blog/send-voice-notes) in a supported conversation.