Hermes flags pool-service errors while routes are live

A route manager responsible for more than 400 weekly pool visits describes adding Hermes to processes they had already built. A routing Google Sheet records assignments and filter-clean schedules. A second sheet stores service history, chemistry patterns, reliability context and suspected leaks. Technicians submit live readings, photos, chemicals and actions through the company’s service software.

The manager developed instructions and skills with Hermes, tested them in dry runs and expanded access only after correcting bad assumptions. The resulting QC workflow examines incoming reports while technicians are still on their routes. It flags questionable chemical adjustments, repeated readings, missed actions and inconsistencies with a pool’s history, then contacts the manager through Telegram and the technician through Slack when necessary.

The author reports that a morning brief saves 10–20 minutes and that batch onboarding fell from roughly two hours to 18 minutes. Those timings are personal reports rather than an independent comparison. The useful implementation detail is to supply an explicit routing and QC framework before granting operational access: the agent did not invent the business rules. The account does not prove its chemistry judgments are universally reliable, so flagged reports still require a qualified person’s decision and field follow-up.

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

Source: Reddit · u/andrewtcombs on Reddit