> For the complete documentation index, see [llms.txt](https://help.chatlyai.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.chatlyai.app/frequently-asked-questions/subscription/subscription-management.md).

# Subscription Management

I mistakenly selected the quarterly plan instead of the monthly one, and I was surprised by the charge. I would like to kindly request to change my subscription to the monthly plan.

#### How to Downgrade Your Subscription

1. **Go to “Manage Subscriptions”**
   * Log in to your Chatly account.
   * Navigate to Manage Subscriptions from profile menu options.
2. **Check Your Current Plan**
   * Review your existing subscription details.
3. **Select a Lower-Tier Plan**
   * Choose the plan that best fits your usage, and click on "Switch" under that plan.
4. **Review Billing Adjustments**
   * Confirm the adjustments that will take effect once the current billing cycle ends.&#x20;
5. **Confirm the Downgrade**
   * Submit the change. Your new plan will begin with the next billing period.

#### **Note:**&#x20;

* Downgrades are applied at the start of the next billing cycle.
* Your current plan remains active until the billing period ends.


---

# 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://help.chatlyai.app/frequently-asked-questions/subscription/subscription-management.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.
