> ## Documentation Index
> Fetch the complete documentation index at: https://support.callin.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Create and manage the frequently asked questions your sub-accounts will see inside your white-label app.

## What this section is for

**FAQs** is where you write the most common questions your customers ask—and the answers you want them to see instantly inside your app.

This is especially useful in a white-label setup, because it helps you:

* Reduce repetitive support tickets.
* Set clear expectations about billing and usage.
* Explain how your plans work in simple language.

> **Important:** Sub-accounts won’t see Callin’s official documentation here. This FAQ section is for **your own** customer-facing answers.

[Click here to open FAQs](https://app.callin.io/cms/faqs)

<div style={{ border:"2px solid #e5e7eb", borderRadius:"12px", padding:"8px", boxShadow:"0 4px 12px rgba(0,0,0,0.10)", maxWidth:"100%", overflow:"hidden", backgroundColor:"#0b0b0b", marginBottom:"0.75rem" }}>
  <img src="https://mintcdn.com/lechusai/bDwr0EG7umzxl6rN/images/faqs1.png?fit=max&auto=format&n=bDwr0EG7umzxl6rN&q=85&s=438a2447ad5567044210596a45dbe34e" alt="FAQs page showing a search bar, a list of questions, an Active status badge per item, and an Add FAQ button." style={{ width:"100%", display:"block" }} width="1903" height="856" data-path="images/faqs1.png" />
</div>

<p style={{ marginTop:"0", marginBottom:"1.5rem", color:"#6b7280", fontSize:"0.95rem" }}>
  Screenshot: the FAQs list where you can add new questions, search existing ones, and manage which FAQs are active.
</p>

## How FAQs work

Each FAQ is made of:

* **A question** (what the user reads)
* **An answer** (your official explanation)
* An **Active** toggle/status (so you can show or hide it)

When an FAQ is active, it can be shown to your sub-accounts inside the app (exact placement can vary depending on your setup).

> **Tip:** Keep answers short and direct. If a topic is long, link to your documentation in the **Guides** section instead.

## Add a new FAQ

1. Click **Add FAQ**.
2. Fill in:
   * **Question**: write it exactly like a user would ask it.
   * **Answer**: give a clear, friendly answer in 3–6 lines.
3. Leave it as **Active** if you want it visible immediately.
4. Click **Save**.

> **Common mistake:** Writing answers like internal notes. FAQs should be customer-friendly and avoid technical jargon.

## Examples you can copy and adapt

Below are realistic FAQ examples (with sample answers) you can use as a starting point.

### Example 1: Plan upgrades

**Question:** Can I upgrade my plan anytime?\
**Answer:** Yes. You can upgrade at any time. The new plan will apply to your next billing cycle. If anything changes immediately in your account, you’ll see it reflected right away.

### Example 2: Buying extra minutes

**Question:** Can I purchase extra minutes?\
**Answer:** If your plan allows additional minutes, you can buy extra minutes once you reach your included limit. The extra minutes are charged at the rate defined in your plan.

### Example 3: Unused minutes

**Question:** Do unused minutes carry over to the next month?\
**Answer:** In most cases, unused minutes do not roll over. Your monthly minutes reset at the start of each billing cycle. (This can vary depending on your plan rules.)

### Example 4: Payment issues

**Question:** My payment failed—what happens now?\
**Answer:** If a payment fails, your subscription may move into a payment-due state until the issue is resolved. Update your payment method and try again. If you need help, contact support.

> **Important:** If you mention rules like rollover or grace periods, make sure they match how your billing is configured.

## Managing existing FAQs

From the FAQs list you can typically:

* **Search** for a question using the search bar.
* **Activate/Deactivate** an FAQ to show or hide it.
* **Edit** a question/answer if your policies change.

> **Tip:** Review your FAQs once a month. The best FAQs evolve based on what your support team gets asked the most.