> 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/contact.md).

# Contact

Ask the assistant, check the common problems, or talk to a human.

Start at the top. Most questions are answered in seconds without waiting for anyone.

## 1. Ask the assistant

The same assistant is in two places. **In Schedulink**, click the icon at the bottom right of any page. **On this site**, press ⌘K on a Mac or Ctrl K on Windows.

Either way, ask a full question and it answers from these guides, with a link to the page it used.

Things people ask:

* Does every task need a template?
* How do I add the school name to an email?
* Why didn't my email send?
* My employee can't see their tasks

Everyone at your studio can use it, photographers and front desk included.

## 2. Check the common problems

If something isn't working, it's usually a permission that's switched off, a subscription that's lapsed, or a sign-up link that's expired.

<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>When something's wrong</strong></td><td>Every known failure, by what you're seeing.</td><td></td></tr></tbody></table>

## 3. Email us

Still stuck, or found a bug? [Send us an email](mailto:seenu@schedulink.io) and we'll come back to you. Include the account or event name if you can, it saves a round trip.

## 4. Book a call

Setting up for the season, or want a walkthrough of something new? Grab 45 minutes.

{% embed url="<https://cal.com/seenuyellapu/45min>" %}
Book 45 minutes with Seenu
{% endembed %}


---

# 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/contact.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.
