> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/user-documentation/registration-and-personal-settings/registering-your-agilecase-account.md).
# Registering Your AgileCase Account
To begin using AgileCase, you must first create an account. This lesson will show you how to complete your registration and access the system.
{% stepper %}
{% step %}
### Select the "Register" tab
First of all, select the "Register" tab at the top of the page. This will take you to the registration page where you can enter your details.
{% endstep %}
{% step %}
### Enter your account details
On the registration page you must provide: a valid Email address, name, phone number and create a password. Once this is done, click "Register" to create your account.
{% endstep %}
{% step %}
### Get Started
Once you have registered you should receive an introductory email. Click the "Let's Get Started!" link to enable your account. If you don't receive this message please check your Spam folder, if you do not receive an email, please contact us on .
{% endstep %}
{% endstepper %}
---
# 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.agilecase.com/user-documentation/registration-and-personal-settings/registering-your-agilecase-account.md?ask=&goal=
```
`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.