Contact Coral UK Notebook
This contact route serves the Coral UK Notebook publishing desk. Think of it as the margin of the notebook where you scribble questions—except digitally and with GDPR in mind.
Reach us at [email protected]. We merge duplicate threads when readers resend the same correction; no need to spam.
Corrections and game notes
If a review misstates a mechanic—wrong number of decks, incorrect free-spin retrigger rules—tell us. Include the game title, supplier and a link to the in-game help file if available. We may forward supplier questions through official PR, but we never promise fixes on their roadmap.
Reader stories
We appreciate anecdotes about limits that saved a bank holiday budget or UX tweaks that helped colour-blind players. We do not publish identifiable player stories without signed consent. Safer-gambling recovery arcs are handled sensitively; we avoid sensationalism.
Partnerships and creatives
Studios pitching exclusive interviews should propose concrete time windows and embargo terms. Influencers seeking collabs must show ASA-aware disclosure plans. We decline undisclosed gifted spins.
Legal
Formal legal notices should identify jurisdiction, claimant and statutory basis. We forward them to counsel. Informal threats without particulars receive no substantive reply.
Gratitude
Notebook culture depends on readers who annotate. Send your marginalia—we read it.
Social channels
We may operate social accounts with discrete handles. DMs there are not official support; email remains the archive-friendly route for corrections.
Bug bounty boundaries
Security researchers who find vulnerabilities on this publisher domain should report responsibly with reproduction steps. Do not test on live player accounts without authorisation. Casino operator infrastructure is out of scope for our programme.
Student journalists
University projects may request interviews; include your tutor’s contact. We cap student calls to thirty minutes and avoid discussing personal gambling histories.
Compliments file
Positive notes get forwarded to writers’ annual reviews. If someone’s sentence helped you, name the article—we share credit internally.
Rate limits
Automated scrapers hammering our forms may be throttled. Humans should never notice; if your legitimate message bounces, retry after an hour.
Third-party inboxes
Forwarding our replies to Gmail or Outlook is fine; we cannot control their spam filters. Add our domain to safe senders if confirmations vanish.
Meeting requests
In-person coffees happen rarely and only in London or Manchester with two weeks’ notice. Virtual meetings default to Google Meet with captions enabled.
Photography
We do not publish reader photos without signed releases. Casino floor shots may violate house rules—check with security before snapping.
Plain-language pledge
We answer emails at the reading level we use on-site—no legalese unless quoting statutes. If we slip into jargon, call it out and we will rewrite.
Escalation inside our org
Complex complaints route to a managing editor within one week. You do not need to threaten publicity to reach them; just ask for a second review calmly.
Holiday autoresponders
During August bank holidays we may send short autoreplies with realistic return dates. The dates are genuine, not marketing fluff.
Read receipts
We do not use tracking pixels in personal replies. If your client requests read receipts, we may decline for privacy consistency.