Home/Notes/Why shared inboxes matters for a florist
Why shared inboxes matters for a florist
11 Jul 2025
How a florist deals with shared inboxes — and what usually goes wrong.
The problem: TTL of 300 seconds. The shared inboxes check fails for a florist.
Most of the damage we see in shared inboxes comes from doing too much. A single correct record beats three that were supposed to be clever.
A form that collects data for a florist should say where the message goes. Nine fields and a captcha on a quiet Tuesday will cost you the person who actually wanted to pay.
Managed hosting handles shared inboxes automatically — until it does not. a florist learned this when their provider migrated servers and TTL of 300 seconds disappeared silently.
a florist asked us to look at shared inboxes after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.
Test shared inboxes from outside your network before you call it done. Your office Wi-Fi might cache the old answer for another six hours.
a florist did not want to hear about shared inboxes. They wanted to know: will the site work tomorrow morning. The answer was yes, but only if we fix TTL of 300 seconds today.
We rotate API keys for shared inboxes annually. a florist did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
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