Meet Hero Chat

Last updated Oct 15, 2026

Hero Chat is the assistant built into DFS Hero. It calls itself Hero. It reads the slate in front of you, your uploaded entries, your contests, and your results history. It can also change your build settings, start a build, run the simulator, fill your entries, export the CSV, run a late swap, open a slate, and create a Playbook. Every change goes through a card that you confirm or cancel.

Power plan. Hero Chat is part of the Power plan. On Essential the chat button does not appear.

Before you start

Open Hero Chat

  1. Go to the Day View, a slate workspace, the Dashboard, or Film Room. Hero Chat opens on these pages only.
  2. Click the chat button in the top bar, between the bell and the help button, or press ⌘\ on a Mac or Ctrl+\ on Windows.
  3. Hero opens as a panel on the right. On a narrow window it floats; on a phone it fills the screen.

  1. Read the greeting. When you have unfilled entries on a slate today, Hero opens with a line about them and offers to work up a build.
  2. Click one of the four suggested prompts, or type in the Ask Hero… box and press Enter. Shift+Enter adds a line without sending.
  3. Press Escape or click the X to close Hero Chat. The thread stays saved.

What Hero is looking at

The context rail under the header tells you what Hero sees: the day on the Day View, the sport and slate in a workspace, or Dashboard or Film Room on those pages. The suggested prompts change with the page.

While Hero writes, the send button turns into Stop.

How a reply reads

After Hero reads something, an activity row above the reply names the read. Click the chevron at its end to see the raw data Hero used.

Under a reply, Hero often adds follow-up chips such as "Focus on CFB Main". A chip sends that text as your next message.

A pivot read shows a Pivot board with the player to fade and the player to buy. A StackIQ read shows a table with Stack, Proj, Own, and Lev columns.

Proposal cards

Hero never changes anything on its own. Every change arrives as a card with a summary, a Details disclosure, and the buttons Confirm and Cancel.

  1. Read the summary. For a settings change the card lists what will change, for example "Smart Randomness: Moderate" and "Stacking: 3-stack".
  2. Click Details to see every value the card carries.
  3. Click Confirm to apply it, or Cancel to drop it.
  4. An applied card shows Done. A Run the build card shows Started instead, because the build keeps working after Hero fires it. A failed card shows Failed with the reason, and Hero sends a corrected card in the same reply when it can.

After a confirmed card, Hero states what changed and offers the next step as chips.

A read of your open workspace or of your built lineups needs no confirmation. Those cards go straight to Done.

What Hero can read

ReadWhat Hero gets
Slate overviewSport, site, lock time, game count, contest count, roster rules
ContestsThe slate's contests with overlay, rake, fill %, field size, and type; the best contests today across all slates; a deep analysis of one contest; top-finisher patterns from comparable past contests
Your entriesYour uploaded entries for the slate and their fill state
Your historyYour lifetime profile for a sport and site, the ROI, ITM %, stake, and profit by sport and window from your Film Room results, and the latest Hero IQ coaching
Games and playersGame environments with weather where available, the player pool with injury flags and MLB batting order, Hero Insights slate analysis, StackIQ team ratings (classic NFL, NHL, MLB, CFB), and pivots (classic NBA, WNBA, NFL, NHL, MLB, CFB, CBB)
Sport primerA strategy primer for the sport
The dayThe Day View survey of the date on screen
Your workspaceThe build, sim, and fill state of the open slate, and specific built lineups with players and sim metrics
A scheduled buildThe status of a cloud build

A read that is not available for the current sport answers "not available here" with a reason.

What Hero can change

ProposalWhat confirming does
Apply build settingsApplies a full recommendation (stacking, exposure, per-team caps, locks) or single tweaks: lineup count, projection source, selection mode, min uniques, locked or excluded players, player exposures. Needs an open slate with an active build tab.
Apply exposuresSets per-player exposure floors and ceilings, for example "cap Judge at 25%", and boost or dock steps, for example "boost Mahomes two steps".
Run the buildFires the same in-browser build the Build button fires, with the settings you have.
Run the simRuns the simulator on the finished build with your saved sim settings.
Fill entriesFills your entries with the allocation shown in Entries Preview, for the contests switched on in Contest Setup. It writes the same lineups as the Fill button, including over entries another build tab filled. Like the button, it starts Live Sync for that build.
Export CSVDownloads the DraftKings or FanDuel upload file for the latest entry set.
Run late swapRe-optimizes the unlocked slots of entries whose games have not started. Classic slates in NFL, NBA, MLB, NHL, CFB, CBB, WNBA, and soccer.
Open a slateAdds the slate to the tab strip and switches into its workspace.
Create playbookSaves a Playbook with build mode, lineup count, contest type, selection mode, and auto-fill, then opens it in the editor.

Hero never schedules a cloud build. A build from Hero Chat runs in your browser tab, so keep the tab open until it finishes.

How Hero reports a change

  • The card shows Done (Started for a build), Cancelled, or Failed.
  • Details keeps a record of every value Hero sent.
  • Hero's next reply states what changed. Right after a build starts, Hero can only report that the build is running. Ask "Did the build finish? How many lineups are in the pool?" and Hero reads the workspace and answers with the real counts.

After a settings card, open the Build Settings sheet and check every value before you build.

Threads and memory

Every conversation is a thread, named from your first message.

  • The thread switcher in the header holds New thread, Rename this thread, and your recent threads. In a slate workspace the list shows that slate's threads plus threads that belong to no slate.
  • Memory (the brain icon) lists the facts Hero saved from chat, each with a kind such as Preference or Strategy and a delete button. Tell Hero "remember that I only play DraftKings" and it saves the fact for future threads.

Tips

  • Open the slate first. Hero can only change settings and build on the slate that is open in the workspace.
  • Ask for one thing at a time. "Set Smart Randomness to Moderate and max exposure to 40%" gets a clean card. A long list gets a long card that is harder to check.
  • Read the card, not the chat. The card is what runs.
  • Save preferences to Memory once. A saved fact such as "Avoids stacking pitchers with opposing hitters" shapes every future recommendation.
  • Check the Build Settings sheet after a recommendation. Hero may set more than you asked for, such as a stack rule or a team cap.

Troubleshooting

"Which DraftKings slate should I apply this to?" : you sent a settings or build request from the Day View. Click Open on the slate, then send the request again in the workspace.

"That slate is open but has no active build tab, so there was nothing to apply the settings to..." : click New Build in the workspace toolbar, then confirm the card again.

"The user does not have this slate open on the date they are viewing, so nothing was applied..." : the Day View is on a different date than the slate. Move the date picker to the slate's date and open the slate.

"The build did not start (the Build button is disabled..." : the player pool has not loaded, or a build or analysis is already running. Wait, then confirm again.

"No lineups in your entries yet" with "Fill your entries from a build first. Nothing was downloaded." : you asked for an export before a fill. Confirm a Fill entries card first, then export.

"Hero ran into an error" : the reply stopped. Send the message again. If it repeats, start a new thread.

"Recovered from incomplete prior turn." : you closed or reloaded the page while a card was waiting for Confirm. The card shows as cancelled. Send the request again.

"Nothing saved yet. Tell Hero a preference in chat." : the Memory dialog is empty. Tell Hero a preference in plain words and it saves it.

Was this article helpful?