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

# Customer support for your app

> Add a help chat to your app. AI answers your customers from your knowledge base, and you answer the rest from Newly.

Customer support gives your app a help chat. A customer asks a question inside your app, an AI answers within seconds from your **knowledge base** (and that customer's earlier chats), and when it can't help, the chat waits for you. You see and answer every chat in Newly.

Everything lives in **Marketing & analytics**, under **Support**, then **Customer support**. It has four tabs: **Inbox**, **Knowledge base**, **Feedback** and **Setup**.

> [!NOTE]
>
> Customer support is rolling out. If you don't see **Customer support** in Marketing & analytics, it isn't on your account yet.

## Add it to your app

**1. Turn it on**

Open **Setup** and turn on **Support in your app**.

**2. Add the help chat**

Select **Add to my app**. The agent adds a help chat screen styled to match your app, a **Help** entry in Settings, and a few starter articles about what your app does. You can also ask in the chat: *Add customer support to my app*.

**3. Write or import your articles**

Open **Knowledge base** and check the articles. Answers are only as good as these. See [Knowledge base](#knowledge-base).

**4. Try it**

Open your app's preview, go to **Help** and ask a question. The chat appears in your **Inbox** with a **Test** tag.

## How a chat works

1. A customer writes in your app's help chat.
2. If **AI answers** is on, the AI replies in a few seconds, using your articles and that customer's earlier chats. Under the answer, the customer sees which article it came from.
3. When the articles don't cover the question, or the customer asks for a person, the AI hands over: *I'll get the team to look at this. They'll reply here.* The chat shows as **Waiting for you** in your Inbox.
4. You reply from the Inbox. Your reply appears in the customer's chat right away. From then on you have the chat: the AI stays out of it, and the customer's next messages wait for you. To let the AI answer again, choose **Let AI answer** in the chat's **⋮** menu.
5. When the customer says thanks, the AI asks if there's anything else. If they say that's all, the AI says goodbye and marks the chat **Resolved**. You can also select **Resolve** yourself.
6. A resolved chat shows as resolved in your app too, and the customer is asked to rate it. If they write again, a new chat starts.

In your app, **Your chats** lists every chat the customer had, newest first, with its status: **Open**, **Waiting for the team** or **Resolved**. They can open any of them to read it again.

## Inbox

The Inbox lists every chat, newest first, with the customer's first question, their name and where the answer came from. Filter with **All**, **Waiting for you**, **Pending**, **Snoozed** and **Resolved**.

| State | Means | How a chat gets there |
| - | - | - |
| **Open** | Being answered | A new chat, or a new message from the customer while the AI has the chat |
| **Waiting for you** | Your team owes a reply | The AI couldn't answer, AI answers are off or paused, or the customer wrote after your team replied |
| **Pending** | Waiting on the customer | You replied, or chose **Mark as pending** |
| **Snoozed** | Hidden until a time you pick | **Snooze until tomorrow** or **Snooze for a week**. It comes back as Open, or sooner if the customer writes |
| **Resolved** | Done | You selected **Resolve**, the customer said they're done, or it closed after days without a reply |

Your customers only ever see a chat as open or resolved.

* **AI answers switch:** at the top of the Inbox. Turn it off to answer every question yourself. Customers then see *Thanks, the team will reply here soon.*, and no credits are used.
* **Test chats:** chats from development builds (the simulator, a dev client) carry a **Test** tag. Turn on **Hide test chats** to see only chats from your released app.
* **Reply or Private note:** in a chat, switch the composer to **Private note** to leave a note for your team. Notes show in yellow. Customers never see them, and the AI never reads them.
* **Resolve and Reopen:** **Resolve** ends the chat and asks the customer for a rating. **Reopen** lets you reply again.
* **Pending and Snooze:** in a chat, the **⋮** menu has **Mark as pending**, **Snooze until tomorrow** and **Snooze for a week**.
* **Let AI answer:** once you reply in a chat, the AI stops answering it. **Let AI answer** in the **⋮** menu hands it back; if the customer's last message is unanswered, the AI answers it right away. The option shows only while you have the chat, and replying again takes it back.
* **Close inactive chats:** in **Setup**, **Close inactive chats after** (5 days by default) closes chats the customer stopped answering after your team or the AI replied. The customer sees that it closed and can write again any time. Chats waiting for you never close. Set it to 0 to turn this off.
* **Download transcript:** the **⋮** menu in a chat saves it as a text file, including private notes.

Customers who signed in to your app show their name and email. Customers who didn't are marked **not verified**. See [Recognise signed-in customers](#recognise-signed-in-customers).

## Feedback

The **Feedback** tab shows how customers rated their resolved chats: the average out of 5, how many ratings of each score, and the latest rated chats. Each shows whether the AI or your team answered it. Select one to open the chat. Ratings also show on resolved chats in the Inbox.

## Knowledge base

The AI answers only from your knowledge base and the customer's earlier chats. It doesn't invent prices, policies or steps.

* **Add article:** write a title and the answer, in plain text or markdown.
* **Upload PDF:** pick a PDF guide or FAQ. The AI reads it once and saves it as articles you can edit. Each import uses 1 credit.
* **Add from link:** paste the address of a public page, like your help site, FAQ or website. The AI reads it once and saves it as articles. Each import uses 1 credit. Select **Refresh** on those articles to read the page again after it changes.
* **Chat history:** turn off **Chat history** if you don't want the AI to use a customer's earlier chats.

Imported articles show a **PDF** or **Link** badge. You can have up to 200 articles.

### Your articles in your project, and on your website

The agent keeps a copy of your articles in your project, in `support/articles`: one file per article plus one list of them all. If you take your code elsewhere, your articles go with it. Ask the agent *Export my support articles* any time to update the copy.

While **Support in your app** is on, your website's FAQ uses the same articles, so your site and your help chat always give the same answers. Edit an article in **Knowledge base**, then ask the agent to update your website. Edit articles in Newly, not in those files: the next export replaces them.

> [!TIP]
>
> Start with the questions customers ask most: how to get started, your main features, account and sign-in, billing and refunds, and how to reach you.

## AI answers and credits

AI answers use your Newly credits. In **Setup**, under **AI answers**, choose the **Answer quality**:

| Answer quality | Good for | Credits per answer |
| - | - | - |
| **Standard** | Everyday questions | 0.05 |
| **Advanced** | Long or tricky questions, long knowledge bases | 0.1 |

* **Daily AI answer limit:** caps AI answers per day (200 by default, up to 5,000). Past it, questions wait for you until the next day.
* **Out of credits:** AI answers pause. Customers see *Thanks, the team will reply here soon.*, and the Inbox shows a banner. Answers start again as soon as you add credits. See [Out of credits](https://docs.newly.app/billing/out-of-credits.md).
* Your replies, private notes and test chats you answer yourself are free.

**Setup** shows how many AI answers you used this month and what they cost.

## Recognise signed-in customers

If your app has sign-in, the help chat can show who the customer is, and their chats follow them across devices. Open **Setup**, then **Developer settings**, then **Recognise signed-in customers**:

* **Supabase:** ask the agent *Recognise signed-in customers in support*. It passes the customer's sign-in to the chat and gives you the three values to paste here. Only you can save them, because they decide who a customer is.
* **Firebase, Clerk, Auth0 and others:** enter the **Issuer**, **Signing keys URL** and **Audience** from your sign-in provider.
* **Your own server:** select **Create secret key** under keys. Your server uses it to vouch for the signed-in customer. The key is shown once; keep it on your server, never in your app.

Without this, the chat still works. Customers are anonymous on each device.

## Keys

Your app connects to support with a **publishable key**, one for development builds and one for released builds. It's safe to ship inside your app: it only opens your app's help chat. The agent writes both keys into your app when it adds support.

If a key leaks or you want to change it, select **Rotate** in **Developer settings**. The old key stops working right away, so ship an update with the new one.

## FAQ

> [accordion] Do my customers need a Newly account?
>
> No. They use the help chat inside your app. Only you and your team sign in to Newly.

> [accordion] Why don't I see my test messages in the Inbox?
>
> Chats from development builds carry a **Test** tag. If **Hide test chats** is on, turn it off to see them.

> [accordion] How do I make sure my released app uses the right key?
>
> Development builds (simulator, dev client) use the development key. TestFlight, App Store and Google Play builds use the released key. Send a message from your TestFlight build: its chat shows in the Inbox without the **Test** tag.

> [accordion] Can I answer every question myself, without AI?
>
> Yes. Turn off **AI answers** at the top of the Inbox or in **Setup**. Every question then waits for you, and no credits are used.

> [accordion] What does the AI do when it doesn't know the answer?
>
> It doesn't guess. It tells the customer your team will reply, and the chat shows as **Waiting for you**. Add an article for that question so the AI can answer it next time.

> [accordion] Why doesn't the AI answer a chat I replied in?
>
> Once you reply, the chat is yours, so the AI doesn't talk over you. The customer's next messages show as **Waiting for you**. To let the AI take over again, open the chat's **⋮** menu and choose **Let AI answer**.

> [accordion] Why did the AI stop answering?
>
> Usually you're out of credits, you reached the **Daily AI answer limit**, or **AI answers** is off. The Inbox shows a banner for the first two. Customers see that the team will reply.

> [accordion] Why did a link import say there was nothing to add?
>
> The page may be private, need a sign-in, or be mostly images. Use a public page with text, or upload a PDF instead.

> [accordion] Can my customers see private notes?
>
> No. Private notes are only for your team. The AI doesn't read them either.

> [accordion] Do I keep my articles if I move my app's code elsewhere?
>
> Yes. The agent keeps a copy of them in your project, in `support/articles`. Ask *Export my support articles* to update it. PDFs and pages you imported aren't kept, only the articles made from them.

> [accordion] Can my website's FAQ use my support articles?
>
> Yes, while **Support in your app** is on. When the agent builds your website, its FAQ comes from your knowledge base, so it matches what the help chat answers. After you change an article, ask the agent to update your website. With support off, your website shows no FAQ from it.

> [accordion] Can I keep a record of a chat?
>
> Yes. Open the chat, then the **⋮** menu, then **Download transcript**.

> [accordion] Does the AI close chats by itself?
>
> Yes, when the customer is done. After a thank-you it asks whether there's anything else, and when the customer says that's all, it marks the chat **Resolved**. It never closes a chat that's waiting for your team.

> [accordion] Where do I see how customers rated their chats?
>
> In the **Feedback** tab: the average rating, the breakdown and the latest rated chats.

> [accordion] Can my customers see their earlier chats?
>
> Yes. **Your chats** in the help chat lists them with their status. Signed-in customers see the same history on every device.

> [accordion] What's the difference between Pending and Waiting for you?
>
> **Waiting for you** means the customer is owed an answer from your team. **Pending** means you answered and are waiting on the customer. Pending chats close by themselves after the number of days set in **Setup**.

> [accordion] What happens if a customer writes after I resolve a chat?
>
> A new chat starts, and the AI answers it as usual.

> [accordion] Does it work on web builds of my app too?
>
> Yes. The same help chat works in your app's web build.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.