Anatomy of a Support Inbox

ℹ️ TL;DR One email address, support@locallygrown.net, quietly turned into a pipeline that reads, sorts, and drafts replies before I ever see a message: it skips the noise, runs a spam gate that fails open, untangles forwarded threads to find the real sender, figures out which market they belong to (with a plain-English database as backup), and hands the whole thing to Sage, the same expert agent my market managers already trust. A recent branch even watches DMARC reports for anyone sending mail as me — and caught a “forger” that turned out to be a customer’s security scanner. Every stage ends in a human decision, on purpose. The machine reads and drafts; I decide. For years, support@locallygrown.net was just an inbox I dreaded. Mail came in — a grower who couldn’t log in, a customer whose eggs never showed up at pickup, a market manager with a policy question, and in between all of it, an unrelenting drizzle of SEO pitches and “I noticed your website could rank higher.” Every message…