> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact Kato support

> Send the details our support team needs to investigate an account or product issue.

Email [support@getkato.io](mailto:support@getkato.io) when you cannot resolve an
issue with the guidance in this help center.

## What to include

* The email address on your Kato account.
* Your workspace name.
* The device and browser or app you are using.
* What you expected to happen.
* What happened instead.
* The approximate time the issue occurred.
* A screenshot or short recording when it helps explain the problem.

Do not send passwords, authentication codes, full payment card details, or
other secrets.

## Try a quick isolation check

Before reporting a missing item, confirm the selected workspace and the view's
filters. For a connection problem, check the account and its displayed sync or
authorization status. For an automation, include whether it is published and
live and what its Runs view shows.

These checks help distinguish an item hidden by a view from a save problem, or
an inactive workflow from an action that failed during execution. You do not
need to diagnose the cause before contacting us.

## Use this report template

```text theme={null}
Workspace:
Account email:
Page or item link:
Device and browser/app:
Time of issue, including timezone:

What I was trying to do:
Steps I took:
1.
2.
3.

Expected result:
Actual result and exact error text:
Does it happen every time, or only sometimes?
Checks already tried:
```

Use one representative example. A task link and the time it failed to save are
usually more actionable than a screenshot of a whole workspace with no explanation.
If the problem happens only with one item, say so.

## Share useful screenshots

Capture the control or error that explains the issue, with enough surrounding
context to identify the page. Redact unrelated client information. Do not
include API keys, access tokens, passwords, sign-in codes, or payment card details.

For API issues, include the method, route, status code, and a redacted example
request and response. Remove the Authorization header value. For billing
questions, use [billing support](/documentation/billing-and-plans#get-billing-help)
and include the invoice reference rather than payment credentials.

## Account access

If you cannot sign in, contact us from the email address associated with your
account whenever possible. We may ask for additional information to verify the
request before making account changes.


## Related topics

- [Use Ask Kato](/documentation/use-ask-kato.md)
- [Gmail and Outlook](/integrations/email-and-calendar.md)
- [Google Docs](/integrations/google-docs.md)
- [Design useful attributes](/documentation/data/attributes.md)
- [Organize tasks](/documentation/organize-tasks.md)