> Use the RestoreCord dashboard's Help form to report bugs and suggest features. What to include, a template that works, and why it isn't for urgent questions.

Source: https://restorecord.support/report-a-bug

# How to report a RestoreCord bug or suggest a feature

The dashboard has a direct line to the team for things that are broken or missing. A clear report saves a round of questions and gets looked at faster.

[Open the dashboard](https://restorecord.com/dashboard)[Ask on Discord instead](https://restr.co/discord)

Short answer

Open Help in the RestoreCord dashboard sidebar, choose Report a bug or suggest a feature, pick Bug report or Feature request, and write a short title plus the steps, expected result and actual result. For questions or urgent issues, use Discord instead.

## What the form is for, and what it isn't

The form sends your report straight to the RestoreCord team. It's built for two things only: **bug reports** and **feature requests**. The form itself warns that it isn't a support channel, so questions, account trouble and urgent problems sent there won't get an answer. For those, use the Discord server, Telegram or email listed on the [support overview](https://restorecord.support/).

## Anatomy of a useful bug report

The form's own prompt asks three things. Answer each one on its own line:

1. 1What did you do? List the clicks or settings, in order
2. 2What did you expect to happen?
3. 3What happened instead? Include the exact error text or code

Details field templatetext

```
What I did:
1. Opened Snapshots and picked the backup from Monday
2. Clicked Restore into Backup Target

What I expected:
Channels, roles and messages restored in order

What happened:
The restore stopped at the roles step, no error shown
Happens every time, Chrome on Windows
```

A title like `Snapshot restore stops at roles step` is far more useful than `restore broken`. Mention the browser and device if the problem looks visual, and whether it happens every time.

Don't paste bot tokens, API keys, passwords or members' personal data into a report. Describe them instead, for example "the token I reset yesterday".

## A before and after

Weak: `pull not working` with the details "it doesn't work, please fix". Strong: `Scheduled migration never starts` with the details "I scheduled a pull into Backup Target for 18:00 on the Migrations page. I expected it to start then. At 18:30 it still showed as scheduled and the live log was empty. Happens with two different servers." The second one can be reproduced by the team without a single follow-up question, and that is what gets bugs fixed quickly.

## Anatomy of a useful feature request

Start with the problem, not the solution. "We run events across three servers and have to set up the same firewall rule three times" tells the team more than "add rule copying". Then describe what you'd like to see and how often you'd use it. One idea per request keeps things easy to track.

## Bug, or a question in disguise?

Many reports turn out to be setup questions. A quick test before you write:

| Situation                                                   | Probably             | Send it to                                 |
| ----------------------------------------------------------- | -------------------- | ------------------------------------------ |
| A button does nothing or a page shows an error it shouldn't | A bug                | The dashboard form                         |
| Members get error 403 on the verify page                    | A role order problem | The permission fix, then Discord if needed |
| You can't find where a setting lives                        | A question           | The Discord support server                 |
| You wish a feature worked differently                       | A feature request    | The dashboard form                         |
| Members can't verify at all right now                       | Urgent               | Discord or Telegram, right away            |

If you're unsure, search the [documentation](https://restorecord.com/docs) first. If the docs describe behaviour that differs from what you see, that difference is exactly what makes a strong bug report.

## After you send it

You'll see a confirmation that the submission reached the team. If you'd like to discuss the idea or see whether others have hit the same bug, raise it in the Discord server too. And if something is broken right now and blocking your community, don't wait on the form: [pick a live support channel](https://restorecord.support/which-support-channel).

## Send a report in three steps

1. 1  
### Open Help in the dashboard  
Log in, open Help in the sidebar and choose to report a bug or suggest a feature.
2. 2  
### Choose Bug report or Feature request  
Pick the tab that matches, then write a short, specific title.
3. 3  
### Describe it in detail  
For bugs, write what you did, what you expected and what happened. For ideas, explain the problem it would solve.

## Bug report questions

### 

### 

## Help shape what RestoreCord builds next

Log in, open Help and tell the team what's broken or what's missing.

[Log in to RestoreCord](https://restorecord.com/login)
