> For the complete documentation index, see [llms.txt](https://docs.yaeris.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yaeris.com/faqs/terms-and-conditions/whatsapp-cloud-blaster.md).

# WhatsApp Cloud Blaster

Please read our terms and conditions before placing an order with us

1. If there is any technical error, we will take 24 - 48 hours to fix it.
2. Our server will service your campaign on best effort basis. The traffic within the server is shared across all of our customers. Your submitted campaign will usually be in the queue.
3. Any technical glitch derived from the software will take 24 - 48 hours to fix it. If the issue is complicated, it will take more than 48 hours.
4. We are not responsible if your WhatsApp account gets blocked. In this case, we are just a software provider.
5. We are not responsible for achieving your expectation/assumption. You are the one who is responsible at the end of the day.
6. We do not have refund policy.

{% hint style="warning" %}
After you have placed the order, it also implies that you have agreed to our Terms & Conditions.
{% endhint %}


---

# 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.yaeris.com/faqs/terms-and-conditions/whatsapp-cloud-blaster.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.