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

# Manual Registration

For manual registration, please follow the below steps:

* Create an account at customized OrgChat URL by providing
  * Name
  * Email
  * Notification channels
    * SMS
    * VoiceMail
    * E-Mails
  * Mobile No. for SMS
  * Mobile No. for VoiceMail
  * Assigned OrgChat Number (have to be given by the organization’s admin)
  * Password
  * Confirm Password

![](/files/-M9cL2ctbLi4EZHw4FNC)

* OrgChat will attempt to verify your email by sending the verification email.
  * Please click on the link in the email and it will generate the validation token.
* Once validated, create
  * Username (depending on availability. This must be unique). The username will be used to tag you in chats and messages.
  * And Display Name (what you want others to see your name tag as). Display name can be similar and exact copy of others. For example, there can be more than one John Doe in the organization.


---

# 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.orgchat.com/registration/manual-registration.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.