AI chatbot on your website: when it pays off and when to skip it
A chatbot helps when your site already holds the answers and someone checks its work. What a tribunal and state laws say about wrong answers.
If your invoices, quotes or contact form messages land in spam, the usual cause is that your domain does not prove the mail came from you. Three DNS records supply that proof: SPF, DKIM and DMARC.
Gmail, Yahoo and Outlook.com require them from large senders and send unauthenticated mail to spam or reject it. You can check your own domain for free today.
Google's email sender guidelines have applied since February 1, 2024 to anyone who sends to personal Gmail accounts. Yahoo's sender requirements came into force the same month, with enforcement rolled out gradually. Microsoft's announcement for Outlook.com, which covers outlook.com, hotmail.com and live.com addresses, set enforcement to start on May 5, 2025.
| Gmail | Yahoo | Outlook.com | |
|---|---|---|---|
| Every sender | SPF or DKIM. Spam rate below 0.3%. | SPF or DKIM. Spam rate below 0.3%. | No minimum stated. Enforcement targets large senders first. |
| Large senders | SPF and DKIM. A DMARC record, which may be set to none. From domain aligned with SPF or DKIM. One-click unsubscribe on marketing mail. | SPF and DKIM. A DMARC policy of at least p=none. From domain aligned with SPF or DKIM. One-click unsubscribe on marketing mail. | SPF and DKIM must pass. DMARC of at least p=none, aligned with SPF or DKIM. |
| Who counts as large | Close to 5,000 or more messages to personal Gmail accounts in 24 hours. | No number given. | More than 5,000 emails a day. |
Google's sender FAQ adds two details that catch growing businesses. Google counts all mail from the same primary domain toward the 5,000. A sender that reaches it once stays classed as a bulk sender permanently.
The FAQ also says Gmail has been ramping up enforcement since November 2025, with non-compliant mail facing temporary and permanent rejections. Microsoft's April 29, 2025 update says Outlook.com rejects mail from high-volume domains that fail the checks, with the error "550 5.7.515".
You probably send far fewer than 5,000 messages a day. Set up all three records anyway.
Google recommends that every sender does, and warns that unauthenticated messages "might be marked as spam or rejected." Your newsletter service, invoicing tool and website each send mail in your name, and any one of them can be the gap.
Authentication does not rescue mail that people report as spam. Google tells senders to keep their spam rate below 0.1% and never let it reach 0.3%.
First, look up the records. Our own ShowMyIP site has a free DKIM, SPF and DMARC lookup. Enter your domain and it shows which records exist and what your DMARC policy is.
Your email provider files your DKIM record under a label called a selector. Leave that box empty and the tool tries the common ones.
Second, test a real message. Send an email from your business address to a personal Gmail account, open it, and click the down arrow under the sender's name.
Gmail's help page says the message is authenticated if you see a "mailed by" line with the domain name and a "signed by" line with the sending domain. Repeat the test with your contact form, your invoicing tool and your newsletter service, because each one sends on its own.
You add these records at your domain provider, the company that manages your domain's DNS. Each email service's help pages give the values to add.
A DMARC policy of none leaves delivery alone. Google's rollout guide says messages are "delivered normally" at this setting, with no risk of rejection. Meanwhile the reports show you every source sending as your domain and whether it passes.
Google's starting record looks like this, with your own address in place of the example:
v=DMARC1; p=none; rua=mailto:[email protected]
The reports are where forgotten senders turn up: a booking system, an old web host still sending form mail. Jump to quarantine or reject before you have fixed them and those messages go to spam or vanish. Google's caution on reject is that failing messages are "never delivered."
Google suggests at least a week at none, then quarantine for a small share of mail, raised over time. Microsoft advises the same path: none, then quarantine, then reject.
Gmail, Yahoo and Outlook.com all accept p=none for their requirements, so the reason to tighten is to stop other people forging your domain. Take it at your own pace. Send the reports to a dedicated mailbox or a DMARC reporting service, because they arrive daily.
A website contact form is often set up to send each enquiry "from" the visitor's own address, so that you can hit reply. Your web server then sends mail that claims to come from gmail.com or yahoo.com.
Your server is not on those domains' lists of approved senders, so the message fails the checks. Google's guidelines tell senders not to impersonate Gmail From addresses, and say Gmail's DMARC quarantine policy may affect delivery of mail that does. The enquiry lands in your spam folder, or nothing arrives.
The fix is two fields. Contact Form 7's guide to setting up mail says: "in the From field, use an email address that belongs to the same domain as the site."
Put the visitor's address in Reply-To, so your reply still goes to them. Then confirm that the server or mail service your website sends through appears in your SPF record and signs with DKIM.
If mail from your domain began landing in spam overnight, check your website as well. A hacked WordPress site can send spam from your server without changing a single page.
HattanMedia builds websites and runs ShowMyIP. If you want us to look at your records or your contact form, see our email marketing page or contact us.
A chatbot helps when your site already holds the answers and someone checks its work. What a tribunal and state laws say about wrong answers.
An AI builder is the right answer for a simple site this week. Here is where it stops, and what a freelancer or an agency adds.
What Google says affects local ranking, how to set up each part of your Business Profile, and the mistakes that get a profile suspended.