QUICK ANSWER
To collect a useful customer bug recording, send a request that explains what to demonstrate, how to record safely, and what happens after submission. In Clipy, a workspace owner creates a reusable request link. The customer records the problem and submits it, and the recording lands in your Requests inbox with its evidence.
- Ask for the starting state, the steps, the expected result and the actual result.
- Customers open the link and record the problem.
- Every submission lands in your Requests inbox with its AREC evidence, and its share link works for your whole team.
- Turn the submitted recording into a clear engineering handoff instead of forwarding an unexplained link.
A customer writes “checkout is broken.” Support asks which page. The customer sends a screenshot. Engineering asks what happened before the screenshot. A day later, everyone has more messages and nobody has a reproducible issue.
A recording request helps when it collects the missing sequence. The request itself matters as much as the capture tool: a vague “send us a video” can produce a long recording that still omits the starting state or expected behavior. This guide shows how to ask a better question, use Clipy’s request-link flow and deliver a report someone can act on.
When should you ask a customer for a recording?
Ask when timing, several actions or a changing screen state is essential to understanding the problem. A menu that closes before a click, a form that loses entered text, or a flow that fails only after navigation is hard to communicate with one still image.
Do not make a recording a requirement for every support question. A billing question may need an account detail sent through an appropriate private channel. A single misplaced label may need one screenshot. An intermittent issue the customer cannot safely reproduce may need a written description first.
Explain why the recording would help. “Could you show the steps from opening the cart to the error?” is easier to answer than “Please provide more information.” Give the customer a bounded task and tell them what they can omit.
Use a recording request to reduce ambiguity, not to transfer all investigation work to the customer. Support should still review the account context already available to the team and avoid asking the person to repeat information they have provided.
What does a Clipy request link do?
A request link gives a recipient a named task and recording instructions. The recipient creates a Clipy recording and submits it to the requesting workspace. The recording lives in the customer’s Clipy library, and your workspace receives it in its Requests inbox with its AREC evidence.
The link is reusable, so one carefully written request can collect several reports for the same workflow. A request for “show the checkout problem” can be reused while that investigation remains open. A request for an unrelated onboarding issue should have its own name and instructions.
The request link and the submitted video link are different. The first invites a recording; the second opens a particular recording. Keep that distinction clear when you copy links into support tickets. Sending the intake link to an engineer does not identify which customer submission they should inspect.
The live Requests page has separate Request links and Inbox tabs. That separation is useful operationally: the request describes what you are collecting, while the inbox is where you review what arrived.
What should you know before creating a request?
Workspace owners manage request links and inbound submissions from the Requests page.
Customers record from the link. They record the problem, and it lands in your Requests inbox with its evidence.
The share link works for your whole team. Each submission lands in your Requests inbox with its AREC evidence. For regulated data, use Clipy Enterprise with its signed BAA. The request page also explains that the recipient’s name and email are visible to the requesting workspace after submission.
New Clipy accounts start with a 7-day free trial, no card needed, and Pro keeps you recording after the trial. Review current plans when this matters to your workflow.
How do you create a request link in Clipy?
- Open Requests. Choose the relevant owned workspace if you have more than one.
- Stay on the Request links tab. Find the “Create a request link” form.
- Enter a Request name. Use the customer’s task or the affected workflow, such as “Show the mobile checkout issue.” Avoid internal shorthand that the recipient will not understand.
- Complete “What should they demonstrate?” Specify where to start, what actions to show and what to explain.
- Select Create link. The request appears under Reusable links.
- Copy the link. Send it with a short explanation of why you need the recording and what the recipient should avoid capturing.
Check the instructions before sending. A request is not improved by adding every possible diagnostic question. Choose the minimum context needed to reproduce the particular problem. Leave a place for uncertainty: the customer may not know which version changed or why a failure occurs.
Do not include private customer details in the request name or instructions. The request page is reached through a shareable link. “Checkout issue after selecting delivery” is usually a better title than one containing a customer’s email, order number or account information.
What should a good recording request say?
Use this template as a starting point. Replace the bracketed text before sending it. It is a sample request, not a transcript from a customer.
Please show us the problem with [workflow]. Start at [safe starting page], then repeat the steps that lead to [symptom]. Tell us what you expected to happen and what happened instead.
Please narrate the actions that matter and pause briefly on the result. You do not need to record the whole session. If you know your browser and device version, include them in your message.
Anyone with the video link can watch the recording, and your name and email will be visible to our workspace when you submit. Do not capture passwords, payment data or unrelated private information. If you cannot reproduce it safely, tell us and we will find another way to investigate.
The final sentence is important. A customer should not repeat a destructive action, expose sensitive information or make another purchase simply to satisfy a request for video. Ask for a safe equivalent or investigate through an appropriate private channel.
For an intermittent issue, ask the customer to show what they can observe without claiming that a successful attempt disproves the original report. “It happened once yesterday and did not happen in this recording” is still useful information.
What does the customer do after opening the link?
The request page shows the workspace’s request name and instructions.
The customer chooses what to capture through the recording flow, demonstrates the problem and stops recording. They should wait for upload and processing rather than closing the page as soon as capture ends. When the recording is ready, the flow lets them review and send it to the workspace.
Recording and submitting are different actions. A customer who made a video but did not complete the submission has not necessarily delivered it to your inbox. In your message, say “review and submit the recording” rather than only “record a video.”
What should the customer capture?
A short, complete sequence is more useful than a long tour of the product. The exact duration should follow the task; there is no magic number of seconds that makes a report good.
| Include | Why it helps |
|---|---|
| Starting page and relevant state | Engineering can begin from the same conditions |
| Actions leading to the failure | The order may explain why the issue occurs |
| Expected behavior, spoken plainly | The recipient can distinguish a bug from a misunderstood workflow |
| Actual visible result | The report has an observable outcome |
| A brief pause on the error or affected element | The reviewer can inspect the relevant state |
| Known environment details in the accompanying message | The team does not have to infer hidden configuration from pixels |
Ask the customer to move unrelated windows away, close sensitive tabs and use safe sample data. They do not need to open browser developer tools: when the customer records with the Clipy Chrome extension, console logs and network requests are captured alongside the video.
If you need a specific error message, ask them to pause while it is visible. If the bug is about a transition, ask them to show the transition rather than only the final screen. If it is a design preference, ask for the desired result so the team is not guessing what “make this better” means.
How should support review the submission?
Open the Inbox tab for the relevant workspace. Start by checking that the recording answers the request: correct workflow, visible symptom and understandable expected behavior. Do not immediately forward every submission to engineering without reading it.
Separate three kinds of information. First, what the recording visibly demonstrates. Second, what the customer says happened outside the recording. Third, what the team suspects may explain the problem. Mixing these together turns a useful report into an unsupported diagnosis.
If something essential is missing, ask one focused follow-up. “Which delivery option was selected before this started?” is more useful than “Can you send more details?” Do not request a complete second recording when a short clarification will answer the question.
Keep the submitted video associated with the support conversation or issue that prompted it. A reusable request link may receive reports from several people; the report handed to engineering should identify the relevant submission and timestamp, not just the intake category.
How do you turn the recording into a bug report?
Use the recording as evidence for a compact written report. The written report helps an engineer decide what to inspect; the recording preserves the sequence and screen state behind it.
Title:
Relevant environment:
Starting state:
Steps to reproduce:
Expected result:
Actual result:
Frequency reported by the customer:
Recording link and useful timestamp:
Open questions:
Next verification step:Here is a sample handoff for a hypothetical checkout issue. It is an example of report structure, not a claim about a real customer or a measured Clipy outcome.
| Field | Sample report |
|---|---|
| Title | Delivery menu covers Continue on narrow checkout layout |
| Starting state | Checkout page with a safe sample address entered |
| Steps | Open delivery options; choose the last option; try to continue |
| Expected | The selected option is applied and Continue remains reachable |
| Actual | The open menu obscures the button in the recorded viewport |
| Open question | Whether the same problem occurs on other viewport widths or browsers |
| Next check | Reproduce at the reported width, then check keyboard access and a wider layout |
Do not invent a browser version, device model or request status if it was not supplied. Do not turn “the button did not respond in this attempt” into “the API is down” without evidence. These distinctions help the engineer choose the right first test.
For a fuller writing reference, use how to write a bug report. For the QA perspective, see the recording-to-repro handoff.
How can Claude Code or Cursor use the submitted recording?
The human-readable video and the agent handoff serve different reviewers. A person watches the sequence. A configured coding agent can use the available recording context to inspect the task. Set up the Clipy integration for the agent you use, then provide the normal recording link and the task.
Begin with understanding, not an immediate code change. Ask the agent to describe what is observable, list the expected behavior and identify missing information. Check that response against the recording before asking it to implement a fix.
Read this recording and the report below. Summarize the steps that are supported by the evidence, distinguish the expected and actual behavior, and list anything missing. Do not infer hidden state. Once we agree on the reproduction, inspect the relevant code and propose the smallest fix with a verification plan.
The recording’s AREC document states what the recording captured, so the agent works from that evidence and asks you about anything else it needs.
Use the Claude Code bug guide for a focused debugging handoff or the Cursor design-feedback guide when the request concerns a desired visual change.
Can the same request flow collect client design feedback?
Yes, but change the instructions. A bug request asks what failed. A design-feedback request asks what should change and why. Reusing bug language for a subjective revision can make the client feel that they need to prove something is broken before asking for an improvement.
For a website revision, ask the client to identify the page, point to the element, describe the desired result and explain any constraint that matters. Encourage them to group related changes and say which are essential. Avoid a long undifferentiated tour of preferences.
The implementer should turn the response into a brief with acceptance criteria and open questions. “Make the hero smaller” may refer to height, type size, spacing or image scale. Confirm the intended change before treating the recording as a complete specification.
The client-feedback-to-implementation-brief guide covers that next step. If one static screenshot communicates the entire change, use that instead; this comparison helps choose the right format.
What happens when a request is paused or revoked?
Pausing is useful when an investigation is temporarily closed or the team cannot process additional responses. Revoking makes a request unavailable. Use the appropriate state deliberately, and update any support macros or help-center links that still point to a request you no longer accept.
When an old link no longer accepts recordings, send the customer a current request.
How do you know the workflow is helping?
Count completed, useful handoffs rather than copied links. A request can be created and never receive a submission. A submission can arrive but omit the reproduction. A recording can be watched without producing an actionable issue.
Review whether the customer completed submission, whether support could describe the issue accurately, whether engineering could reproduce it and whether another clarification was necessary. Compare similar cases before drawing conclusions about speed. Do not attribute a shorter resolution time to the recorder if the bugs were different in complexity.
The most useful qualitative question is: “What did this recording tell us that the original message did not?” If the answer is consistently nothing, improve the request instructions. If it preserves an otherwise missing sequence, keep that example as a model for future requests.
What else should customers and requesters know?
How does a customer respond to a request?
They open the link, record the problem and submit it. The recording lands in your Requests inbox with its evidence.
Who can watch a request recording?
Anyone with the video link can watch it, no signup needed, and the workspace receives each one in its Requests inbox with its AREC evidence. For regulated or health data, use the Enterprise plan with its signed BAA.
Should every request be sent to a coding agent?
No. Some reports need a support answer, a configuration check or a product decision. Use an agent when there is a clear task, appropriate access and enough evidence to proceed.
Collect a clearer report. Open Request a Clipy as a workspace owner, write a specific request, and check the recipient experience before sending it. If you are recording the issue yourself, start with the bug report recorder.