> For the complete documentation index, see [llms.txt](https://docs.getkita.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getkita.org/legal-and-support/help-and-support.md).

# Help and support

Kita is used in classrooms, where a problem in the middle of a lesson cannot wait. This page covers the quickest way to get an answer, whatever the question.

Most questions are answered somewhere in this documentation. If yours is not, or a lesson is affected and you need an answer now, contact the support team

### Contact us

|       |                                  |
| ----- | -------------------------------- |
| Phone | +44 (0)2046 529991               |
| Email | <support@getkita.org>            |
| Hours | 9am to 5pm GMT, Monday to Friday |

Calls outside these hours reach voicemail. Leave your name, your school and a number, and the team will call you back.

Emails are answered within one working day. If a lesson is affected, say so in the subject line and it will be picked up sooner.

#### What to include

The more of this you can give, the faster the answer:

* The address of your school's Kita instance.
* What you were trying to do, and what happened instead.
* The name of the course, group or student involved, if it applies to one.
* A screenshot of what you are seeing, including any error message.

If it is easier to show than describe, a short screen recording is welcome.

#### Who to ask first

Some things are set by your school rather than by Kita. Your Kita lead can help with sign-in links, teacher permissions, and which courses are available on your instance.

For anything else, contact the support team directly.

### Knowledge base

Search the documentation using the bar at the top of any page.

These are the guides teachers open most often. Top guides:

* [Setting up a class in Kita](/getting-started/add-your-students-to-kita.md)
* [Migrating from Trinket](/getting-started/migrating-from-trinket.md)
* [Create an assessed activity](/set-up-your-lesson/create-a-code-submission.md)
* [Unsubmit a student's work](/mark-and-give-feedback/unsubmit-a-students-work.md)
* [Supported languages and libraries](/guides/supported-languages-and-libraries.md)

### Webinars and support calls

Webinars run through setting up a class, building a lesson, and marking, with time for questions at the end.

Support calls are for questions specific to your school, such as planning a rollout or moving existing material across.

{% hint style="info" %}
Sessions are being scheduled. Email <support@getkita.org> and the team will arrange a time with you.
{% endhint %}

### Reporting a problem

If Kita is not behaving as the guides describe, email <support@getkita.org> with what you saw and a screenshot.

Security issues should go to the same address, marked as security in the subject line. Please report these privately rather than posting publicly.


---

# 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.getkita.org/legal-and-support/help-and-support.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.
