Hermes triages collectibles email and stock alerts

GeekTekRob describes a Hermes deployment for a small family collectibles business. The assistant runs continuously on a VPS and connects to the business’s email and inventory system. The author frames the setup around the shop’s actual workflow: sales are packed manually at particular times, while questions and urgent issues need attention sooner.

Hermes scans incoming sales messages and enquiries, provides an email rundown and gives priority to items needing an immediate response. It also reads a changing inventory of more than 4,000 SKUs. The account describes support for building bundles, checking prices, low-stock alerts on reusable items and lists of price changes awaiting approval. The assistant therefore connects communication and stock context, while the owner retains the packing process and pricing decisions.

The reported outcome is an operating support layer, not a measured increase in sales or an independently tested inventory forecast. The comment gives hosting and model costs for that business, but expressly warns that the same model choice may not suit another team. A useful adaptation starts with the order-processing schedule and the inventory fields that matter, then makes alerts actionable. Price changes should arrive as a reviewable list instead of automatically rewriting the catalogue.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/GeekTekRob on Reddit