> For the complete documentation index, see [llms.txt](https://docs.oshi.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oshi.co/help-and-support/support-channels.md).

# Support Channels

How to get help from Oshi support via email, Discord, and this help center.

***

### Which channel should I use?

| Issue type                                           | Best channel     |
| ---------------------------------------------------- | ---------------- |
| Payment, billing, account access                     | Email            |
| Quick questions, community discussion, feature ideas | Discord          |
| Self-service, browsing topics                        | Help Center      |
| Bug reports                                          | Email or Discord |

***

### Email support

<support@oshi.co>. Response within 48 hours.

Email is the best channel for account access problems, payment or billing questions, Legacy Contributor status issues, and technical problems with the platform. For bug reports, include "BUG:" in the subject line. For urgent issues affecting payment, rewards, or account security, include "URGENT:" in the subject line.

***

### Discord community

[Join our Discord](https://discord.gg/oshi). Response times vary (community-driven).

Discord is the best place for quick questions about the campaign, connecting with other participants, and general GATE 2 discussions. It's also where feature ideas and suggestions live. The team reads community feedback regularly, and moderators can route support questions to the right people.

***

### Help Center

You're here! Browse by section:

**Start Here** covers platform basics, how anime gets made, and where your contributions go. **GATE 2 Campaign** covers ranks, rewards, timeline, leaderboards, and quests. **Help & Support** covers payments, account management, and troubleshooting.

***

### Campaign updates

For announcements and production news:

**X:** [@oshikatsu\_co](https://x.com/oshikatsu_co) and [@gate\_anime](https://x.com/gate_anime)

**Campaign page:** [gate2.oshi.co](http://gate2.oshi.co)

**Email:** Updates sent to your Oshi account email

***

### Submitting feedback

We welcome suggestions for improving Oshi. You can share feedback in Discord or email <support@oshi.co> with "FEEDBACK:" in the subject line.

See [Reporting Issues or Bugs](/help-and-support/reporting-issues-or-bugs.md) for how to submit bug reports with the details our team needs.

***

**Related articles**

* [Managing Your Account](/help-and-support/managing-your-account.md): Account settings and security
* [Reporting Issues or Bugs](/help-and-support/reporting-issues-or-bugs.md): How to report problems
* [Staying Safe](/help-and-support/staying-safe.md): How to verify official channels

{% hint style="info" %}
**Still need help?** Join our [Discord](https://discord.gg/oshi) or email <support@oshi.co>
{% endhint %}


---

# 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.oshi.co/help-and-support/support-channels.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.
