> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/reference-guide/support-and-contacts.md).

# Support & Contacts

### Support & Contacts

#### Purpose

This section explains how to get help—whether you are integrating for the first time or running live traffic in production. It points you to the right channel, sets expectations for response times, and defines severity levels.

#### Quick-contact table

| Need                                           | Email                                           | Coverage (America/New York) |
| ---------------------------------------------- | ----------------------------------------------- | --------------------------- |
| Technical / production issues                  | [**support@bead.xyz**](mailto:support@bead.xyz) | 24 × 7                      |
| General inquiries (billing, partnership, docs) | [**info@bead.xyz**](mailto:info@bead.xyz)       | Mon – Fri, 09:00 – 18:00    |

#### Severity matrix

| Severity          | Examples                                                | First response target |
| ----------------- | ------------------------------------------------------- | --------------------- |
| **P1 – Critical** | API unavailable, payments failing globally              | 30 min                |
| **P2 – High**     | Single merchant blocked, webhook backlog, major latency | 2 h                   |
| **P3 – Normal**   | Non-blocking bug, documentation clarification           | 1 business day        |
| **P4 – Low**      | Cosmetic issue, enhancement request                     | 2 business days       |

#### Where to go next

* [**Integration Support**](https://developers.bead.xyz/reference-guide/support-and-contacts/integration-support.md) – step-by-step ticket workflow, what details to include, and how we triage issues.
* [**Escalation Contacts**](https://developers.bead.xyz/reference-guide/support-and-contacts/escalation-contacts.md) – severity definitions re-stated with target status-update cadence and (future) phone or pager details.

Use the email addresses above and the severity guidelines to ensure your request reaches the right team with the right urgency.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/reference-guide/support-and-contacts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
