What a bonus code usually means
A bonus code is a short string the reader enters during sign-up or first deposit. The reading-room desk's note is that bonus codes usually come with conditions: a minimum deposit, a playthrough requirement, an expiry window and a stake band. A careful reader reads the conditions before entering the code.
This page describes what bonus codes usually mean, what they usually require, and the things an adult reader checks before using one. The reader who has read this note has read the most useful bonus-code note.
What a bonus code usually requires
Most bonus codes require three things. First, a minimum deposit, often set at the same band the app recommends for first-time players. Second, a playthrough requirement, often expressed as a multiple of the bonus. Third, an expiry window, often 7 to 30 days.
Three things to read first
- The minimum deposit
- The playthrough multiple
- The expiry window
The reading-room reader who has read all three has read the most useful bonus-code conditions list.
What the playthrough means
A playthrough multiple is the number of times the bonus must be played through before it can be withdrawn. The reading-room desk's note is that a higher playthrough multiple means the reader is more likely to lose the bonus before clearing it. A careful reader sets the playthrough multiple against the stake ceiling they have already set.
An example
- A 100% bonus on a 500 rupee deposit with a 5x playthrough means the reader must play through 2,500 rupees before the bonus can be withdrawn
- The reading-room reader who has read the example has read the most useful playthrough note
The stake ceiling and the bonus
The desk's recommendation is to set the stake ceiling before entering the bonus code. A reader who has set a stake ceiling is the reader who has read the most useful responsible-play page. A bonus code that pushes the stake ceiling above the reader's own ceiling is a bonus code the reader should not use.
What to read next
The routes that pair well with this one are the responsible-play guide, the safety explainer and the reviews. The reading-room reader who has read all four has read the full bonus-code spine.
Why a bonus code is a short piece of writing
A bonus code is a short string the reader enters during sign-up or first deposit. The reading-room desk's note is that the short string comes with a longer paper trail: the conditions the publisher publishes, the playthrough multiple, and the expiry window. A careful reader reads the longer paper trail before entering the short string.
The reader who has read the conditions has read the most useful bonus-code note.
Three things to read before entering a code
- The minimum deposit
- The playthrough multiple
- The expiry window
When not to use a bonus code
The desk recommends declining a bonus code in three situations. First, when the playthrough multiple exceeds what the reader is willing to play through. Second, when the expiry window is shorter than the reader's typical evening. Third, when the bonus code would push the stake ceiling above the reader's own ceiling.
The reader who has read these three situations has read the most useful decline list.
What to read next
The routes that pair well with this one are the responsible-play guide, the safety explainer and the reviews. The reading-room reader who has read all four has read the full bonus-code spine.
What does not change when a code is entered
The rules do not change when a bonus code is entered. The KYC requirements do not change. The responsible-play tools do not change. The reading-room desk's note is that a bonus code is a short string with conditions, not a content change. The reader who has read this note has read the most useful description of what does not change when a code is entered.
The desk's read is that the stake ceiling the reader has set also does not change when a bonus code is entered. A reader who has set a stake ceiling and entered a bonus code has read the most useful responsible-play practice.
- The rules do not change when a code is entered
- The KYC requirements do not change when a code is entered
- The responsible-play tools do not change when a code is entered
- The stake ceiling the reader has set does not change when a code is entered
The reading-room reader who has read this list has read the most useful description of what does not change when a code is entered.
What the reader checks after entering
After entering the code, the reader checks the bonus credit has been applied. The reader also checks the playthrough progress under the bonus section. The reader who has checked both has read the most useful post-entry check.
What to read next
The routes that pair well with this one are the responsible-play guide, the safety explainer and the reviews. The reading-room reader who has read all four has read the full bonus-code spine.
A short reading-room reading list
The reading-room routes that pair well with the bonus-code note are the responsible-play guide, the safety explainer and the reviews. The reader who reads all four has read the full bonus-code spine. The bonus-code reader who has not visited the responsible-play guide is the reader who has skipped the foundation.
The desk's read is that the bonus-code reader revisits the bonus-code note when a code is to be entered. The reader who has done both has read the most useful version of both.
Three reading habits worth practising
- Re-read the bonus-code note before entering a code
- Re-read the responsible-play guide once a quarter
- Re-read the safety explainer once a month
What to read next
The routes that pair well with this one are the responsible-play guide, the safety explainer and the reviews. The reading-room reader who has read all four has read the full bonus-code spine.
What the desk reads when it revisits this note
When the desk revisits this note on the quarterly review cycle, the desk reads the page against the source and against the reader's likely intent. The reading-room note is that the page is more useful when it has been read at least once by the reader before the revision; the reader who has read a page once has read the most useful baseline. The reader who revisits a page after a quarter has read the most useful updated version.
The desk's read is that the quarterly review also creates a small archive of dated revisions. The reader who has revisited a page after several quarters has read the most useful arc of the page. The desk publishes a dated note at the foot of every page when a revision has changed the content. The reader who has read the editorial standards page has read the most useful description of how the desk handles revisions.
The desk reads every page against the same three criteria. First, accuracy against the source. Second, plain-language writing without jargon. Third, adult-reader framing, no promotional language. A page that meets all three criteria on the quarterly review has read the most useful test. A page that fails one of the three has read the most useful reason for a revision.
What the desk does not revise
- The desk does not revise the URL of a page once it has been published
- The desk does not revise the publication date of a page without noting the revision
- The desk does not revise the editorial voice of a page without noting the revision
- The desk does not revise the page structure without noting the revision
The reading-room reader who has read this list has read the most useful description of what the desk does not revise.
How the desk handles reader feedback
The desk reads every message sent to the contact page. The desk replies within a week to messages that include a name, a return address and a clear subject. The desk publishes a dated correction note at the foot of a page when a verified error has been reported. The desk's read is that a feedback message with a dated source is more useful than a feedback message without one; the reader who has included the source has read the most useful feedback format.
The desk also reads the messages for patterns. A pattern the desk has noticed in reader feedback is the request for more practical examples; the desk responds by adding more examples in the next quarterly review. The reading-room reader who has written a feedback message with a specific example has read the most useful contribution to the next quarterly review.
Three kinds of useful feedback
- A correction with a dated source
- A practical example that illustrates the page's content
- A suggestion that links the page to a related page in the room
The reading-room reader who has included one of these three has read the most useful feedback format.
What the reader should expect on the next quarterly review
The reader should expect a small update to the page's content. The desk publishes a dated note at the foot of the page when the update has changed the content. The reader who has revisited the page after the quarterly review has read the most useful updated version. The reader who has read the editorial standards page has read the most useful description of how the desk handles updates.
The desk's read is that the quarterly review is also a useful opportunity for the reader to revisit related pages. The reader who has revisited the related pages has read the most useful full route. The reader who has read all three related pages has read the most useful reading-room spine for this route.
What to read next
The routes that pair well with this one are the responsible play note, the safety note and the reviews note. The reading-room reader who has read all four has read the full bonus code spine.