by Audra Carpenter

Turn manufacturer emails into service calls and draft replies for your approval

Have Claude Code read the mailbox, turn manufacturer emails into service calls and draft the replies, with anything that has consequences waiting for the owner's approval on his phone.

What the agent did

Source-reported example · as described by Jorge Garzón (dev.to user satgarzon), second-generation owner of a small family car-wash equipment service company in Spain, writing about his own company

The author, Jorge Garzón, second-generation owner of a small family company in Spain that services and repairs car-wash equipment for two large manufacturers and its own customers (a handful of field technicians and one office; he says nobody there is a programmer), built a set of agents on Claude Code and an MCP server alongside the company's own ERP.

The agents read the mailbox, create service calls from manufacturer emails and draft replies; they prepare emails but never send them. Anything with consequences, such as creating a document or sending something, shows up on his phone in Telegram with two buttons for his approval, and every decision is logged (who, when, result).

The tooling requires the agents to consult the company's written procedures before they are allowed to write anything, and a second model from a different company reviews the first model's work and flags disagreements.

Reported: "I review twenty decisions a day from the phone in a few minutes, and nothing surprising ever happens." This figure covers the whole approval loop, not only service calls and replies. No counts of emails handled, service calls created, time saved or accuracy are given for this job.

Limitations

The post is a short overview of the whole system, not a write-up of this job: it gives no examples of a manufacturer email, a created service call or a drafted reply, and no volumes, time saved or error rates for this job.

The 'twenty decisions a day' figure covers every approval, not just this job. The author's first approach let the agents act and report afterwards, and the company lost a day to a batch of work reports "approved" with the wrong prices (a different task, but the reason everything with money now needs a human click).

He says they measured one long working session re-reading hundreds of thousands of tokens on every step, so they switched to one session per topic with a short hand-over note; anything the AI "remembers" in chat but that is not written in a procedure or file "does not exist the next day".

Local models derail on anything longer than a page. The setup is custom-built (own ERP, MCP server, Telegram approvals, about 1,500 written procedures) and the author does not publish code, configuration or prompts. He warns owners to expect to maintain it themselves.

The post describes other jobs (reconciling manufacturer approvals against work reports, preparing supplier orders, a technician Q&A library, the ERP itself) that are not part of this listing. dev.to labels the post 'AI-assisted'.

Try it in your business

What you'll need

Claude Code access; a business system that holds service calls (the author built his own ERP) plus an MCP server or similar connection that lets the agent read the mailbox and create records in it; an approval step on your phone or desktop (the author uses Telegram with approve/reject buttons and a decision log); written procedures the agent must read before it writes anything (the author's company has about 1,500); your own review and approval of every service call and reply before it is created or sent

The agents run on Claude Code through an MCP server connected to the company's own ERP and mailbox, with a custom Telegram approval flow and tooling that blocks writes until procedures are read; this is self-built software, not a packaged app connection.

The original is a custom-built system. The prompt below is a simpler starting point and won’t reproduce it.

Starting prompt

The author didn't publish their prompt, so this is our adaptation.

How ours differs from the original setup: Same execution agent (Claude Code). The author's agents connect to his self-built ERP through an MCP server and send approvals to Telegram; our prompt assumes you point Claude Code at your own mailbox and job system and an approval queue of your choice.

It keeps everything as drafts until you approve, matching the author's rule to "Separate 'propose' from 'do'", and never sends, orders, deletes or changes records. The service-call fields and the reply content are our additions, since the source does not describe them.

Our suggested starting prompt — not the author's original · untested
You help me run the office of my equipment service company. Check the mailbox [mailbox] for new emails from the manufacturers we service for [manufacturer names]. Before doing anything, read our written procedures for handling manufacturer requests [procedures file or folder]. For each email that asks for a service visit, prepare a draft service call (do not save it in [our job or service system] until I approve) with the customer site, machine model, fault reported, manufacturer reference and urgency, taken only from the email; mark anything missing or unclear instead of guessing. Then draft a reply to the manufacturer confirming what we understood and asking for any missing details. Put each draft service call and draft reply in my approval queue [where] with a one-line summary. Do not create, change or close any record, send any email, order parts, or delete anything; I will review and approve each one myself.

Replace the [bracketed] parts with your own files and tools.

Get examples like this every Tuesday and Friday

Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.

Unsubscribe any time. Privacy policy

Report a correction

Related use cases

Run a new client's standard audits and draft the kickoff strategy brief

Have Claude Code run a new client's standard first-week audits and draft a strategy brief with recommended priorities for you to review before the kickoff call.

Claude Code · Operations · Custom development · Source: Alejandro Arce, founder of Arce Consulting (Vancouver), writing about his own consultancy's client onboarding · June 16, 2026

Onboard a new client end to end: draft the contract, set up their Slack channel and podcast feed, and build website mockups for your review

Have Claude run a client-onboarding skill that drafts the client's contract, creates their shared Slack channel, adds them to your client database, and prepares samples, website mockups and a podcast feed for your review, while you send the invites, grant access and write the client messages yourself.

Claude · Operations · Connected apps · Source: Peter Hartree, who runs TYPE III AUDIO (T3A, bespoke AI narration services for the AI safety and effective altruism communities) and calls himself an AI Uplift Consultant; author of the AI Wow journal (wow.pjh.is); describing his own business's onboarding of the client Epoch AI · May 20, 2026

Project inventory and recommend when to reorder each product

Have Claude Code pull inventory and sales data, project the next twelve months of sales and stock by product, and recommend when to reorder each one, using written notes on supplier lead times and holidays.

Claude Code · Operations · Custom development · Source: Alex Willen (acquires and operates Amazon e-commerce brands; author of The Automated Operator) · January 29, 2026