# Bug Reporting

## Bug Reporting Instruction

This documentation helps all new clients provide bug information correctly so that our team can resolve issues quickly.

***

## What is the purpose?

At the very first stage of interacting with a customer, it is essential to collect accurate information about potential bugs. This enables:

* Quick identification of the problem
* Timely updates/fixes
* Stable and uninterrupted service operation

***

## What information do we request about a bug?

When you discover a bug, please provide us with the following details:

#### 1. A brief description of the problem

What is not working?

#### 2. Where does the problem occur?

Please provide:

* The page URL (if available)
* Which browser/device is being used
* Operating system (e.g., Windows, MacOS, iOS, Android)

#### 3. Steps to Reproduce the Bug (Step‑by‑Step)

For example:

* I go to the Dashboard
* Click **Add Widget**
* Click **Save**
* The changes are not saved

#### **4.** Screenshots or Videos

To better understand the bug, it is recommended to provide:

* Screenshot
* Screen recording (e.g., Loom, OBS, or your phone’s camera)

This helps us understand exactly what is happening.

#### 5. How to Submit This Information?

Please send all the details listed in points 1–4 to the following email: [**hello@livecaller.io**](mailto:hello@livecaller.io)

***

## What happens next?

Our technical team will:

* Review the information you provided
* Reproduce the issue
* Fix the problem or get back to you with questions for additional information
* Keep you updated on the status until the issue is resolved


---

# 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.livecaller.io/livecaller/onboarding/bug-reporting.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.