> 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/tech/serve.md).

# MaiAgent Serve｜客戶服務整合

- [軟體廠商整合指南：把 AI Agent 嵌給您的客戶](https://docs.maiagent.ai/tech/serve/vendor-integration-guide.md): 軟體廠商將 Web Chat 嵌入自家產品並完成權限對接的端到端指南：嵌入、批次補建、登入同步、Token 刷新與登出註銷
- [Web Chat 嵌入與 SDK](https://docs.maiagent.ai/tech/serve/web-chat-sdk.md): 將 MaiAgent Web Chat 嵌入任何網站：嵌入碼、視窗模式、身分識別、完整配置參考與 JavaScript SDK API
- [MaiGPT 模式嵌入](https://docs.maiagent.ai/tech/serve/web-chat-sdk/web-chat-maigpt-mode.md): 將類 ChatGPT 的 MaiGPT 完整對話介面嵌入您的網站或產品，支援指定容器與漂浮全屏兩種佈局
- [注入頁面 Context](https://docs.maiagent.ai/tech/serve/web-chat-sdk/web-chat-context-data.md): 透過 embed SDK 的 auth.contextData，把頁面 context（如商品 ID、工單編號、使用者識別碼）注入 Agent 的 LLM System Prompt
- [LINE LIFF：什麼是 LINE LIFF](https://docs.maiagent.ai/tech/serve/whatislineliff.md): 什麼是 LINE LIFF（LINE Front-end Framework）：在 LINE 應用程式內嵌入網頁應用的框架，以及 MaiAgent Web Chat 用 LIFF 開啟的好處。
- [LINE LIFF：如何串接](https://docs.maiagent.ai/tech/serve/whatislineliff/setting.md): LINE LIFF 串接步驟：在 LINE Developers 建立 LIFF app、把對話平台公開網址設為 Endpoint URL，讓 Web Chat 在 LINE 聊天視窗內開啟。
- [LINE Flex Message 規格](https://docs.maiagent.ai/tech/serve/line-flex-message.md): MaiAgent 怎麼把 LINE Flex Message 卡片送出去：FlexMessage 工具的模板與 AI 欄位格式、驗證端點、回覆串流中的 flex 項目，以及送到 LINE 時的限制與失敗處理。
- [聯絡人 (Contact) 介紹及串接](https://docs.maiagent.ai/tech/serve/contacts.md): 聯絡人（Contact）介紹及串接：以 sourceId 把自家系統使用者對應到終端使用者，建立與同步聯絡人的四種方式、Excel 批次匯入與實作建議。
- [聯絡人身分同步與 Token 更新](https://docs.maiagent.ai/tech/serve/contacts/contact-credentials-sync.md): 企業系統在新增使用者與每次登入時，透過 setup-contact-credentials 同步聯絡人身分與更新 Token 憑證
- [角色(Role) 和 聯絡人(Contact) 的差異](https://docs.maiagent.ai/tech/serve/contacts/role-vs-contact.md): 內部成員用角色（Role）管理平台權限，外部使用者用聯絡人（Contact）識別身分；完整對照見使用者手冊
- [第三方客服系統串接（含轉真人）](https://docs.maiagent.ai/tech/serve/customer-service-system-integration.md): 客服系統或聊天平台以 API 接入 MaiAgent 當 AI 引擎：訊息進出、AI 判定轉真人時交由您的真人客服接手、結束後回到 AI 的端到端規格
- [Genesys Cloud 整合](https://docs.maiagent.ai/tech/serve/customer-service-system-integration/genesys-cloud-integration.md): 以 Genesys Cloud Open Messaging 串接 MaiAgent 對話平台：架構、OAuth 憑證與 API、訊息雙向流向、簽章驗證、錯誤處理與限制
- [對話交接與接續對話 API](https://docs.maiagent.ai/tech/serve/conversation-handoff-continuation.md): 以交接摘要建立接續對話，並辨識原對話與接續對話的關聯。
- [通話中心外撥 API](https://docs.maiagent.ai/tech/serve/call-center-outbound-api.md): 從外部系統透過通話中心外撥 API，讓號碼綁定的 Agent 撥出電話，並以通話紀錄 API 查詢處理狀態。
- [Webhook](https://docs.maiagent.ai/tech/serve/webhook.md): 對話平台 Webhook：把訪客訊息與 AI／真人回覆即時推送到您的系統，支援 MaiAgent 標準格式、Genesys Cloud 與自訂 Jinja2 範本


---

# 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/tech/serve.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.