> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/contacting-support.md).

# Contacting support 🆘

If there's ever a problem, a user should know how to get help. Then when they try to get that help, they should know exactly what kind of communication they're receiving.

* [ ] Show a link to contact support

  This can be placed in a number of areas, such as:

  * footer in a website
  * settings in a mobile app
  * a page experiencing an error

  Use clear copy and easy to recognize visuals to highlight the link.
* [ ] Show methods of contact

  If you have one option, showcase it! If you have multiple options (chat, call, FAQ), list them out and represent each of their benefits.

  Chat is great for a specific, complicated issue that needs an instant response. On the other hand, FAQ is great for standard questions that are easy to explain.
* [ ] Represent how to communicate and what is expected

  Once a method is chosen, make it clear on how the method will work.

  Illustrate the response time, and what the user will need to provide to receive support.


---

# 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:

```
GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/contacting-support.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.