> For the complete documentation index, see [llms.txt](https://docs.ezorderly.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezorderly.com/guide/sheng-ji-yu-fu-kuan/fu-kuan-yu-fa-piao-ji-lu/you-jian-yu-jian-xun-chu-zhi.md).

# 郵件與簡訊儲值

點選左上角縮放功能目錄，最下方的「升級與付款」中，點選「付款與發票紀錄」進入。

![](/files/ARFJarJFlU8IXdOnSBpX)

游標移至儲值金額上方會顯示儲值兌換方案，請選擇您欲儲值的額度，點擊進入。

* 線上儲值 $3,000

  個人版﹔郵件 30,000 封或簡訊 1,500 則。

  團隊版﹔郵件 50,000 封或簡訊 2,000 則。

  企業版﹔郵件 75,000 封或簡訊 3,000 則。
* 線上儲值 $6,000

  個人版﹔郵件 60,000 封或簡訊 3,000 則。

  團隊版﹔郵件 100,000 封或簡訊 4,000 則。

  企業版﹔郵件 150,000 封或簡訊 6,000 則。
* 線上儲值 $12,000

  個人版﹔郵件 120,000 封或簡訊 6,000 則。

  團隊版﹔郵件 200,000 封或簡訊 8,000 則。

  企業版﹔郵件 300,000 封或簡訊 12,000 則。

![](/files/r3uASJnoo7DsVl2cK8CS)

若選擇「線上儲值 $3,000」進入，畫面將跳轉至第三方支付金流平台。

> 完成付款後，請與客服聯繫兌換內容(郵件/簡訊擇一)，點數將於 3 個工作天內匯入系統中，電子發票將於 7 個工作天內開立。

![](/files/fo0PM31d4OCc9Qn9oXpm)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ezorderly.com/guide/sheng-ji-yu-fu-kuan/fu-kuan-yu-fa-piao-ji-lu/you-jian-yu-jian-xun-chu-zhi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.