GoDaddy Airo Inbox: Recheck Chat After You Change Business Hours
When you update business hours on a site built with GoDaddy Airo AI Builder, the safest way to test the optional AI agent is to verify the live public page after the change has been published. GoDaddy’s November 2026 Airo AI Builder product update describes published site content as the source the AI agent uses, so a saved draft and a published page are not the same thing for support verification.
Why saving is not the same as publishing
If you save new hours in the builder without publishing the change, the old hours can still be visible to customers. Start by updating the hours, publishing the change, and checking the live page. Then test whether the chat response matches what customers can read on the site.
GoDaddy also distinguishes Airo AI Builder from Airo for WordPress in its help documentation, so make sure you are checking the right product before troubleshooting. The workflow in one product should not be assumed to apply to the other.
November 2026 Airo AI Builder product update
GoDaddy launch announcement from November 16, 2026
Help article on the difference between Airo AI Builder and Airo for WordPress
A simple support check after changing hours
A useful example is changing a business from Thursday 6 p.m. close time to 5 p.m. close time in the business’s local time zone. If that change affects a public hours mention elsewhere on the site, update the conflicting public reference too. Then publish the page so the live site reflects the current hours.
After publishing, open the live site in a clean browser session with the widget visible. Use a neutral visitor question that does not include private details, such as asking what time the business closes on Thursday. Compare the exact answer against the newly published hours. If the reply still shows the old time, note the misbehavior, correct any remaining contradictions, and publish again as appropriate.
If the answer is still wrong after you have confirmed the public page is correct, use a human reply in Inbox to follow up while you continue troubleshooting. That keeps the customer experience accurate even when the optional AI agent is not yet aligned with the updated page.
What not to assume during verification
- Do not assume a saved draft has already reached the public site.
- Do not assume the chat response will refresh instantly after an edit.
- Do not assume every page or mention has been ingested at the same time.
- Do not assume this behavior is identical across Airo AI Builder and Airo for WordPress.
- Do not assume access to phone, AI voice, or full telephony features outside the U.S. if you are comparing capabilities; GoDaddy says those are U.S.-only, while site chat and contact forms can be published where the product supports them.
Practical support takeaway
For customer support teams, the most reliable order is: edit the public fact, save, publish, confirm the live page, test the chat from a clean browser, and then decide whether the AI answer matches the current site content. If it does not, document the mismatch clearly, remove conflicting public references, and republish before escalating or continuing with a human reply in Inbox.
