# Help center assistant (/en/docs/solutions/help-center-assistant)



Let customers ask questions in your help center and find answers in your published material. You maintain the help content, brand and customer contact channels.

## Who this is for [#who-this-is-for]

This solution is for businesses with product documentation, frequently asked questions or support policies, and developers maintaining those sites. Prepare reviewed material that can be made public, a page you can modify and a backend that can establish visitor identity.

Start with a clearly defined subject, such as delivery, returns or membership. A small collection can go directly into the assistant's instructions; evaluate knowledge retrieval separately when the collection grows. This demo answers from a fixed FAQ. It does not promise to crawl your site or keep material up to date automatically.

## What customers can do [#what-customers-can-do]

* **Ask on the original page.** Customers click a search entry point or use the page's keyboard shortcut to open a conversation without moving to another chat product.
* **Get answers from published content.** Turn frequently asked questions into a conversation where customers can follow up on the same topic.
* **Find help beyond the material.** If discounts, timings or service commitments are absent from the source, direct customers to your support contact for confirmation rather than guessing.

This assistant explains help content. Knowing the return policy does not give it permission to read orders or issue refunds. If you later need account-specific data, connect authorized tools for those business actions and verify them separately.

## Solution components [#solution-components]

| Service need                           | Integration guide                                                    |
| -------------------------------------- | -------------------------------------------------------------------- |
| Define answer sources and boundaries   | [Service agents](/en/docs/developers/agent)                          |
| Open a conversation on the site        | [Docs Q\&A recipe](/en/docs/cookbook/scenarios/docs-qa-assistant)    |
| Choose a modal or embedded experience  | [Embedding methods](/en/docs/developers/agent/embed/overview)        |
| Distinguish visitors and conversations | [Embed tokens and end users](/en/docs/developers/agent/embed/tokens) |
| Inspect conversations and usage        | [Operations](/en/docs/developers/agent/monitor)                      |

## Launch the solution [#launch-the-solution]

1. Follow the [agent quickstart](/en/docs/developers/agent/quickstart). Prepare public material and a support contact. Check trial answers against the source before adding the assistant to your site.
2. Follow the [docs Q\&A recipe](/en/docs/cookbook/scenarios/docs-qa-assistant) for the window and entry point. Use existing login identity where available. For visitors, have your backend establish a stable, separate identity for each person.
3. Follow [embedding security](/en/docs/developers/agent/embed/security) to check allowed website origins and backend credential storage. The demo's shared guest identity is for demonstration; do not copy it as the identity design for your live site.
4. Test known and unknown questions, closing and reopening the window, different visitors' conversations and loading failures. Keep the original help articles and support contact available so customers can still get help if chat is unavailable.

**Give this to your agent:**

```text
Add Q&A to my help center. Read /en/docs/solutions/help-center-assistant on this site and follow its integration links.
Confirm the help-center URL, approved public material, agent, login or visitor identity design and human support contact. Configure credentials only on the backend.
Done means: the entry point opens working chat; known answers match the source; unknown answers do not invent policy; visitors' conversations are isolated; failures leave articles and human support accessible.
Deliver verification records and instructions for disabling the Q&A entry point.
```

## Cost estimate [#cost-estimate]

Cost estimate pending. [Public pricing](/en/docs/developers/account/pricing) and the [model catalog](/en/docs/developers/model/catalog) alone do not establish the cost of the complete service. Record question volume, average turns, source length and actual model usage during the trial. If you later add knowledge retrieval, account for its costs separately.

## Demo [#demo]

Open the [Good Finds help center](https://praxis-kit-demo-develop.jshansince93.workers.dev/help). Click the search entry or press ⌘K, or Ctrl+K on Windows and Linux. Ask “如何申请退货？” (“How do I request a return?”), then ask for a specific refund time absent from the material.

Compare answers with the FAQ on the page: known rules should match, while missing commitments should lead to customer support. The example uses store policies; replace them with your own help content when integrating your product.

## Next step [#next-step]

Start with the [docs Q\&A recipe](/en/docs/cookbook/scenarios/docs-qa-assistant). For customer order lookup or return requests, continue with the [ecommerce support solution](/en/docs/solutions/ecommerce-support) and add authorization and verification for each new action.