BaseballBetting.us is run by a small editorial desk, and every message we receive is read by a person who works on the site. The quickest way to reach us is by email at [email protected]. That is the only contact channel we use: no phone line, no chat widget, no social inbox.
Before you write, it may help to check the glossary or the about page, which explains how our data is built. A lot of questions about why a number looks a certain way are answered there. If not, send the email anyway.
What to write to us about
Corrections. If a guide gets a rule wrong, a calculation does not add up or a definition is unclear, tell us. Please include the page link and the sentence or number you think is wrong. “The run line example on the calculators page seems off” is hard to act on; “the $50 at +130 example says $110 returned but I get $115” can be checked in two minutes.
Data questions. Our tables come from the MLB Stats API and rebuild daily. If a probable starter on the probable pitchers board looks outdated, a team’s rate on the NRFI page seems off, or a table shows an update time that is more than a day old, let us know which table, which team and what you expected to see.
Feedback and topic requests. Tell us which markets you want explained, which parts of a guide were confusing and what you would like our calculators to do. Several of our pages exist because a reader asked for them. We read every suggestion, even if we cannot build all of them.
Our corrections policy
We treat factual errors as the most important thing in the inbox. When a reader reports a mistake, we check it against the official source: the MLB rules for how games settle, the MLB Stats API for data, and plain arithmetic for anything involving prices. If the report is right, we fix the page and update its revision date. If a table was wrong because of a data problem, we fix the cause, not just the one number.
We do not quietly rewrite a page to hide an error. Where a correction changes the meaning of a section, the page is updated so that the corrected version is clear. We also reply to tell you what we changed, or why we think the original was correct. Sometimes a report turns out to be a difference in house rules between betting apps, and in that case we usually add a line explaining the difference, because the next reader will probably have the same question.
When to expect a reply
We work US business days and keep our schedule in Eastern Time. We aim to reply within two to three business days. Correction reports and broken data tables are checked first, usually within one business day. Messages sent on a weekend or a federal holiday are picked up the next business day.
During the busiest parts of the season, such as opening week and the postseason, general feedback can take longer. Corrections do not wait.
What we cannot help with
A few requests we have to turn down, however politely they are asked.
We cannot help with sportsbook accounts. We are not a betting operator, we have no partnerships listed on our pages and we cannot see or change anything in your account. Questions about deposits, withdrawals, identity checks, limits or a disputed bet belong with the customer support of the app you use, or with your state’s gaming regulator if support does not resolve it.
We also do not give picks, personal betting advice or predictions for specific games. We can explain how a market works, what a line means on the baseball betting lines page, or how to read a table, but we will not tell you what to bet. That is a firm line, not a matter of time.
Where to get gambling help
If betting has started to cost more than you planned, in money or in time, you do not need to email us first. Call 1-800-GAMBLER for free, confidential help that is available 24 hours a day. Sports betting is legal only where states regulate it and is limited to adults 21 and older in most states. Most betting apps also offer deposit limits, cool-off periods and self-exclusion; you can ask their support to set those up.
For everything else, the home page links every guide and data table on the site.
