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

# Contact Zolt Support — Channels, SLAs, and Bug Reports

> Reach the Zolt support team via live chat, email, or community forum. See response time SLAs by plan and tips for writing an effective bug report.

Zolt's support team is here to help you resolve issues, answer questions, and get the most out of the product. Choose the channel that best fits your situation — whether you need a quick answer right now or want to share a detailed bug report.

## Support Channels

<CardGroup cols={2}>
  <Card title="Live Chat" icon="message">
    Access live chat directly inside the Zolt app by clicking the **chat bubble icon** in the bottom-right corner of any page.

    * **Free plan:** Available during business hours (Mon–Fri, 9 am–6 pm ET)
    * **Pro plan:** Available 24/7
    * **Business plan:** Available 24/7 with priority routing
  </Card>

  <Card title="Email Support" icon="envelope">
    Send an email to **[support@zolt.io](mailto:support@zolt.io)** for non-urgent issues or detailed questions that benefit from a written response.

    For the fastest resolution, include your **workspace name** and a clear description of the issue. See [Providing a Good Bug Report](#providing-a-good-bug-report) below for guidance.
  </Card>

  <Card title="Community Forum" icon="users">
    Visit **[community.zolt.io](https://community.zolt.io)** to connect with other Zolt users, ask questions, share workflows, and find answers to common problems.

    The community forum is monitored by Zolt staff and experienced community members. It's a great place to get input on best practices and feature ideas.
  </Card>

  <Card title="Status Page" icon="signal">
    Before contacting support, check **[status.zolt.io](https://status.zolt.io)** to see if there are any active incidents, degraded services, or scheduled maintenance windows that may be causing your issue.

    You can subscribe to status updates via email or RSS to be notified of incidents automatically.
  </Card>
</CardGroup>

***

## Response Time SLAs

Zolt's first response time commitment depends on your plan. Response times are measured from when your message is received during the applicable support hours.

| Plan     | First Response  |
| -------- | --------------- |
| Free     | 3 business days |
| Pro      | 1 business day  |
| Business | 4 hours         |

<Note>
  For urgent production issues on the **Business plan**, include the word **"URGENT"** in your email subject line (e.g., `URGENT: Webhook delivery completely down`). This triggers the priority support queue and ensures your ticket is escalated immediately to a senior support engineer.
</Note>

***

## Before You Contact Us

Taking a few minutes to check these resources first often resolves the issue faster than waiting for a support reply:

* **Check the FAQ** — Browse the [Frequently Asked Questions](/support/faq) page for answers to the most common questions about accounts, billing, projects, and integrations.
* **Search the documentation** — Use the search bar at the top of this page to find guides, reference articles, and tutorials relevant to your issue.
* **Check the status page** — Visit [status.zolt.io](https://status.zolt.io) to confirm there are no active incidents affecting the feature you're using.
* **Gather your workspace ID** — Find this under **Settings > General**. Including it in your support message allows the team to look up your account without delays.
* **Note your browser and OS** — Record the browser name and version (e.g., Chrome 124) and your operating system (e.g., macOS 14.4). This context is essential for reproducing UI or performance issues.

***

## Providing a Good Bug Report

The more detail you provide, the faster Zolt's support team can reproduce and resolve your issue. When reporting a bug, include the following:

* **Steps to reproduce** — A numbered list of exact actions that consistently trigger the issue, starting from the Zolt dashboard or a specific page.
* **Expected behavior** — Describe what you expected to happen when you followed those steps.
* **Actual behavior** — Describe what actually happened instead, including any error messages you saw.
* **Screenshots or screen recording** — Visual evidence is extremely helpful. Annotate screenshots to highlight the relevant area if needed.
* **Browser and OS version** — For example: Firefox 125 on Windows 11, or Safari 17 on macOS Sonoma.
* **Workspace ID** — Found under **Settings > General**. This lets support pull up your account and logs directly.
* **Frequency and consistency** — Note whether the issue happens every time, intermittently, or only under specific conditions (e.g., only with certain file types or on a specific project).