> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/serve/voicecs.md).

# 應用實例：語音客服

語音客服應用總覽：從語音輸入、ASR 語音辨識到 Agent 處理的流程，涵蓋 IVR 意圖辨識、通話摘要與通話質檢三種應用。

現代語音客服系統結合人工智慧技術，提供多樣化且靈活的解決方案，提升服務效率與客戶體驗。整體流程從 **語音輸入** 開始，透過 **ASR 語音識別** 將客戶語音轉換為文字，接著依據需求可應用多種 Agent 功能，靈活地進行進一步處理。

Agent 涵蓋以下應用：

1. **意圖辨識**：用於解析客戶語音內容，快速了解需求或問題，便於後續處理。
2. **摘要派單**：針對複雜的客戶需求，生成摘要並自動分派至合適的服務部門或系統。
3. **智能質檢**：進行即時的通話監控與分析，確保服務品質符合標準。
4. **智能回覆**：根據意圖辨識結果生成適切的回應內容，並透過 **TTS 文字轉語音** 技術轉化為語音，回覆給客戶。

以上功能的應用可以根據實際需求靈活選用，不一定需要全流程執行，而是針對不同場景與需求進行設計。例如，有些場景可能僅需要意圖辨識，而智能回覆則適用於希望提供即時語音回應的情境。

這些應用模組的結合，構建了一個功能多樣且高度適應性的語音客服生態，實現了更高效且個性化的客戶互動。接下來，將針對各個應用該如何打造 Agent 與 MaiAgent 的解決方案進行詳細介紹，展示其技術核心與應用價值。

```mermaid
flowchart LR
    A[語音輸入] --> B[ASR 語音識別]
    B --> E[意圖辨識]
    B --> X[真人客服助手]
    B --> F[摘要派單]
    B --> G[智能質檢]
    B --> H[智能回覆]
    

    
    subgraph AI 助理
    E
    F
    G
    H
    X
    end
    
    H --> I[TTS 文字轉語音]
    I --> J[語音輸出]
```

MaiAgent 目前已內建整合多種 ASR 語音識別與 TTS 語音合成，方便使用者根據不同場景來選擇合適的技術。

<figure><img src="https://1593648278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmzb5NG9GDzFP2YDKeYVl%2Fuploads%2Fgit-blob-e7ff69b764594e4cbcf903aa16a739d30318a469%2Fimage%20(7)%20(1)%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maiagent.ai/serve/voicecs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
