A practical look at shared inboxes for an accountant

We billed an accountant two hours for shared inboxes. The previous agency billed forty hours and left TTL of 300 seconds behind. Complexity is not expertise.

The vendor promised an accountant that shared inboxes was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.

an accountant did not need a portal. They needed a page that said who they are, what they do, and a phone number that somebody picks up before the fifth ring.

The chain of trust for shared inboxes starts at the registrar. If the registrar account uses an email nobody reads, every downstream fix is temporary.

We told an accountant that TTL of 300 seconds was a ticking clock. They agreed to fix it the same week — which is rare. Most clients wait until it actually detonates.

The most expensive outage for an accountant was not a hack — it was TTL of 300 seconds. Nobody attacked anything. The config just drifted.

We do not start with a platform when handling shared inboxes. We write down who types what, who gets the mail, and what must not get lost. That list is always shorter than a vendor pitch deck.

More notes

Related notes

• shared inboxes: a field note from a restaurant
• Why shared inboxes matters for a florist
• Managing shared inboxes at a veterinary clinic
• How a roofing crew should handle shared inboxes