> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/start-here/start-your-onboarding.md).

# Start your onboarding

Book a demo, send us your data, and we'll set you up on a call.

## 1. Book a demo

Forty-five minutes, walking through the app against the way your studio actually runs. Bring whoever else needs to see it.

[Schedule a demo](https://schedulink.io/schedule-demo)

We'll create your account afterwards, so you can log in and look around before we speak again.

## 2. Send us your data

Your accounts and the people at them go in first, because everything else attaches to them. Download the two templates, fill them in, and upload them.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Send us your data →</strong></td><td>Upload your accounts and contacts</td><td><a href="https://tally.so/r/0Qqb6N">https://tally.so/r/0Qqb6N</a></td></tr></tbody></table>

Preparing your data for import explains what goes in every column, and has the same two templates if you'd rather start there.

Most studios need a few days for this. Take the time to get it right, because tidy data now saves an afternoon of corrections later.

## 3. Your setup call

We'll have imported your accounts and contacts beforehand, so the call is spent on the part that actually needs you: how your studio runs, and the templates that reflect it.

Template structure is the thing worth getting right early, which is why we build it together rather than leaving you to guess at it.

## Prefer to set it up yourself?

You can. Sign up, import your own data, and build your templates as you go. Setup overview covers the order to work in, and Preparing your data for import has the templates and the import instructions.

You can start on your own and book a call later if you get stuck.


---

# 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://schedulink.io/help-center/start-here/start-your-onboarding.md?ask=<question>&goal=<user_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.
