Talk to the people behind RestoreCord
Six official doors into RestoreCord: a Discord server, a Telegram channel, two email addresses, a form inside the dashboard and the company's legal notice. Each one below links to the real thing, with the reply times RestoreCord publishes itself.
Only the channels on this page are run by RestoreCord.
Pick a door, every one is real
These are the contact points RestoreCord lists on its contact page, footer, login screen, dashboard and legal notice. Nothing else is official.
Discord support server
RestoreCord's preferred channel. Team members and experienced owners answer setup, pull and backup questions, typically within about 12 hours.
Telegram channel
Product updates plus support from the team. The quickest published reply time of any channel: typically within about 3 hours.
contact@restorecord.com
The general inbox for long, detailed messages, billing and privacy requests. Allow 2 to 3 days, as emails can take several business days.
Dashboard bug and feature form
Under Help in the dashboard sidebar. It sends bug reports and feature ideas straight to the team, but it doesn't answer questions.
admin@restorecord.com
The address RestoreCord's own login screen gives when an account has been disabled. Use it to ask for that account to be reviewed.
Legal notice (Impressum)
The operating company's address, phone number and register entry, for formal and legal correspondence rather than product help.
Reply times and strengths, side by side
Reply times are the typical figures from RestoreCord's contact page. The team also aims to answer within 24 hours on business days.
| Discord | Telegram | Dashboard form | ||
|---|---|---|---|---|
| Typical reply | About 12 hours | About 3 hours | 2 to 3 days | No reply thread |
| Preferred by RestoreCord | — | — | — | |
| Answers from other owners too | — | — | — | |
| Product updates | — | — | — | |
| Long messages with full details | — | — | ||
| Setup and account questions | — | |||
| Bug reports and feature ideas | Discuss them | Discuss them | Possible |
Six things to have ready before you write
A complete first message is the single biggest thing you control about how fast your problem gets solved.
You've searched the docs
The documentation and its common-errors pages already cover most setup questions and verification errors.
Server name or ID
Say which server is affected, so nobody has to guess between the several you may run.
The exact error
Copy the message and code as shown, for example 403 on the verify page or 10003 for a rate limit.
What you already tried
List the fixes you've attempted so the reply starts where you stopped, not at step one.
A screenshot with secrets hidden
Show the dashboard or verify page, with bot tokens, API keys and passwords blacked out.
One channel, one thread
The same team reads every channel. Posting everywhere at once only lengthens the queue.
Disabled account, refund or legal matter?
Those go to specific addresses, not the chat channels. Our guide lists who handles what.
A direct line for bugs and ideas
Logged-in owners have a form under Help that drops bug reports and feature requests straight into the RestoreCord team's queue. It's the best place for something broken or missing, and the wrong place for a question.
- Choose Bug report or Feature request first
- Write what you did, what you expected and what happened
- Use Discord or Telegram if you need someone to answer you
Report a bug or suggest a feature
Dashboard sidebar, Help
Title
Before you send
Steps, expected result and actual result
Goes in the details field
Tokens, keys and passwords removed
Describe them instead of pasting them
This is a question, not a bug
Questions go to Discord or Telegram
Some answers don't need a ticket
RestoreCord documents its setup and its most common errors in detail. A minute here can save a day in a queue.
RestoreCord documentation
Guides for bots, servers, verify messages, sub-users, webhooks, pulls and snapshots, plus a common-errors section with step-by-step fixes.
Fixes already written up
Errors members and owners hit most often
VPN or proxy detected
Turn off the VPN, Private Relay or proxy, then reload
Rate limited (10003)
Discord's limit: wait 60 minutes before one retry
Error 403 on the verify page
Bot permissions or role order, fixed by the owner
Email permission required
Verify again and keep Email switched on
Common errors
Written fixes for VPN or proxy blocks and Discord's rate limit, the two errors members report most.
Can't verify as a member?
Our member guide explains which errors you fix yourself and which only the server's staff can clear.
Manage my data
Members can see or remove what a server stores about them on their own, with no email needed.
Questions about reaching RestoreCord
A real person is one message away
The Discord support server is where RestoreCord wants your question, and where the team picks it up.