BOTLOBBIES.ORG
English · Available languages

Invite a Fortnite Lobby Bot from Console While Using Your Phone

Keep Fortnite open on your console and the BotLobbies.org panel open on your phone. Use the controller for Fortnite's friend and party actions; use the phone to identify and manage the hosted bot. This walkthrough follows one invitation across those two screens so you can tell which account needs to do the next action.

Give each screen one job

The console runs your playing account. That is the character you move with the controller and the player who will lead the party. The phone shows the hosted bot's setup or control panel. Opening a website on the phone does not move your console player into another Epic account.

The bot needs a separate Epic account. When setup opens Epic authorization, check which account is signed in before approving it. The account you authorize for the bot and the player you later verify are different identities. If you are unsure which one Epic is showing, resolve that before continuing with authorization.

Match the console player to the player named on the phone

During setup, the player field asks for your Epic display name, not your email address. Compare the verified player with the person actually playing Fortnite on the console. A PlayStation name or Xbox gamertag above the character can differ from the linked Epic identity, so a familiar console alias alone is not enough to confirm the match.

Use Epic's linked-account guide if the names are confusing. It describes signing into the relevant Epic account through the platform sign-in option and checking Linked Accounts. Check the association without unlinking or relinking accounts just to troubleshoot an invitation. Once the intended player is confirmed, keep that player signed into Fortnite for the remaining steps.

Read the direction of the friend request

The trial's friendship screen identifies your player and the bot. A confirmed sent message means the request was sent to the player named on that screen. On the console, open Fortnite's player profile, select Add Friends and inspect the incoming request from the bot. Epic's instructions say to select the sender's display name and accept it.

If the phone only shows the player name or a request in progress, do not treat that as a confirmed delivery. If nothing arrives, use the bot name shown in the tutorial to add the bot manually from Fortnite. The phone's Copy name action helps identify the exact text; you still carry out the social action in the game.

  1. Read the current bot name on the phone rather than an older screenshot.
  2. On the console, inspect the sender or search result before accepting or sending a request.
  3. Check that the bot is now an Epic friend. A pending request is not an accepted friendship.
  4. Continue in the tutorial after checking the result in Fortnite; Continue also allows manual progress and does not prove friendship by itself.

Send the party invitation from your playing account

When the tutorial reaches the party step, create or return to the party led by your console player. Find the bot in Fortnite's friend list and invite that account to this party. The instruction on the phone names the bot to invite; it does not ask you to invite your own player account back to itself.

Check the member list on the console after sending the invitation. Seeing the bot among friends proves a different checkpoint from seeing it in the current party. If a friend invites you to another party while you are setting up, agree which party everyone is using before moving; otherwise the bot and the human players can end up in different groups.

Confirm the party before pressing Ready

The trial tutorial asks your player to remain party leader and press Ready in Fortnite; it says the bot will ready up automatically. Confirm the current party members and selected activity on the console first. The phone is a control screen, so completing its tutorial is not evidence that a match has started.

If a warning appears, write down which screen showed it and which action produced it. A request sent to the wrong player, a bot absent from the party and a mode rejecting the lineup need different next steps. Use the console setup reference for an explicit crossplay or family-permission warning rather than changing permissions for every missing invitation.

Use a short handoff when someone else holds the phone

Say the checkpoint aloud: which player is on the console, which bot name is on the phone, and whether you are checking friendship, party membership or Ready. Ask the controller user to confirm the result in Fortnite before the phone user advances. This keeps a shared screen from becoming a second, conflicting set of instructions.

For support, share the platform, the last successful checkpoint and a cropped view of the visible warning if needed. Keep account passwords and Epic authorization codes out of that message. A connected bot and a completed invitation establish setup progress; they do not establish the opponents, rewards or outcome of the next match.