# ❓Frequently Asked Questions

The FAQs feature is designed to help you provide instant answers to common customer questions directly on your public front page. This not only saves time for your team but also enhances the customer experience by making key information easily accessible.

<figure><img src="/files/Kw6DzXAEL9ftFYmFQMCT" alt=""><figcaption></figcaption></figure>

***

#### 📍 Where Do FAQs Appear?

<br>

All active FAQs are prominently displayed in the middle section of your public-facing homepage, ensuring they are easily visible to site visitors and potential customers.

***

### 🛠️ Management

<br>

You can manage all FAQs from the admin panel.

***

#### ➕ Create a New FAQ

<br>

To add a new FAQ:

1. Enter the question – This will be the visible title (e.g., “How long does a repair take?”)
2. Enter the answer – A detailed response to the question (e.g., “Most repairs are completed within 24–48 hours, depending on part availability.”)
3. Save – Once saved, the FAQ appears live on the public site.

***

#### ✏️ Edit / Update an Existing FAQ

<br>

You can easily:

* Modify the question
* Update the answer content to reflect new policies or procedures
* Save changes, and the updates will instantly appear on the public site

***

#### 🖼️ Frontend Appearance

* FAQs appear in a collapsible accordion layout on the public homepage
* Visitors can click to expand a question and view its answer
* Clean, mobile-friendly design ensures a smooth user experience


---

# 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://codehas.gitbook.io/repair-box/tools/requently-asked-questions.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.