Everything a specialist needs.
Relics Tech Support and PC Building. What you can use, how, when, and who may use it.
Getting Started
The teams, the roles, how to join, and where everything lives.
The three teams
Tech Support
Troubleshooting software and hardware problems. Role: Tech Team.
PC Building
Part lists, upgrades and compatibility. Role: Build / Upgrade Team.
Laptop / Prebuilt
Laptop and prebuilt recommendations. Role: Laptop / Prebuilt Team.
Roles
Junior Specialist, Specialist, Senior Specialist. Promotions come from constant activity, solid work and strong tech skills. The details are on the Policies page.
How to apply
Fill out the Google form. You can apply to one, two or all three teams. After that, follow #specialist-app-results and #specialist-intros.
- Application review: a reviewer accepts or declines.
- Team vote: the team gives opinions, the reviewer decides.
- You confirm your answers are your own work (AI for research only).
- The role is not a real-world certification.
Where everything lives
#specialist-chat#specialist-announcements#management#ticket-logs#ratings#specialist-resourcesrelicstech.site/handbookTickets
From the Create Ticket button to the end message: how a ticket runs.
Life of a ticket
- Claim it. Click Claim Ticket or use
/ticket claim. Read the form answers at the top. - Diagnose. Start simple: restart, drivers, Task Manager. Use tags for repeatable instructions.
- Can't continue? Click Unclaim, post in
#specialist-chatand leave context for the next person. - Wrap up. Send
!endmessage, then/ticket requestcloseor/ticket close.
Who types where
Users press Create Ticket in #tech-support or the PC building and support channels. Three kinds exist: support, PC building and application.
- Tech Team types only in Tech Support tickets.
- Build / Upgrade Team types only in PC Building tickets.
- Someone else needs in? Use
/ticket addand pick the user or role.
Closing
- Close after 2 days without a reply, or after 1 day if the opener says to close it.
- Keep the ticket list free of clutter.
- Closed tickets and transcripts are in
#ticket-logs. - If something goes wrong or the user is unhappy, tell a Senior or Management. Don't argue in the ticket.
Adding a note
Notes are saved per user, so the next specialist sees the history. Add one when a user has a repeat issue or there is something the next person should know.
- Go to the notes channel. Non-moderators can only use the Notes system in the channel set up for it.
- Add the note. Use
/note add, pick the user and write the note. You can also use the Vör Discord integration (right-click menu). - Check it.
/notes @userlists a user's notes,/note infoshows one by its ID. - Fix a mistake.
/note editor/note deleteon your own note.
Junior Specialist, Specialist, Senior Specialist and Tech Team. You can add and read notes, but you cannot see notes written by moderators.
Troubleshooting
Start simple, work toward complex, and reach for a tag when the answer repeats.
Workflow
Check the form answers at the top of the ticket (OS, issue type, description). Ask what changed recently, then go from simple to complex: restart, drivers, Task Manager, then logs and hardware.
- Check
#specialist-resourcesfirst. - AI is for research only. Verify it, never copy-paste.
- Basics first.
Which tag for which problem
| Problem | Tag | Note |
|---|---|---|
| Windows broken or slow | !usb | Prefer a USB clean install over Windows Reset. |
| Display driver crashes or artifacts | !ddu | Remove the old driver before installing a new one. |
| PC won't POST, odd BIOS state | !cmos | Reset CMOS after checking power and RAM seating. |
| New CPU or board instability | !biosupdate | Disable BitLocker before flashing. |
| You need exact specs | !specify | Ask for the Spec-ify link output. |
| Crashes under load, overheating | !occt | Run OCCT and compare temperatures. |
| Drive needs wiping | !clean / !cleanw | Pick by where DiskPart runs (OS vs. installer). |
| Hardware looks wrong | !photoguide | Ask for photos before guessing. |
Right-click a pasted FRST log and pick Clean FRST Log (or use /frst clean_strings) to strip noise before you read it.
PC Building
Send the right questionnaire first, then build the list.
How requests arrive
New users request build advice with /getstarted. It pings the Specialist role, so watch for it. Once you pick one up, send the matching questionnaire below.
Questionnaires
Every user answers the matching questionnaire before you build or recommend anything. They are sent as tags.
!bhq
New PC build. Only if the user buys within 7 days.
!uhq
Upgrading an existing PC.
!lhq
Laptop recommendation.
Tools
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/getstarted | Lets a new user request build advice. Pings the Specialist role. | Everyone (new users) | A new member wants help picking parts. | /getstarted |
!bhq, !uhq, !lhq | Send the right questionnaire. | Junior Specialist and up | Before any recommendation. | !bhq |
/psu search | wattage | help | Look up PSU quality and wattage. | Specialist team | Reviewing a PSU. | /psu search RM850x |
/dropref ram_stats | ram_offers | ram_category | pcpp_compare | Compare a PCPP list against drop prices. | Specialist team | Is a part a good deal? | /dropref pcpp_compare |
/pcpp history | Previously shared PCPP lists. | Specialist team | Find a user's older list. | /pcpp history |
Right-click: Show PCPP List | Preview a PCPP link (private or public). | Specialist team | A link did not auto-preview. | Right-click the message |
/currency | Convert currencies. | Everyone | Prices in another currency. | /currency 100 USD EUR |
Building the list
Compile in PC Part Picker, check compatibility and budget, then post the list. Vör shows a preview automatically.
Bots
What each bot does and what you need from it.
The bots moved recently. If a command does nothing, check it still works and tell a Senior or Management.
/ticket add (let a user or role into a ticket), rename, close requests and closing all run through Tickety.#eco: /balance, /eco, /game, blackjack, slots, /gamble, gifts. Not support related.Commands
Slash commands, !tags and right-click menus, with who may use them and when.
Tags are called with !name in an allowed channel, or with /tag get name. Tags are rate-limited to 2 calls per channel. Any specialist can create tags. Editing and deleting tags is limited to one role.
Tags
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
!endmessage | Thank-you message with the ratings channel and staff application link. Mandatory at the end of every ticket. | Junior Specialist and up | Right before closing a ticket. | !endmessage |
!ddu | DDU guide with download and video tutorial. | Junior Specialist and up | Clean GPU driver reinstall. | !ddu |
!usb | Guide to (re)install Windows from a USB stick. | Junior Specialist and up | Reinstall or clean install needed. | !usb |
!biosupdate | BIOS update guide. Warns to disable BitLocker first; covers Q-Flash, EZ Flash, M-Flash, Instant Flash. | Junior Specialist and up | New CPU or stability problems. | !biosupdate |
!cmos | How to reset the CMOS. | Junior Specialist and up | No POST, bad BIOS settings. | !cmos |
!specify | Spec-ify for full system info. | Junior Specialist and up | You need the exact hardware. | !specify |
!occt | Introduction to OCCT stress testing. | Junior Specialist and up | Crashes, heat or stability tests. | !occt |
!clean | Wipe a disk with DiskPart from inside the OS or recovery. | Junior Specialist and up | Disk needs a full wipe from a running OS. | !clean |
!cleanw | Same wipe, from the Windows installer (Shift+F10). | Junior Specialist and up | Disk wipe during Windows setup. | !cleanw |
!photoguide | Which photos the user should send. | Junior Specialist and up | Hardware or build problems. | !photoguide |
!bhq | PC build questionnaire. Only if the user buys within 7 days. | Junior Specialist and up | Start of a PC build request. | !bhq |
!uhq | Upgrade questionnaire. | Junior Specialist and up | User wants to upgrade parts. | !uhq |
!lhq | Laptop recommendation questionnaire. | Junior Specialist and up | User wants a laptop. | !lhq |
!support | Tells a user how to get help by opening a ticket. | Junior Specialist and up | A user asks how to get help. | !support |
Helpers: /tags lists all, /tag search finds one, /tag info shows details, /tag raw copies the raw text.
Ticket commands (Tickety)
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/ticket claim | Claim the current ticket. | Specialist team | First thing when you take a ticket. | /ticket claim |
/ticket add | Add the provided user or role to the current ticket. | Specialist team | Someone else needs in. | /ticket add @user |
/ticket remove | Remove the provided user or role from the current ticket. | Specialist team | Someone should no longer see it. | /ticket remove @user |
/ticket priority | Change the priority of the current ticket. | Specialist team | Time-critical problems. | /ticket priority high |
/ticket requestclose | Request a ticket closure for the current ticket. Include a reason and 3d (3 days). | Specialist team | Solved, or user gone quiet. | /ticket requestclose solved 3d |
/ticket rename | Give the current ticket a new name. | Specialist team | Make it easy to find. | /ticket rename GPU crash |
/ticket close | Close the current ticket. | Specialist team | After the end message. | /ticket close |
Support helpers (Vör)
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/remindme | Reminder up to 9999 hours. | Everyone | Follow up with a user later. | /remindme 24h check ticket |
/reminders add | list | remove | Manage reminders. | Everyone | Overview of your reminders. | /reminders list |
Right-click: Clean FRST Log | Strip noise from FRST logs. | Specialist team | Reading a pasted FRST log. | Right-click the log |
/frst help | FRST helper commands. | Specialist team | See available FRST tools. | /frst help |
/whois, /uinfo | Look up a user. | Specialist team | Account age and info. | /whois @user |
/alt show | Show linked alt accounts. | Specialist team | Suspicious second account. | /alt show @user |
/timestamp | Discord timestamp. | Everyone | Tell users a time in their zone. | /timestamp |
/calculator | Quick calculator. | Everyone | Quick maths for builds. | /calculator 650*1.2 |
/close_thread | Close a thread. | Specialist team | Thread is resolved. | /close_thread |
/ping | Check that the bot is alive. | Everyone | Bot seems unresponsive. | /ping |
Notes (Vör)
Notes are saved per user. Who may add notes: Junior Specialist, Specialist, Senior Specialist and Tech Team, only in the notes channel. Specialists cannot see notes written by moderators. Step by step: see Tickets, Adding a note.
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/note add @user text | Add a note to a user. You can also use the Discord integration (right-click menu). | Specialist team | Repeat issues worth remembering. | /note add @user repeat GPU crash |
/notes @user | Show a user's notes. | Specialist team | Before helping a returning user. | /notes @user |
/note edit | delete | info | type | help | Manage your notes. | Specialist team | Fix or remove a note. | /note info 3 |
Ranks and Permissions
The ladder, and what each rank can do in Discord.
The ladder
Discord permissions
From the Discord role settings. Everything not shown is off. All members can send messages, react and attach files.
| Permission | Junior | Specialist | Senior Specialist |
|---|---|---|---|
| Kick members | No | No | No |
| Ban members | No | No | No |
| Timeout members | No | No | Yes |
| Manage messages | No | No | Yes |
| Change nickname | Yes | Yes | Yes |
| Manage nicknames | No | No | Yes |
| Pin messages | No | No | Yes |
| Manage threads and posts | No | No | Yes |
| Bypass slowmode | No | No | Yes |
| Mention @everyone / @here | No | No | No |
| Voice: mute | No | No | Yes |
| Voice: deafen, move | No | No | Yes |
Rules and Judgement
The calls you will have to make, and who to ask.
Staff Policies
The rules every specialist agrees to.
Use of AI
While AI tools can be valuable resources for assisting with technical support, they should be used responsibly and in moderation.
Guidelines
- AI may be used as a supplementary tool for research only.
- Direct copying of AI-generated responses is prohibited.
- Your own technical knowledge should always be the primary resource.
Remember that while AI can provide helpful suggestions, our goal is to offer human-to-human support with personal attention to each user's unique situation.
Payments and Tipping Policy
Payments are not permitted. No paid work, commissions, paid 1-on-1 services or price negotiations of any kind through this server.
We appreciate that users may wish to reward exceptional service. However, to maintain professionalism and fairness, strict guidelines apply to accepting gratuities.
Permitted
- Accepting a tip only if explicitly offered by the user first.
- Communication via the ticket channel.
- Communication via DMs only with prior permission from Senior Staff+ (SR+).
Prohibited
- Soliciting or asking for a tip.
- Setting a price for support services.
- Requesting a specific amount.
Any specialist found requesting tips, setting prices, or negotiating amounts will be issued TWO strikes on a first offense, which can lead to removal from the team. Our support services are free; tipping is entirely optional and user-initiated.
Personal Information Policy
Specialists must refrain from asking users for personal information including but not limited to:
In order to preserve the user's privacy and uphold strict ethical standards, specialists must avoid collecting any personally identifiable information unless absolutely necessary and explicitly consented to.
Prohibited information requests
- Full name or any identifying aliases
- Physical address or location details
- Phone numbers
- Email addresses
- Identification numbers (SSN, etc.)
- Financial information
Specialists must prioritize user privacy and only request information that is strictly necessary for the technical support task at hand. Any requests for personal information must be justified by absolute necessity and require explicit user consent.
Promotions
Our promotion system is designed to recognize and reward staff members who demonstrate consistent excellence in their roles.
Junior Specialist → Specialist
- After taking several tickets and remaining active, Senior Staff+ will schedule an "Observation".
- Senior Staff will complete an observation form evaluating your performance.
- Promotion decisions are based on this formal evaluation.
- Demonstrate consistent activity and quality responses.
- Complete an introduction in
#specialist-introsincluding: your name/nickname, where you're from, your areas of technical expertise, and why you joined the support team.
Specialist → Senior Specialist
- Consistently high user satisfaction ratings.
- Demonstrated leadership within the team.
- Active participation in community discussions.
- Willingness to mentor junior staff members.
- Consistent activity over an extended period.
Promotions beyond Specialist are evaluated based on overall contribution to the community, not just quantitative metrics. Leadership qualities, technical expertise, and dedication to helping others are all considered.
Inactivity Policy
To maintain an active and responsive support team, we require all staff members to remain engaged with our community.
Activity requirements
- If you do not participate in the server in a 14 day period without warning, you can be given a strike, demoted, or removed.
- Participation in community discussions is encouraged.
- Extended absences should be communicated to leadership.
A staff member hasn't responded to any tickets or participated in server discussions for 3 weeks without notice. After attempts to contact them go unanswered, they would be subject to removal from the staff team.
We understand that real life takes priority, so communication about availability is always appreciated and will be taken into consideration.
Three Strike System
To maintain high standards of professionalism and service quality, we employ a three-strike system for policy violations.
First strike
Cause: First-time violations (e.g., breaking rules, unprofessional behavior, misuse of AI, soliciting or requesting a tip)
Result: Formal warning.
Duration: 14 days.
Second strike
Cause: Repeating violations, soliciting or requesting a tip
Result: Temporary restrictions & leadership review.
Duration: 14 days.
Third strike
Cause: Continued violations.
Result: Removal from staff team.
Appeal: After 30 days.
Severe violations may skip the strike system entirely and result in immediate removal at the discretion of leadership. All strikes expire after 14 days if no further violations occur.
Resources
Useful places outside the server.