To send video messages to customers, prepare a focused answer, record the information they need, review the saved result and deliver it with a clear written introduction. Check the recipient’s access before relying on the message as your support response.
This guide covers asynchronous video answers through Screendesk, including sharing controls, helpdesk library delivery and follow-up. It does not assume every customer wants video or that sending a recording resolves the case. For broader use cases and team planning, see video messaging for business.
1. Decide what the message should help the customer do
Review the conversation and identify the question you can answer accurately. A useful message shows a known task, explains a relevant result or clarifies what information is still needed. If the next instruction depends on watching the customer’s response, consider a live conversation instead.
Check the customer’s account context and product version. Your demonstration may show a feature or permission they do not have. Explain that distinction rather than recording an administrator workflow as if it applies to everyone.
For a fictional example, a customer cannot find an export control. A focused message can show its location, identify the permission required and explain what to reply if the control is absent. That is an illustrative script; it does not claim that a particular customer completed the task.
2. Outline a short, actionable explanation
Use the customer’s relevant context, one task and a specific closing action. Avoid adding private account details to a recording intended for reuse. A personal greeting can accompany a generic demonstration in the written reply.
Video message outline Customer question: Relevant account/version context: Starting state and prerequisites: Opening: “This video shows [task/result].” Action: “Open [location] and choose [control].” Explanation: “This matters because [reason].” Result: “You should see [verified expected state].” Exception: “If you see [different state], [appropriate next step].” Closing: “Please [one action] and reply with [specific result/question].” Written summary: Audience and approved sample data: Review points before sending:
Choose the length the task requires. Split unrelated topics when that makes them easier to use, but keep necessary context with the instruction. A universal two-minute limit would not tell you whether the explanation is complete.
Use a calm, direct tone. Reassure the customer about the next support step without promising an unverified fix. For a longer procedural lesson, use our training video planning guide.
3. Record the content that serves the answer
Use your workspace’s supported recording workflow and choose the visual content deliberately. A software task usually needs the relevant application view; a spoken update may not. Check whether the selected recorder supports the desired screen and camera arrangement.
Screendesk’s current video library page describes screen recording with a webcam, uploading existing videos, and editing options including trim, cut, thumbnail changes and a call-to-action button. Verify the controls available in your workspace rather than assuming every recording mode or editor capability.
Prepare approved sample data, reduce irrelevant notifications and inspect the actual shared area. A selected window can still contain private information. Make a short saved trial if you have changed the microphone, camera or capture arrangement.
Describe the important action as you show it and pause at the result. Point out a control by name instead of relying only on cursor movement. The Screendesk Chrome extension documentation lists drawing, arrows or shapes, click highlighting and blurring. Those are documented extension capabilities, not universal controls in every browser recorder.
Stop when the intended answer and next step are complete. If an instruction is wrong, correct or replace it before sending. A minor speech hesitation may be harmless; an incorrect command or unclear result needs attention.
4. Review the actual saved video
Watch the saved result through the delivery route you intend to use. Confirm understandable speech, readable controls and the demonstrated outcome. Check transitions where a menu, dialog or different window becomes important.
Verify any captions or transcript you provide, particularly product terms, names and actions. W3C’s media planning guidance distinguishes captions, descriptions of essential visual information, transcripts and accessible playback. Keep a written route to the answer for customers whose needs the video does not meet.
Inspect the content for this audience, including any thumbnail or preview. Editing one section does not automatically remove information from every related transcript, preview or written message. Use the appropriate review process before sharing more broadly.
5. Choose the delivery method
Screendesk’s Share menu provides the following options:
| Method | What it provides | Delivery check |
|---|---|---|
| Share link | A URL opening the recording’s playback page | The recipient can open it with the selected access setting |
| Website embed | An iframe copied from the Website row | The destination page allows the embed and presents it usefully |
| GIF preview | An animated image linked to the full recording | The message still includes a usable text link |
| Download | A video file saved to your computer | The final file and destination support the intended viewing |
For a link, open the recording and use Share. For a website embed, use Website → Copy code in the Embed section. For a GIF, generate it if needed, then copy the rich preview link. The GIF points to the recording rather than carrying its full spoken explanation.
To save a file, use the Video row’s Download option. The documented download uses the edited version when available, otherwise the processed or original version. Attaching that file to email is a separate delivery decision; check attachment limits and inspect the recipient’s version.
6. Check who can open the message
The sharing documentation distinguishes Anyone with link, which allows viewing without login, from Workspace members, which requires workspace membership and login. Sent recordings expose visibility controls through the Share dropdown. Check the actual setting rather than assuming that a private email makes its video link recipient-only.
Do not send a workspace-restricted link to an external customer expecting it to work. If wider link access is unsuitable for the material, choose an approved alternative. Test the intended audience’s experience; opening the link while signed in as the owner does not establish customer access.
Keep the written explanation and recording’s access decision aligned. A public knowledge-base example and a customer-specific account demonstration may require different handling.
7. Send a library video from the helpdesk
The documented helpdesk workflow uses the Screendesk sidebar: choose Send from Library, search by title or a tag such as #onboarding, then select Share beside the chosen video. The link is inserted into the conversation. Intercom also provides a personalized-message area.
Confirm that the administrator has connected the supported integration. Preview the message in your actual channel. A link and thumbnail do not mean every email client or helpdesk provides in-place video playback.
Use the following original reply template to explain why the recording is relevant. Adapt the prerequisites and next action to the case.
Hi [name], This video shows [specific task] for [relevant context]: [Descriptive video title and link] Before you start: [prerequisite, if any]. The key steps are: 1. [Step] 2. [Step] 3. [Expected result] Please reply with [specific confirmation or remaining question]. If you cannot open or use the video, [written alternative/support route]. [Agent/team]
8. Reuse reviewed answers without losing context
Before sending a library answer, check its version, prerequisites and relevance to this customer. A popular recording can still be outdated. Assign an owner to update or retire it when the underlying procedure changes.
The library management documentation states that Admins and Editors can add or remove videos; Members can browse and use them. Authorized users can choose Add to library from the recording menu or page. The library supports title and label filtering. Follow the documented library workflow rather than assuming that ordinary folder organization and library membership behave identically.
Keep reusable demonstrations free of unnecessary customer-specific details. Personalize the surrounding reply and identify any important exception. If the example no longer fits, create a corrected message or use another channel.
9. Follow up on understanding and the result
The first-party library page documents view counts, a Seen by list and first-view email notifications for sent videos. Use those as viewing signals. Do not infer that the customer understood the instruction or resolved the problem merely because the message was opened.
Ask for the relevant result and inspect later related contacts. Record whether the customer could access the message, whether the instruction matched their situation and what remained unresolved. Use recurring feedback to improve the answer or the underlying product guidance.
If your tools provide additional analytics, verify the actual event and definition before using them. A view count does not provide a watch-time curve or a detailed rewatch heatmap. Keep unknown outcomes visible rather than recording silence as success.
Video message send check Correct question and customer context: Reviewed video title/version: Audio, screen and instruction checks complete: Access setting fits recipient: Actual channel/link preview checked: Written summary and alternative supplied: One next action requested: Follow-up owner: Customer result or unresolved question: Resource improvement needed:
Common questions
Will every customer watch a video message?
No. Explain its purpose and provide the key answer in an accessible form. If video is unsuitable, continue through another appropriate channel.
Should every answer be a new recording?
No. Use a reviewed library message when it matches the customer’s task and context. Record a new explanation when the existing resource would mislead or omit an important difference.
What if the customer cannot open the link?
Check the actual URL, access setting and recipient route. Provide the written answer or another approved delivery method while the access problem is investigated.
For deciding where video belongs across the wider service journey, use our video customer experience guide.
