RestoreCord

When RestoreCord restores a backup of a Discord server, every channel, role and message comes back with a new Discord ID, and the buttons on restored copies of TicketCord's messages no longer work (Discord only sends a click to the app that posted the message). Reconnect TicketCord fixes that in one step: your ticket settings switch to the restored channels and roles, your panels are posted again, open tickets carry on in their restored channels with fresh Close and Claim buttons, and for a restore into a new server your ticket history and stats move with them. It is for anyone who uses TicketCord in a server they back up with RestoreCord.

Before you restoreCopy Anchor Link

Do these before you start the restore in RestoreCord:

• Link RestoreCord to TicketCord. Follow Get Pro with RestoreCord: on Plan & billing, under Partner perks, click Connect RestoreCord and approve TicketCord. Link before the restore starts: RestoreCord asks TicketCord at the start which channels hold tickets and which messages to leave out, so open tickets come back first and your panels and ticket cards are left out instead of coming back as copies with dead buttons. At the latest, link before the restore finishes: TicketCord only learns about a restore from what RestoreCord sends while your accounts are linked, so a restore that ended before you linked does not show up.
• Allow TicketCord to read your restores. The approval screen asks to let TicketCord see your server restores and the new IDs they created. TicketCord cannot reconnect without it. If you linked RestoreCord before this permission existed, the restore page shows Reconnect RestoreCord (also when it cannot tell whether your link has the permission): click it and approve again.
• Be an admin in the restored server. You must own the restored server or have a role with Administrator in it.
• Have your bots in the restored server. Every one of your bots that was set up in the backed-up server must be in the restored server. RestoreCord's restore offers invite links for them, and the TicketCord restore page has an Add button for any bot that is missing.

Reconnect step by stepCopy Anchor Link

OptionsCopy Anchor Link

The page shows these only when they apply. Both start unticked.

What TicketCord doesCopy Anchor Link

Each step on the progress list does the following.

• Update your settings. Every channel, category, role and mention in your bots' settings for the server, including panels, buttons, messages and forms, is switched to its restored copy. Custom emojis on panel buttons and menus are matched by name when exactly one emoji in the restored server has that name (custom emojis written inside message text are not matched). Anything that could not be matched is listed under Settings to set again. For a new server, the settings move there: your bots no longer have settings in the old server afterwards.
• Move ticket history (new server only). Your tickets, notes, saved replies, ratings, response target records, escalations, stats, staff activity, staff profiles, AI usage, saved ticket views, knowledge base, the history of Atlas threads in public channels and your GitHub integration link move to the new server. Tickets keep their messages, and ticket numbering continues where it left off.
• Post panels again. Each panel that was in the backed-up server is posted again in its restored channel, with working buttons. TicketCord recognises which of your saved panels each one was from its buttons.
• Reconnect open tickets. Each open ticket is attached to its restored channel or thread. A ticket whose channel was not restored gets a new channel or thread, created like a new ticket. Each ticket gets a fresh welcome message with Close and Claim buttons as soon as its channel's message history is back, so the card appears under the restored conversation rather than above it. In a channel ticket this message does not ping your staff. In a private-thread ticket it mentions the staff roles, because that is how Discord adds them to the thread.
• Refresh the bots. The bots load the new settings straight away; you do not need to restart them.

While the restore runsCopy Anchor Link

• Timers pause. From the moment the restore starts, auto-close, its reminders, ModMail reminders, scheduled closes and response targets are paused for the server, so no ticket is closed or marked late because its channel is being rebuilt. A reconnected ticket's timers start again when it gets its fresh Close and Claim buttons or when the restore ends, whichever is later; every other ticket's start again when the restore ends. They also start again if RestoreCord reports no progress for about an hour, or if TicketCord hears nothing from RestoreCord for 12 hours. Time spent paused does not count towards any timer, with one exception: a reconnected ticket whose fresh buttons could never be posted has its timers started again 6 hours after the restore ends, and for that ticket the paused time does count.
• Restored history is not counted as new messages. The messages RestoreCord posts back into a reconnected ticket do not trigger Atlas, reset timers or get stored a second time. Until a reconnected ticket gets its fresh buttons, for at most 24 hours, every message posted by a webhook in it is treated this way.
• Members get their tickets back when they rejoin. When a member who opened a reconnected ticket joins the restored server, they get access to their open tickets again, as they had before.

After the restore finishesCopy Anchor Link

Once RestoreCord reports the restore as finished (or failed or stopped), TicketCord makes a second pass on its own:

• It switches any setting that could only be matched now (archived threads, closed tickets and custom emojis are restored last) and updates Settings to set again.
• It tries again to post any panel that could not be posted earlier, for example because its channel or one of its emojis was not restored yet.
• It points closed tickets at their restored channels, so reopening one works in place.
• It removes the restored copies of TicketCord messages whose buttons cannot work. Copies of panels and ticket cards are deleted for you, because fresh ones were posted. Copies of Atlas answers, stats replies and other messages TicketCord keeps on purpose stay, and so do copies with no buttons. Any other copy with buttons is listed under Restored TicketCord messages for you to decide.

TicketCord keeps following up for 7 days after the restore ends, and RestoreCord keeps the list of new IDs for the same 7 days, so reconnect within that time.

Same server or a new serverCopy Anchor Link

Failed or stopped restoresCopy Anchor Link

If the restore failed or was stopped, the Restore card says "The restore failed" or "The restore was stopped".

• Some channels and roles were created: you can run the restore again in RestoreCord, which we recommend, or reconnect TicketCord with what was restored. To do that, tick Reconnect with what was restored and click Reconnect TicketCord.
• It ended before any channels or roles were created: there is nothing to reconnect to. Run the restore again in RestoreCord.

What to check afterwardsCopy Anchor Link

After the reconnect the page shows up to four more cards.

• What could not be reconnected lists each ticket (by number) or panel that did not make it, with the reason. See Troubleshooting.
• Settings to set again lists roles, channels, categories and emojis that were not found in the restored server, with where each one is used in your settings. Those settings still point at the old ones. Click Open settings for bot and pick them again.
• Good to know shows notes that apply to your restore:
  • "Images you uploaded to your panels still come from the old server. Upload them again if they stop showing." (new server only) Upload them again on Panels → Ticket panels.
  • "Some custom emojis in your settings were not found in the restored server. Pick them again in the dashboard."
  • "Message history is still restoring. Each ticket gets its Close and Claim buttons once its messages are back."
  • "Some settings may only match once the restore finishes. We check them again then."
  • "Some knowledge base entries could not be copied. Check your knowledge base and add anything missing." (new server only) Check them on AI assistant → Atlas → Sources.
• Restored TicketCord messages appears after the restore finishes, when restored copies with buttons need your decision. Tick the ones to remove (or Select all), click Delete selected and confirm. Deleted messages cannot be brought back. Open in Discord shows a message first, and Keep them clears the list without deleting anything. The card also says how many copies were deleted for you.

Also check in Discord that your panels sit where you want them, and that staff roles can see the restored ticket channels.

What RestoreCord leaves outCopy Anchor Link

When your accounts are linked at the start of the restore, RestoreCord does not restore these messages from your bots, because their buttons only work on messages TicketCord posts itself:

• your ticket panels, which TicketCord posts again;
• the messages inside tickets that carry ticket buttons: the welcome message with Close and Claim, claim, close, reopen and delete confirmations, confirmations for removing the ticket's creator, closed-ticket controls (reopen, transcript, delete), pin and unpin, inactivity reminders with their keep-open button, quick replies, AI Help, application reviews, ModMail notices and controls, and Atlas's offers to open a ticket or mark a question as solved.

Other messages from your bots, such as Atlas answers and stats replies, are restored as copies: their text stays readable, but their buttons do not work.

TroubleshootingCopy Anchor Link

The restore page explains anything that stops the reconnect next to the Reconnect TicketCord button. In these messages, server is your restored server's name.

Reasons under What could not be reconnected:

If a member cannot see their reconnected ticket after rejoining, staff can add them with /add.

Common questionsCopy Anchor Link