Source: https://asterly.co/resources/blog/step-by-step-reply-instead-of-video

[Blog](https://asterly.co/resources/blog)

# Stop Sending Support Videos: Reply With a Link to Steps Instead

4 November 2026

![A faded video player with a play button sits behind a vertical stack of three numbered step cards, each with a small screenshot and a progress chip, on a soft coral wash.](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/featured-hifi.png)

Support videos feel helpful to the person who recorded them.

The catch: the customer has to watch the whole thing, pause it, squint at your cursor and rewind when they miss the click.

So how do you send a customer step-by-step instructions instead of a video? Write numbered steps with one action each, add one screenshot per step with the click highlighted, put it on a page with a link and reply with that link plus one line of context.

In this post, we'll cover when a video is still fine, how to build the steps and how to write the reply.

## Why Do Videos Frustrate Customers?

[![Two side-by-side cards comparing a support video with numbered steps: a video can't be skimmed, searched or easily updated, while steps can be skimmed, searched and fixed one line at a time.](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/video-vs-steps.png)](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/video-vs-steps.png)

A video asks the customer to watch at your speed. Steps let them glance, click and glance back.

Think about how people actually follow instructions. App in one tab, help in another. Glance, click, glance back.

A video breaks that loop.

-   **You can't skim it.** Step 4 is somewhere around the one-minute mark. Probably.
-   **You can't search it.** "Where was the export button?" means scrubbing.
-   **It moves at your speed.** You know the app. They don't.
-   **It's hard to update.** One renamed button and the whole video is out of date.

For example, a customer needs to change their billing email. Your video starts with "Hey! So, first we're going to head over to..." and they're already looking for the skip button.

## When a Video Is Still Fine

To be fair, videos have their place.

-   **Showing a feeling:** a product tour where the point is "look how smooth this is."
-   **Explaining a concept:** why something works the way it does.
-   **Something truly visual:** dragging, drawing or animation you can't describe in a sentence.

For a "how do I..." question with a clear end, steps win.

## How to Build the Steps

[![A vague one-line instruction, "Update your billing info in settings", next to four numbered steps with exact button labels in bold and a heads-up for non-owners. Demo data.](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/bad-vs-good-step.png)](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/bad-vs-good-step.png)

Illustrative example with demo data: one action per step, exact labels in bold.

Do the task yourself, once, at normal speed. Grab a screenshot right before each click.

Then write one line per step:

-   **One action:** one click, one field or one choice.
-   **Exact labels:** the button name as it appears, in bold.
-   **One highlight:** a box around the thing to click.

For example, here's a bad step:

> Update your billing info in settings.

Here's the same thing as good steps:

> 1.  Click your profile picture in the top right.
> 2.  Click **Billing**.
> 3.  Click **Edit** next to Billing email.
> 4.  Type the new address and click **Save**.

Four short steps beat one vague one. Every time.

Add one line of context on the step where people get stuck. For example: "If you don't see Billing, you're not the account owner. Ask your admin."

## Put It Behind One Link

Where do the steps live?

Not pasted into the reply as a wall of text and images. Email clients mangle that, and next week you'll write it again.

Put the steps on a page with a stable link: your help center, a public doc or an internal wiki your customers can see. One task per page.

That link becomes reusable. The next customer who asks gets the same answer, instantly.

## How to Write the Reply

[![A short demo reply to a customer with three numbered highlights: the guide link, a heads-up about the tricky step, and an invite to reply if the screen looks different.](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/reply-template.png)](https://asterly.co/resources/blog/images/step-by-step-reply-instead-of-video/reply-template.png)

A three-part reply: the link, the heads-up and the invite. Demo customer and address.

The reply itself should be short. The steps do the heavy lifting.

A simple template:

> Hi \[name\],
> 
> Here's a step-by-step guide for that: \[link\]
> 
> It takes about a minute. Step 3 is the one people usually miss, so keep an eye out for the **Edit** button next to Billing email.
> 
> If anything looks different on your screen, reply here and I'll sort it out.

Three things are doing work here:

1.  **The link** gives them the steps.
2.  **The heads-up** points at the tricky step before they get stuck.
3.  **The invite** to reply tells you when the guide is out of date.

For example, if a customer replies "I don't see Edit," that's not a failure. That's your guide telling you it needs a fix (free QA, honestly).

## Make It a Habit

One guide doesn't change much. A habit does.

-   **Every repeat question gets a guide.** Second time you answer something, write the steps.
-   **Every guide gets a saved reply.** Link plus heads-up line, ready to send.
-   **Every guide gets a date.** "Last checked" at the top, so you know what's fresh.

I'll admit it: typing out the answer "just this once" feels faster. It's faster exactly once.

## The Wrap-Up

Customers don't want to watch you use the app. They want to get it done themselves.

Numbered steps, one screenshot each, behind one link. Short reply, clear heads-up.

Less watching, more doing.

_Written by the Asterly team._

[All posts](https://asterly.co/resources/blog)