> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/intents-connect/integration-best-practices/handling-support-cases.md).

# Handling Support Cases

We have a streamlined process for handling support requests from integrators and their end users.

The goal is to keep user cases in a single support pipeline, ensure the support team has the information needed to investigate, and prevent cases from being lost across chats or other communication channels.

### How to report an issue

All user support cases should be submitted through the Intents Support form:

[**https://aurora.dev/intents-support**](https://aurora.dev/intents-support)

Submitting the form creates a support case that is reviewed by the relevant teams.

Please use the form for individual user issues rather than sending cases directly to team members.

### What information to include

Provide as much information as possible when submitting a case. Complete reports are significantly easier to investigate and usually require fewer follow-up questions.

Include:

* **Transaction hash(es)** for the affected transaction
* **Deposit address**

As well as any additional information, if it's available:

* **Error message** shown to the user
* A description of **what the user expected to happen**
* A description of **what actually happened**
* Any other identifiers or technical details that may help trace the issue

Do not include private keys, seed phrases, passwords, or other credentials.

### Example of a useful report

**Issue:** User deposited funds but hasn't received them on the destination chain after some time.

> **Transaction hash:** `0x...` \
> **Deposit address:** `0x...`\
> **Route:** Base USDC → Ethereum ETH\
> **Amount:** 100 USDC
>
> User has not yet received the funds on the destination chain, even after waiting for 1 hour. The deposit seems to be stuck in the deposit address.

This level of detail gives the support team enough information to begin investigating the case immediately.

### What happens after submission

1. The report is submitted through the Intents Support form.
2. A support case is created.
3. The support team reviews the case and the information provided.
4. The issue is investigated and, when needed, routed to the appropriate team.
5. Updates are handled through the support case so that the investigation remains in one place.

### Guidance for integrators

If one of your users reports an issue, collect the relevant transaction and error details and submit the case through the support form.

For transaction-specific incidents, avoid opening the same case through multiple channels simultaneously. Keeping the investigation in the support pipeline makes ownership and status easier to track and reduces duplicated work.

**Report an Intents issue:** <https://aurora.dev/intents-support>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intents.aurora.dev/intents-connect/integration-best-practices/handling-support-cases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.