Read this page once. Internalize it. Forget it at your peril.
The mechanic
Tablevoice keeps your saved configuration and your live configuration as two separate states. This is on purpose — it lets you draft changes, review them, and push them live in one explicit step. It also means you can't accidentally make Foodie say something weird because of a half-finished edit.
Saving
Click Save Changes (purple button, bottom-right of any config page).
Your edits are stored.
Foodie's behavior does not change.
A blue banner appears at the top of the AI Host page: "Publish Agent."
Publishing
Scroll to the top of the AI Host page. Click Update Agent in the blue banner.
Your saved edits become live.
The next call Foodie answers reflects them.
The blue banner disappears.
Why we did it this way
You can review before deploying. Edit hours, edit menu, double-check, then push live.
You can stage edits across a day and publish all at once at end of shift.
You can't accidentally roll out a partially-done change mid-service.
Why this trips everyone up
The Save Changes button is purple and obvious. The Update Agent button is at the top of the page, in a banner you might not notice.
The blue banner uses gentle colors. Looks informational, not action-required.
After saving, you might navigate away and assume changes are live.
What it looks like when you forget
You change Hours. Save. Navigate away. Foodie keeps quoting old hours for hours, days, weeks. Your team blames Foodie. The fix: you forgot the second click.
A guest calls about a holiday closure. Foodie books them anyway. You added the holiday exception last week, but never clicked Update Agent.
Build the muscle
For the first month, before you save anything, mentally check: "Am I going to remember to publish?" Then save. Then immediately scroll up and publish. By month two, the two-click pattern feels native.
Some venues add a sticky note to the iPad: "After save: scroll up, click Update Agent." It looks silly. It works.
What about §3.1 changes (knowledge fields)?
Same mechanic. Save Changes on a §3.1 page like Hours doesn't push live until you click Update Agent on the AI Host page. The button is centralized.
What about §3.3 (playbooks)?
Same.
TL;DR
Two clicks. Every time.