# Recording links

### What are Recording Links?

> Recording links are the screen recording URLs that you can instantly generate from the BetterBugs.io dashboard and share with your customers to collect feedback as screen recording sessions.&#x20;

Your customers can paste the recording link in their browser that enables them record their screen to capture bugs or issues that they’re facing.&#x20;

After screen recording, the customer can add:

* **Email\*** -> User email.
* **Title** -> Concise title (e.g., Payment Issue, Can't Add Items to the Cart, or any others)
* **Description** -> A quick summary of what went wrong.&#x20;

The customer can instantly **submit the bug report/feedback that directly lands in your BetterBugs.io Project!**

**The best part?**&#x20;

> Customers DO NOT have to download or install anything to use recording links, and it works on all desktop browsers! They can just paste the recording link in their browser, record the screen on which they are facing issues, submit, and voilà!&#x20;

{% hint style="success" %}
Both technical and non-technical users can easily use it without any hassles or setup.
{% endhint %}

It’s perfect for you to get the:

* Screen recording of the issue.
* Full context of what went wrong.
* Technical details of issues directly from end users and customers.&#x20;

You and your team can use the report for debugging purposes.

<a href="/pages/l3NsHT0qU5vKZmRa28A2" class="button primary">Start using recording links</a>

### How does the Recording Link Work in BetterBugs.io: Step-by-Step Process Breakdown&#x20;

{% hint style="success" %}
No downloads or installations are required for your customers to use recording links.&#x20;
{% endhint %}

1. **Create** **a new recording link** for a project from your BetterBugs.io dashboard.
2. **Share the URL** with your users *via* email, support chat, or any customer support software that you might be using, such as Zendesk, Intercom, Hiver, or any others.
3. The customer/end-user can: Paste the link in any web browser **->** Screen record the issue **->** Add other details -> Submit.

The submitted report gets added to your BetterBugs.io project. You can access the complete report, analyze it, and work on the next steps.

### What are the Key Benefits of Recording Links: Use Cases

You can use the BetterBugs.io recording links in your software development, QA, and customer support workflows, such as for getting:

* **Screen recording from customers**: Getting visual bug reports directly from your end users.
* **Technical details:** Getting technical information (environment, console logs, network requests) about the issues.&#x20;
* **Full context:** Getting complete context, visuals, and technical information of issues (for debugging) from external users.
* **Specific scenarios:** Developers can get info about the specific scenarios, setups, or environments in which an issue occurs.
* **Issue repro steps:** You can trace the exact steps that triggered an issue.
* **QA overall:** Quality assurance teams can use it to share visual feedback and technical information with other team members during software testing procedures.

### How does Recording Links Improve Your Customer Support Services and Feedback Processes?

1. **No extra steps or downloads are required for end users** — Users can start recording right off the bat by opening the link and hitting the “**Start the recording**” button.
2. **Easy to use and intuitive interface** — After recording the bug, the reporter can add their email, provide a title, and describe the issue.
3. **Quick sharing** — Users can then “**Submit the bug**” to send the visual recording as a bug report back to you for debugging purposes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.betterbugs.io/product-features/recording-links.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.