Not Receiving Email Notifications After Someone Submits a Form on My Website

[JGorske]

Hi there!

I am not receiving email notifications when people submit forms on my website. There's 2 spots they can submit them. 

Here, on our team building page. 

Or, here on our contact us page. 

I have them set up to send to my email address under the form settings.

I've tried another email address, and that didn't work.

I tried to create a new contact us form, but when I hit publish, my website doesn't update. I tried seeing it from multiple devices and browsers, but it didn't update within the 10 minutes I was trying.

I changed website hosts a few months back (from GoDaddy to Blue Host), and that's when I stopped receiving email notifications.

I went through the automatic connection from Square to Bluehost on 1/3/25 to see if that would update the connection, but it didn't fix it.

Square Customer Support wasn't able to help me, and when I contacted Google they said the form probably isn't initialized or configured properly because Gmail isn't getting emails (they're not even hitting the Google server). 

Does anyone have a fix for this? It would be GREATLY appreciated!

[JJ_]

Hello there @JGorske 👋

The quickest and best way to resolve this is to call Square Customer Success.  Someone there can look over your account and determine if this needs to be escalated to an engineer.

Can you determine if you used to get these emails, and they just quit?  Look into your email history because this information will be helpful in tracking down the issue.  

Also, though I’m sure you’ve done this a thousand times, maybe try changing the email address for the form to an email not from Gmail, as a test and see if they start up again.  If they do, then maybe changing the address back fixes things.

[BA123]

Hi! Did you find a solution for this? We are having the same issue....

[JGorske]

It took a lot of phone calls, but eventually someone from Square was able to help. They had to toggle something on in the back end to get it fixed. It was a Square issue.