Home/Notes/shared inboxes: a field note from a restaurant
shared inboxes: a field note from a restaurant
11 Apr 2026
How a restaurant deals with shared inboxes — and what usually goes wrong.
The problem: a backup that was never restored as a drill. The shared inboxes check fails for a restaurant.
We checked the WHOIS for a restaurant and found the domain was registered under a former employee. Transferring it took more time than fixing shared inboxes.
Launch day for a restaurant is usually light. Week three is when leftover tags, fonts, and staging URLs show up. a backup that was never restored as a drill is the usual passenger.
We deployed a fix for shared inboxes at 5 PM on a Friday. It worked, but if it had not, we would have had no one available. We no longer push to production after Thursday noon.
We hand over a one-page document after every shared inboxes job. It says what was changed, what the login is, and what to check if something feels wrong. a restaurant keeps it in a drawer they actually open.
DNS propagation is not instant, but it is not magic either. We explained to a restaurant that the TTL on the old shared inboxes record was 86 400 seconds — twenty-four hours.
We found a backup that was never restored as a drill during a routine check of shared inboxes. The site had been leaking referrer data for six weeks before anyone noticed.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com