Rules for WoW Boosters

Rules for WoW Boosters, Farmers & Coaches

A complete set of rules and standards for everyone providing World of Warcraft services through GRAMBL — boosters, farmers, and coaches alike. Following these rules is critical for protecting client accounts, maintaining consistent service quality, and minimizing the risk of action from the game's developers. Every active team member is expected to know this document.

⚠️ Note: Blizzard's policies around boosting and account sharing change periodically. This document reflects our current standards and is reviewed regularly — always check for the latest version before starting an order.

1. Core Principles

Account safety comes first. Nothing about an order matters more than the client's account staying safe. Any action that risks it is not worth doing, regardless of how much faster or easier it might be.
Treat every account like your own. Full confidentiality, careful handling, and documentation of everything you do on it.
Blend in. Everything you do on a client's account should look like ordinary play from a regular player — no signs of automation, scripting, or unusual behavior patterns.

2. Which Rules Apply to Your Role

Most roles at GRAMBL involve direct access to a client's account. Coaching does not — a coach works alongside the client in real time, on the client's own logged-in session. The rules below are grouped accordingly.

Role Group	Roles Included	Account Access?
Account-Access Roles	PvP Booster, Mythic+ Booster, Raid Booster, Achievement Completion Specialist, Mount Farmer, Pet Farmer	✅ Yes — full rules in Sections 3–8 apply
Coach / Trainer	Coach / Trainer	❌ No — see Section 9 for coaching-specific rules instead

3. Account Login & Access Security

Applies to all Account-Access Roles.

VPN required: always connect through a VPN server located in the same country or region as the client's usual play location.
IP consistency: your connecting IP should match the client's geographical region for the entire session.
Staggered login: never log in immediately after the client logs out — wait at least 30–60 minutes.
Never touch security settings: do not change the password, disable 2FA, or alter any account security setting under any circumstances.
Coordinate timing in advance through your manager before beginning any session.

Session & Schedule Limits

Limit	Standard
Maximum continuous session	4–6 hours
Mandatory breaks	At least 15 minutes every 2 hours
Daily limit	No more than 10–12 hours on a single account
Weekly rest	At least 1 full day of inactivity on that account

4. Communication Protocol

Applies to all Account-Access Roles.

🚫 All client communication goes through a GRAMBL manager — never directly with the booster or farmer. This isn't a formality; it protects the client's account, keeps records consistent, and keeps every order auditable.

Strictly Prohibited

Responding to messages in game chat from strangers
Starting conversations with other players
Accepting friend requests, guild invites, or group invites from unknown players
Discussing prices, discounts, or "extra services" directly with a client
Offering services outside GRAMBL, or directing a client to another platform
Sharing personal contact details with a client

Allowed, Minimal Exceptions

Brief, functional group callouts within content ("ready", "pull", "skip")
Built-in emotes and standard raid/group commands

5. Handling Client Property

Applies to all Account-Access Roles.

Gold and currency: never spend, transfer, or use a client's gold for anything other than the order itself.
Items and gear: everything obtained stays on the client's account. Don't sell, delete, or equip anything unless it's required to complete the order.
Achievements, titles, and progress: these belong entirely to the client — don't use up consumables or resources beyond what the order requires.

6. Documentation & Reporting

Applies to all Account-Access Roles.

Every session should leave a clear record. At minimum:

Start and end time of the session
What was completed (content cleared, achievements earned, items obtained)
Any changes in gold, items, or reputation
Screenshots or clips of key moments — especially final completion of the ordered content

Send your report to your manager, not the client directly — see Section 4.

7. Role-Specific Guidelines

⚔️ Raid & Mythic+ Boosting

Study boss mechanics thoroughly before the run — don't rely on the group to carry unfamiliar content.
Groups must consist only of verified GRAMBL boosters or vetted guild members. Never fill a spot using the public Group Finder with unknown players.
If the client is present but not actively playing, standard AFK behavior is fine as long as it doesn't break game mechanics for the group.
Keep in-group chat minimal and functional — no discussion of pricing or services.

🛡️ PvP Boosting

Play according to a reasonable class/spec meta — no obviously scripted or bot-like patterns.
In rated content (Arena, Rated Battlegrounds), the client must actively participate if playing alongside the booster — AFK is not acceptable in rated queues.
Avoid sharp, suspicious rating jumps in a single session.
No toxic behavior, no prohibited add-ons.

🏆 Achievement Completion

Confirm the exact achievement (and any sub-requirements) with your manager before starting — some achievements require specific group sizes, difficulty settings, or sequencing.
Where an achievement requires a group, the same "verified team only" rule from raid/M+ boosting applies.
Document the specific completion moment (achievement pop-up, relevant UI) for the client's report.

🐴 Mount Farming & 🐾 Pet Farming

Farming sessions on a client's account follow the same login, VPN, and session-limit rules as any other Account-Access role.
Realistic pacing — camping a boss or rare spawn for a reasonable, natural amount of time looks very different from scripted, repetitive farming. Avoid patterns that look automated.
Report drop attempts honestly, including unsuccessful sessions — clients should have an accurate picture of progress, not just a final result.
Any gold spent on farming aids (repairs, consumables) should be minimal and directly tied to the order.

8. Technical & Security Requirements

Use only a licensed, official game client — no modified or third-party clients.
No bots, automation scripts, or programs that bypass game protections, under any circumstances.
Keep your own system secure: updated OS, reliable antivirus, and a reputable VPN provider.
Stable internet connection and a device capable of smooth, uninterrupted play.
Don't store client credentials in unprotected files or unsecured notes — use whatever secure method your manager provides.

9. Coaching — A Different Set of Rules

Coaching works differently from every other role above: the client stays logged into their own account, and the coach works with them live, guiding their play rather than playing for them. Because of that, most of the account-access rules simply don't apply here.

Direct communication is the job. Coaches talk to clients directly — by voice, text, or screen share — throughout the session. This is expected and encouraged.
No account access required. A coach should never need the client's login credentials. If a session seems to call for it, stop and check with your manager first.
Stay on topic and professional. Keep the session focused on coaching content — mechanics, rotation, decision-making — not on GRAMBL's other services or pricing.
Documentation is lighter but still expected: a short session summary (what was covered, what to work on next) helps both the client and GRAMBL track progress.
Scheduling and payment for sessions are still coordinated through your manager, not arranged privately with the client.

10. Team Coordination & Shift Handover

When more than one specialist works an order (multi-day boosts, farming assignments, or handoffs between sessions):

Clearly divide who's responsible for what before starting
Brief the next person on progress, timing, and anything unusual before handing off
Keep a shared log of what's been done so nothing gets duplicated or missed
Confirm the next person is ready before you step away from the account

11. Emergency Situations

Situation	What to Do
Suspected account compromise	Stop all activity immediately, notify your manager, and document what happened. Don't try to fix it yourself.
Technical failure (connection loss, crash, etc.)	Notify your manager as soon as you're back online. Document the gap in your session log.
Warning or suspicious activity from the game's systems	Stop working immediately, preserve any evidence, and contact your manager before doing anything further. Never try to resolve it directly with the game's support yourself.

12. Quality Standards

Ongoing work with GRAMBL is based on a simple standard: real, demonstrable skill in the content you're working on, consistent account safety, honest and complete reporting, and professional conduct with every order. Reliable performance in these areas is what leads to priority orders and expanded responsibilities over time.

13. Staying Current

Blizzard's stance on boosting, account sharing, and third-party services shifts periodically. Every specialist is expected to stay reasonably current on major changes and flag anything that might affect how orders should be handled. When something changes significantly, GRAMBL will update this document and notify the team — check back periodically rather than assuming these rules are static.

14. Violations & Consequences

Violating these rules — particularly anything affecting client account safety, unauthorized direct client contact, or misuse of client property — can result in a warning, a reduced rate on the affected order, or immediate termination of the working relationship, depending on severity.

📩 Questions? Contact GRAMBL

Last Updated: August 22, 2026
Version: 1.0