Skip to main content
Getting started

Find help and contact support

Every way to get help in Ottili ONE: documentation, the status page, the Support Center with Support AI, and reaching the team directly.

Overview

When something does not work as expected, or you have a question, there are several ways to get unblocked quickly. Most issues are resolved through the Ottili ONE documentation, the public status page, or the Support Center — and when it is urgent, you can reach the support team directly.

Ottili ONE documentation

The documentation at [docs.ottili.one](https://docs.ottili.one/) is the fastest starting point for explained workflows, concepts, and step-by-step guides. Start with the [Getting Started guide](/docs/getting-started-with-ottili-one), or browse the Getting started* category directly.

If you are unsure what a status badge such as *Beta* or *In development* means, the article [Understand feature status labels](/docs/understand-feature-status-labels) explains how Ottili ONE signals availability.

Check the status page

Before opening a ticket, check the [public status page](https://status.ottili.one/). It shows active incidents, planned maintenance, and the real-time status of individual components. The status page is also a knowledge source for Support AI: if an incident is listed there, the assistant already knows about it.

Support Center and Support AI

In the [Support Center](https://ottili.one/support) you can submit requests and track their progress. The Support AI* assistant is also available there — it answers your questions and suggests relevant articles. Support AI uses the Ottili ONE documentation and the public status page as its knowledge sources.

Support AI complements the human support team; it does not replace it. For complex or privacy-sensitive matters, the team takes over.

Contact us directly

Open a request through the [Support Center](https://ottili.one/support). Have the following details ready so we can help quickly:

  • Your workspace domain* (for example yourcompany.ottili.one)
  • The exact steps* that led to the problem
  • What you expected* versus what you actually saw*
  • Screenshots or error messages, if available

Writing a good bug report

A precise report saves time on both sides:

  • Name the environment:* browser, operating system, or app version.
  • State the time:* when did it happen, and was there a known incident on the status page at that moment?
  • Describe reproducibility:* does it happen always, sometimes, or only once?
  • Mind the company:* if you work across several companies, switch to the correct company using the company switcher in the top bar before testing.

Where to go next

  • [Account and login](/docs/account-and-login) — for sign-in or access problems.
  • [Troubleshooting](/docs/troubleshooting) — the most common issues and how to fix them.
  • [What is Ottili ONE?](/docs/what-is-ottili-one) — a platform overview.

Was this article helpful?