> For the complete documentation index, see [llms.txt](https://global-starlink.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://global-starlink.gitbook.io/help/south-east-asia/south-east-asia/south-east-asia-prepaid-travel-esim-card-20gb-30gb-30-days-data-only.md).

# South East Asia Prepaid Travel eSIM Card 20GB/30GB 30 Days (Data Only)

### Plan Overview<br>

* **Data: 20GB/30GB High Speed Data**
* **Speed:** 4G/Lte
* **Calls & Texts:** No Calls and Texts, Data only eSIM
* **Phone Number:** No
* **Coverage:** **Vietnam, Cambodia, Malaysia, Indonesia, Thailand, Singapore**
* **Compatibility:** Unlocked eSIM compatible devices
* **Hotspot/Tethering:** Yes
* **Network:** Multiple Mobile Network
* **Recharges:** No
* **ID Requirement:** None
* **Delivery:** Via email (please allow up to 24 hours)
* **Validity:** Starts on first network connection
* **When to install:** Anytime before your intended travel date
* **Activation:** Scan QR code from email

### **What else is included**<br>

* Digital eSIM profile (QR Code)
* Calls to and from Australia not included. We recommend you using Apps like WhatsApp
* 30 days service options from activation date
* For more data plan options, please contact our customer service

<br>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://global-starlink.gitbook.io/help/south-east-asia/south-east-asia/south-east-asia-prepaid-travel-esim-card-20gb-30gb-30-days-data-only.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 `build a script that syncs our docs to a CMS` 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.