> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc/general/ix-hello-create-account.md). # iX Hello: Create Account {% embed url="" %} ## Create an Account in iX Hello 1. To create an account in iX Hello, browse to the “” URL and click “***Sign up now***”.

2. You are directed to a “***Sign up now***” page. Fill in all the form fields.

3. Press "**Send Verification Code**". This will verify your email address. 4. An email with the verification code will be sent to your registered email id. It may land in your junk or spam folders so be sure to check those folders in addition to your inbox.

5. Enter the verification code and characters as below example and click verify code

6. Once clicked on Verify code, you will see a notification, that your email ID is verified. 7. After Email ID is verified, kindly fill in the necessary details and click "**Create**", your iX Hello account will be created and click continue.

8. Once you click continue you will be redirected to the login page, kindly use your email id and newly created password to login.

9. After creating the account and logging in, you will land on the iX Hello screen as shown below:

--- # 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.ixhello.com/ixhc/general/ix-hello-create-account.md?ask=&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.