Support

Build a customer support agent in an afternoon

An agent can read your helpdesk, draft every reply in your brand voice, and flag the ones that need you. Here is the exact setup I use in my own store.

Why this works now

Your replies are a pattern, not a mystery

Most support tickets in an ecommerce store are variations on the same dozen questions: where is my order, can I change my address, do you ship here, how do returns work. You already answer them the same way every time. That is exactly the kind of work an agent is good at.

With Claude Code connected to your helpdesk, an agent can read the open tickets, draft a reply for each one in your voice, and leave anything sensitive or unusual for you to handle. You go from an inbox of 40 to a short list of 3 that actually need a human.

What you'll need

Claude Code, a helpdesk the agent can read (Gorgias, Gmail, or similar), and 20 minutes. No code, and nothing gets sent without your say-so on the first run.

The setup

Three steps to your first drafts

01

Give it your voice

Paste five of your own past replies into a short brand-voice note. That is all the agent needs to stop sounding like a robot.

02

Point it at the inbox

Connect your helpdesk so the agent can read open tickets and the customer's order history for context.

03

Review the drafts

The agent drafts a reply per ticket and flags the tricky ones. You skim, tweak, and send. After a week you will trust it with the easy ones on autopilot.

The catch

Keep a human on the hard ones

Refunds outside policy, angry customers, anything legal: those stay with you. The point is not to remove yourself, it is to stop spending your morning on copy-paste so you have time for the replies that actually matter.

Want the exact prompts?

They're in the free Store Audit Prompt Pack, along with the rest of my agents. Drop your email and I'll send it over.

← All guides