# Support - Latchkey

Source: https://latchkey.dev/support

## Send us a message

Fill out the form below and we'll get back to you as soon as possible.

0/5000 characters

More resources

- [Documentation Browse our comprehensive guides and API documentation. View Docs](/documentation)
- [Frequently Asked Questions Find answers to common questions about Latchkey. View FAQ](/faq)
- [Troubleshooting Jobs stuck in queued, an empty dashboard, missing insights, and blocked billing states, each with the check that identifies it. Diagnose an issue](/documentation/troubleshooting)

Before you write to us

## What to include in a support request

Send the run URL, the job name, and what you expected instead. No logs needed — we can read the run.

## When you will hear back

A person reads every message, during UK and US business hours. Blocked builds and billing jump the queue — say so in the first line.

## Things you can answer faster than we can

A stuck job is usually the runner label or the concurrency ceiling; an empty dashboard is usually the filter bar. Troubleshooting covers both.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt