> For the complete documentation index, see [llms.txt](https://docs.efento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efento.io/efento-cloud/advanced/organization-settings/topping-up-the-sms-phone-call-pool.md).

# Topping Up the SMS / Phone Call Pool

To send SMS or phone call notifications, your organization must have an available pool of messages and calls. You can view the current balance in **Organization Settings**.

To increase the pool:

1. Purchase an SMS / phone call package from Efento.
2. In **Organization Settings**, click the **Add +** button next to the **Available SMS / Phone Calls** field.
3. Enter the activation code you received with your purchase and click **Next**.
4. Verify that the number of added SMS / phone call credits matches your purchase. If the values are correct, confirm and save the changes.

If the code is valid, the number of available SMS messages and phone calls will be increased according to the purchased package.


---

# 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://docs.efento.io/efento-cloud/advanced/organization-settings/topping-up-the-sms-phone-call-pool.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.
