Keeping a one-day closure in the menu routine
A Sunday closure in Cindy’s menu post also needed to reach Google’s opening hours. I asked AI to keep that connection in our weekly publishing instructions.
On 28 October, I pointed out that the menu had no Sunday pickup. Cindy’s Facebook post said we would be closed that Sunday, and I asked the agent to carry that information over to Google. I specified the upcoming Sunday only, because we had something else to do that day. I wanted someone checking our hours to see the change before making the trip.
That Sunday was 1 November. The agent added a closed entry for that date in Google’s special hours, then reopened the settings to check it. Our regular weekly hours and the existing special dates stayed as they were. The Sunday row also showed Closed in the search view checked through our signed-in account. That was the visibility we had verified at the time.
We had used special hours before, and had already added Google posts to our menu workflow. This time I wanted the connection between a menu notice and the hours field to be remembered. On 29 October, I asked AI to add it to publish-menu, the written instructions the agent follows when publishing a weekly menu. An explicit temporary-closure notice in the Facebook menu should also prompt a change to the matching special date.
The instructions had to distinguish a closure notice from a missing menu day. A day with no dishes listed does not by itself say the shop is closed. The date also has to come from the week named in the menu. If its last pickup is Friday, a Sunday closure notice can still belong to that same menu week. Those details determine which date the agent should change.
The updated instructions say to inspect the current hours first, keep the regular schedule and unrelated special dates, and avoid saving the same closure again if it is already correct. They also separate posting a notice from changing the hours field. After a change, the agent should reopen the saved entry and check the customer-facing view where the date is visible. A pending review must remain pending in the report.
I approved the change to those instructions on 29 October, and it was merged. That step updated two workflow documents; it did not make another change to Google’s hours. We still had to see the rule used on a future menu run. For now, the one-day correction had a place in the weekly process, with its date, source and checks written down.
