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

# Get support

> How to reach the Custral team, and what to send so we can help on the first reply.

## Contact us

<CardGroup cols={2}>
  <Card title="Email" icon="envelope" href="mailto:hello@custral.com">
    **[hello@custral.com](mailto:hello@custral.com)**<br />
    Best for anything that isn't urgent: bugs, questions, billing, feature requests.
  </Card>

  <Card title="Phone" icon="phone" href="tel:+19179245861">
    **+1 (917) 924-5861**<br />
    Monday–Friday, 9:00 AM – 6:00 PM ET.
  </Card>
</CardGroup>

<Info>
  Something broken right now? Check [status.custral.com](https://status.custral.com)
  first, if it's a known incident, it's already being worked on and you don't
  need to write in.
</Info>

## What to include

The single most useful thing you can send is the **request id**. Every Custral
error carries one, and it points us straight at your exact call instead of a
class of similar ones.

<Steps>
  <Step title="Grab the request id">
    It looks like `req_2a1f9c8e7b6d5`. In the app it's shown in the error toast;
    over the API it's the `reqId` field on every response, success or failure.
    See [Requests & responses](/dev/api-reference/requests).
  </Step>

  <Step title="Say which workspace">
    Its name is enough. If you belong to more than one, tell us which. The same
    account can look very different across workspaces.
  </Step>

  <Step title="Say what you expected">
    What you did, what happened, and what you expected instead. A screenshot of
    the screen you were on usually saves a round trip.
  </Step>
</Steps>

<Tip>
  In the app, **Settings → Client Settings → Report a bug** attaches your recent
  in-app logs automatically. It's the fastest way to send us something
  reproducible.
</Tip>

## Try these first

Most issues land in one of these areas, and each has a troubleshooting table of
the symptoms we see most, with the cause and the fix:

<CardGroup cols={2}>
  <Card title="Email" icon="envelope" href="/comms/email/troubleshooting">
    Sync, sending, threading, and connected mailboxes.
  </Card>

  <Card title="Deliverability" icon="shield-check" href="/comms/deliverability/troubleshooting">
    Mail that sends but doesn't arrive: SPF, DKIM, DMARC, reputation.
  </Card>

  <Card title="SMS" icon="comment-sms" href="/comms/sms/troubleshooting">
    Delivery failures, A2P registration, throughput limits.
  </Card>

  <Card title="Voice" icon="phone" href="/comms/voice/troubleshooting">
    Calls, recording, voicemail, and caller ID.
  </Card>

  <Card title="Workflows" icon="bolt" href="/automation/workflows/troubleshooting">
    Automations that don't fire, or fire twice.
  </Card>

  <Card title="Reporting" icon="chart-simple" href="/bi/reporting/troubleshooting">
    Charts that look wrong, empty, or out of date.
  </Card>

  <Card title="AI auto-fill" icon="wand-magic-sparkles" href="/ai/property-agents/troubleshooting">
    Agents that don't run, or fill the wrong value.
  </Card>

  <Card title="Your account" icon="user-gear" href="/start/account/overview">
    Sign-in, two-step verification, sessions, and notifications.
  </Card>
</CardGroup>

## Building on the API

For questions about the REST API, the SDK, the CLI, or MCP, email the same
address and mention that it's a developer question. It routes to the same
place, but the detail we need is different:

* The **endpoint** and method you called.
* The **`reqId`** from the response.
* The error **`code`**. See [Errors](/dev/errors/overview) for the catalog.

If an endpoint you need doesn't exist yet, say so. The `/v1` surface grows from
what people actually ask for.

## Reporting something sensitive

For a suspected security issue, email
[hello@custral.com](mailto:hello@custral.com) with **"Security"** in the subject
and we'll route it straight away. Please don't post details publicly until we've
had a chance to respond.

To delete your account, see [Deleting your account](/start/account/overview#deleting-your-account).
You don't need to contact us for that.


## Related topics

- [Troubleshooting](/dev/webhooks/troubleshooting.md)
- [Assemble a support inbox](/recipes/support-inbox.md)
- [Getting Started](/data/getting-started.md)
- [Introduction](/start/introduction.md)
- [Quick Start](/start/quickstart.md)