Support

team@speko.ai 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.

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.

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

If you have found a vulnerability, write to team@speko.ai 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.