> For the complete documentation index, see [llms.txt](https://wachatbot.gitbook.io/wachatbot-info-pages/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wachatbot.gitbook.io/wachatbot-info-pages/wachatbots-refund-policy.md).

# WaChatbot's Refund Policy

**Refund Policy for WhatsApp Support Chatbot Development and WhatsApp Marketing SaaS Platform**

**Effective Date: 15/01/2024**

Thank you for choosing our WhatsApp Support Chatbot Development and WhatsApp Marketing SaaS Platform. This Refund Policy outlines the terms and conditions for refunds related to our services. By using our services, you agree to comply with this refund policy.

#### 1. Refund Eligibility:

1.1 **Satisfaction Guarantee:** We strive to ensure your satisfaction with our services. If you are not satisfied with our WhatsApp Support Chatbot Development and WhatsApp Marketing SaaS Platform, you may be eligible for a refund.

1.2 **Criteria for Refund:** Refunds may be considered if there is a substantial failure in the functionality of our services that prevents you from using them effectively.

#### 2. Refund Process:

2.1 **Contact Support:** To request a refund, please contact our customer support team at <ganesh@wachatbot.in> within 5 days from the date of purchase or subscription renewal.

2.2 **Provide Information:** When requesting a refund, please provide detailed information about the issue you encountered and any steps you have taken to address it.

#### 3. Refund Decisions:

3.1 **Evaluation:** Refund requests will be evaluated on a case-by-case basis. We may ask for additional information to assist in the evaluation.

3.2 **Refund Approval:** Refunds will be approved if the issue is confirmed to be a substantial failure in our services, preventing effective use.

3.3 **Refund Denial:** Refunds may be denied if the issue is caused by factors outside our control or if there is evidence of misuse or violation of our terms and conditions.

#### 4. Refund Methods:

4.1 **Payment Reversal:** Refunds, if approved, will be processed using the same method of payment used for the original purchase.

4.2 **Timing:** Refunds may take \[number of days] days to be reflected in your account, depending on the payment method and financial institution.

#### 5. Changes to Refund Policy:

5.1 **Updates:** We reserve the right to update or modify this Refund Policy at any time. Any changes will be effective immediately upon posting the updated policy on our website.

#### 6. Contact Information:

6.1 **Questions:** If you have any questions or concerns about our Refund Policy, please contact us at <ganesh@wachatbot.in>

By using our WhatsApp Support Chatbot Development and WhatsApp Marketing SaaS Platform, you agree to abide by the terms outlined in this Refund Policy.

WaChatbot

Address: 25/4, Yerikarai Road Shivaya Nagar, Reddiyur, Salem, Tamil Nadu - 636004.&#x20;

Phone: 7806997591&#x20;

Email: <ganesh@wachatbot.in>


---

# 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://wachatbot.gitbook.io/wachatbot-info-pages/wachatbots-refund-policy.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.