> For the complete documentation index, see [llms.txt](https://docs.smartbotpro.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smartbotpro.io/scripts/variables/global-variables.md).

# Global variables

{% hint style="info" %}
**Global variables** store the same value for all users&#x20;
{% endhint %}

For example, you have created a global variable %number\_of\_orders% and you want to store in it the number of users who have left a request for your product.&#x20;

In such a case, at the end of the ticket collection script, you can add a "set variable" step that will add one to the %number\_of\_tickets% variable.&#x20;

So you can store exactly the total number of applications: each new one will be taken into account. The bot will increment the same variable regardless of which user it is chatting with. For such purposes, a global variable is great.&#x20;

And with the help of a global array variable, you can distribute limited promotional codes.


---

# 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.smartbotpro.io/scripts/variables/global-variables.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.
