BOTLOBBIESWhat information should I send support about a bot problem?
Send a short sequence of what you attempted, when it happened, what the panel and Fortnite showed, and the exact warning. Keep passwords, authorization codes, private sign-in links, payment details, and account secrets out of the report.
Describe the missing checkpoint
A useful report says whether linking completed, whether the bot connected, whether it joined the current party, and which control or game action then failed. Include your device or browser type and the selected experience when they are relevant. Instead of saying everything is broken, describe one reproducible sequence such as connected in the panel, invited once, and Fortnite returned a particular warning. This gives support a starting point without requiring them to guess which account, screen, or stage your message refers to.
Include timing and a carefully cropped example
Give the approximate time with your timezone, and say whether the problem is ongoing or happened only once. Copy the visible error after removing personal information, or provide a cropped screenshot showing the relevant state. If a public incident was listed, mention its current status as context rather than claiming it proves the cause. A sequence that distinguishes the first failure from later retries is especially helpful, because multiple restarts or new codes can create different symptoms after the original event.
Leave sensitive material out
Do not send Epic passwords, website passwords, one-time codes, complete verification addresses, email login links, private account identifiers, or raw configuration exports. A screenshot can accidentally contain those values even when its main purpose is to show a harmless warning, so inspect the crop before sharing. Support can explain a pending or expired state from its label and sequence without receiving the material used to authorize the account. Keep the report factual and focused, then follow the supported recovery action tied to the specific problem.