---
title: "Support"
description: "How to reach the Speko team, what to include so we can help on the first reply, and where to check whether something is already known to be down."
canonical: "https://speko.com/support"
last-updated: "2026-08-22"
---

> ## Speko page index
> The complete index of every page on this site is at: https://speko.com/llms.txt
> Read it before exploring further. It lists the exact Markdown URL for every canonical HTML page.

# Support

How to reach the Speko team, what to include so we can help on the first reply, and where to check whether something is already known to be down.

## Email us

[[email protected]](https://speko.com/cdn-cgi/l/email-protection#275342464a675457424c4809464e) reaches the whole team, including the engineers who built the thing you are writing about. It is the right address for everything: a bug, a question about the API, help picking a voice stack, billing, security, or a partnership.

We answer during business hours, Monday to Friday. If something is actively broken in production, say so in the subject line and it gets picked up ahead of the queue.

## What to include

None of this is required, but each one usually saves a round trip:

- **A session or call id.** Almost every question about a call is answerable in one step from its id.
- **The time it happened, with a timezone.** "This morning" is a wide window in our logs.
- **What you expected, and what happened instead.** The gap between those two is the actual report.
- **The exact error.** Pasted verbatim, including the status code, rather than described.

## Before you write

Two places worth a look first, because they answer faster than we can. [status.speko.ai](https://status.speko.ai) shows whether a provider or a Speko service is degraded right now, and [docs.speko.dev](https://docs.speko.dev) carries the API reference, the quickstarts, and the migration guides.

## Security

If you have found a vulnerability, write to [[email protected]](https://speko.com/cdn-cgi/l/email-protection#790d1c1814390a091c1216571810) with "security" in the subject and please give us a chance to fix it before disclosing it publicly. We will confirm receipt and keep you updated through the fix.
