Skip to content

Warranty replies that ask before they offer

A one person store has agents draft every customer email from the full thread and the order history. For a warranty problem the first reply only asks questions, and a hook blocks any draft that promises money or product until the owner approves that exact text.

SupportWorks with Claude Code · Claude Desktop with MCP+1Community example

What it does

  • Reads the whole email thread and the customer's orders from the store
  • Drafts a short, plain reply in the owner's voice inside the existing thread
  • For warranty claims, asks diagnostic questions first and never offers a replacement up front
  • Lists anything that costs money on its own line in the draft
  • Texts the owner a 9 AM summary of the day's orders and waiting emails

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending any email, only when the owner says send
  • Any promise of a refund, replacement or credit
  • Any order change the customer would see

You decide what happens next.

More about this workflow

This setup is for support leads and small teams who answer customers every day. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads the whole email thread and the customer's orders from the store. Next, it drafts a short, plain reply in the owner's voice inside the existing thread. Then it for warranty claims, asks diagnostic questions first and never offers a replacement up front. After that, it lists anything that costs money on its own line in the draft. Finally, it texts the owner a 9 AM summary of the day's orders and waiting emails. It works with your email, store admin and shipping app, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending any email, only when the owner says send, any promise of a refund, replacement or credit and any order change the customer would see, and says plainly if a step cannot be undone.

“An email only goes out when I literally say send.”
nicedreamzapp nicedreamzapp on GitHub · Oct 8, 2026
Before you startEmail · Store admin accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

  • Shopify

    Handles the store admin part of this job. Grant read orders and products.

    API required: Yes. Needs a Shopify app with an access token and the admin scopes you approve.

  • ShipStation

    Handles the shipping app part of this job. Grant read order and shipment status.

    API required: Yes. Needs API credentials from your ShipStation account settings.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Writes careful replies and reads long ticket threads.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Made for sorting and routing at high volume.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. WooCommerce

short and plain, or your own examples

what to ask before offering anything

2Your prompt

4 of 4 still empty
Fill these in before you run it: [STORE PLATFORM: e.g. WooCommerce] [VOICE NOTES: short and plain, or your own examples] [WARRANTY QUESTIONS: what to ask before offering anything] [BRIEFING TIME] You are the Warranty replies that ask before they offer agent. A one person store has agents draft every customer email from the full thread and the order history. For a warranty problem the first reply only asks questions, and a hook blocks any draft that promises money or product until the owner approves that exact text. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads the whole email thread and the customer's orders from the store - Drafts a short, plain reply in the owner's voice inside the existing thread - For warranty claims, asks diagnostic questions first and never offers a replacement up front - Lists anything that costs money on its own line in the draft - Texts the owner a 9 AM summary of the day's orders and waiting emails What you must never do without a yes from a person: - Sending any email, only when the owner says send - Any promise of a refund, replacement or credit - Any order change the customer would see Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  2. 2Connect Shopify with its own login, not yours. Grant read orders and products.
  3. 3Connect ShipStation with its own login, not yours. Grant read order and shipment status.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: sending any email, only when the owner says send, any promise of a refund, replacement or credit, any order change the customer would see.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Warranty replies that ask before they offer](https://trustcase.dev/badge/warranty-replies-that-ask-before-they-offer.svg)](https://trustcase.dev/use-cases/warranty-replies-that-ask-before-they-offer)
HTML
<a href="https://trustcase.dev/use-cases/warranty-replies-that-ask-before-they-offer"><img src="https://trustcase.dev/badge/warranty-replies-that-ask-before-they-offer.svg" alt="Trustcase trust score for Warranty replies that ask before they offer" height="20"></a>
  • Ticket triage

    Sorts new tickets by topic and urgency so the right person sees them first.

  • Reply suggester

    Drafts answers to common questions using your help docs.

  • Refund checker

    Checks refund requests against your policy and lays out the facts.

  • Help doc gap finder

    Spots questions customers keep asking that your docs do not answer.

Other workflows that use the same tools