# How Threadly Charges for Active Users

We understand that clear and predictable pricing is important. That's why Threadly's billing is simple: you'll only be charged for the users on your team who actually send messages within your billing period. This covers all their outgoing communication, including messages sent through automated workflows, the main Threadly app, or quick shortcuts.

Learn more about our [Premium plan here](/threadly/admin-and-billing/understanding-threadlys-premium-plan.md).

For a detailed look at which actions contribute to billing, check out the table below:

<table><thead><tr><th>Action</th><th data-type="checkbox">Billed</th></tr></thead><tbody><tr><td>User sends a message via the Threadly app or shortcut.</td><td>true</td></tr><tr><td>User activates a Workflow they created in Threadly.</td><td>true</td></tr><tr><td>User views, interacts, leaves an emoji on a message.</td><td>false</td></tr><tr><td>User opens the Threadly app to view analytics, conversation groups, or settings.</td><td>false</td></tr></tbody></table>

## FAQ:

<details>

<summary>What happens if I have no users sending messages in one month?</summary>

On the Threadly Premium plan, the minimum amount of users is one.

</details>

<details>

<summary>Will Threadly downgrade my bill if the amount of users drops month over month?</summary>

Yes, we will only charge for the users sending messages. Please reach out to us if we can help clarify your bill, or explore a credit, should one be necessary.

</details>


---

# Agent Instructions: 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:

```
GET https://threadly.gitbook.io/threadly/admin-and-billing/how-threadly-charges-for-active-users.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.