Customer Support

How to process refund and return requests as DTC Brand Founders

Customer SupportFor DTC Brand Founders2 apps12 steps~24 min to set up

Refund and return requests pile up in your Shopify admin, your support email, and occasionally a DM on Instagram — all in different places, none talking to each other. You're manually checking order status in Shopify, cross-referencing whether the item was actually delivered, then typing the same 'we're so sorry, here's your refund' response for the fourth time that day. Meanwhile you have no idea whether your return rate on that new colorway is 18% or 35%, because that data lives inside Shopify reports that don't connect to your ad spend or your reorder model. Every refund you issue is a guess about whether it's worth fighting or just approving.

Build this on Starch → See the apps used

Customer SupportFor DTC Brand Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A refund-request triage system that pulls Shopify order data, flags high-value customers and repeat returners automatically, and drafts responses you can send in one click from your inbox

A returns dashboard that shows your return rate by SKU, by acquisition channel, and over time — so you know whether your Meta ad creative is attracting the wrong buyer before it wrecks your margin

An automation that logs every approved refund back to a running ledger and alerts you when a single SKU's return rate crosses a threshold you set

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM

Data sources & config

Connect Shopify from Starch's integration catalog — the agent queries it live when the triage app runs and when the dashboard refreshes. Connect Gmail as a scheduled-sync provider — Starch syncs your inbox on a schedule so the triage automation has messages ready to process. Connect Slack from Starch's integration catalog for threshold alerts. If your returns portal runs on a third-party site with no API (like a branded loop returns page), Starch automates it through your browser — no API needed.

Prompts to copy

Build me a refund triage inbox that reads my Gmail for emails with subject lines containing 'refund', 'return', or 'damaged'. For each, look up the order in Shopify using the customer's email, check whether it was delivered, pull the customer's lifetime order count and total spend, and draft a reply: approve automatically if LTV is over $300 or the order is under $40, otherwise flag for my review with a one-sentence summary of the situation.

Build me a returns dashboard that pulls from Shopify and shows: return rate by SKU this month vs last month, return rate by traffic source (use UTM data from Shopify orders), average days between delivery and return request, and total refund dollars issued in the last 30 days. Alert me in Slack if any SKU's 7-day return rate exceeds 20%.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Gmail to Starch as a scheduled-sync provider. Starch syncs your inbox on a schedule and stores messages so the triage automation can run even when you're not actively logged in.

2 Connect Shopify from Starch's integration catalog. The agent queries it live: order status, delivery confirmation, customer email, LTV, and UTM source all come back in real time when a refund request comes in.

3 Open the Email Triage app from the App Store and fork it for your returns flow. Tell Starch: 'Filter for emails about refunds or returns. For each, look up the Shopify order, check delivery status, and pull the customer's order history.'

4 Set your auto-approve rules in plain language: 'If the item shows as undelivered, approve the refund and send the customer a replacement offer. If LTV is over $300, approve and add a $10 credit. Otherwise draft a response for my review.'

5 Wire the draft-and-send step to Gmail so approved responses go out automatically and flagged ones land in a review queue you can clear in under five minutes each morning.

6 Build the returns dashboard by describing it to Starch: 'Show me a table of return rate by SKU, sorted highest to lowest, for this calendar month. Add a column for last month so I can see the trend. Pull from Shopify orders with a refund or return tag.'

7 Add an acquisition-channel breakdown: 'Break down return rate by the UTM source on each original Shopify order. I want to see whether my Meta traffic returns more than my email traffic.' This is the column that will change how you write your next ad brief.

8 Set a Slack alert automation: 'Every morning at 8am, check whether any SKU has a 7-day rolling return rate above 20%. If yes, send me a Slack message listing the SKU, the return rate, and the top reason given in return request emails.'

9 Add the approved refund logger: 'Every time a refund is approved through the triage app, log it to a running table with: order ID, SKU, refund amount, reason, customer LTV, and whether it was auto-approved or manually approved.' This becomes your monthly returns ledger.

10 Set a monthly summary automation: 'On the first of each month, pull the previous month's returns ledger, calculate total refund dollars, average refund per order, and the three SKUs with the highest return rates. Send me a Slack summary and add a row to my investor reporting table.'

11 If you use a third-party returns portal, describe it to Starch: 'Log into my returns portal every morning, pull any new return requests submitted in the last 24 hours, and add them to the triage queue.' Starch automates the portal through your browser — no API needed.

12 Once the Customer Support Agent launches (coming soon), route first-contact refund emails there for fully automated resolution. Today the Email Triage app handles the drafting; the Support Agent will close the loop end-to-end.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 returns spike — new jogger colorway

Sample numbers from a real run

Refunds issued — jogger (slate colorway)	4,800
Refunds issued — all other SKUs	1,200
Triage emails processed (auto-approved)	61
Triage emails escalated for review	14
Avg founder time per refund before Starch (minutes)	8
Avg founder time per refund after Starch (minutes)	1

In February 2026 you launched a slate-grey jogger that performed well on Meta — 3.4x ROAS, strong add-to-cart. By March 10th you had 61 refund emails in Gmail and no idea whether it was a sizing issue, a color representation problem, or just a bad batch. Before Starch, that was 8 minutes per ticket: open Gmail, find the order in Shopify, check delivery, type a response, log it somewhere. Eight minutes times 75 requests is ten hours of founder time. With the Starch triage app running, 61 of those 75 were auto-approved and responded to inside four minutes of arriving — the customer's LTV was over $300 or the order total was under $40. The 14 flagged ones landed in a review queue you cleared in 22 minutes on a Tuesday morning. The returns dashboard showed a 34% return rate on the slate jogger specifically versus 8% on every other colorway, with the top reason phrase in return emails being 'color looks different in person.' That single data point killed the reorder on slate and moved the budget to the olive, which had a 6% return rate. Total refund dollars on the spike: $6,000. Time you spent on it personally: under two hours across the whole month.

Measurement

How you'll know it's working

Return rate by SKU (%, trailing 30 days vs prior 30 days)

Refund dollars as % of gross revenue (monthly)

Return rate by acquisition channel (Meta vs email vs organic)

Average time from delivery to return request (days)

Auto-approval rate on refund triage (% handled without founder review)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Shopify's built-in returns flow + manual Gmail

Shopify processes the refund but doesn't triage, draft replies, or surface return-rate trends — you're still doing the lookup and the typing yourself.

Gorgias or Zendesk

Good dedicated support tools, but they don't connect your return rate back to ad channel performance or your reorder model, and they're priced for teams — not one founder checking tickets between calls.

Loop Returns

Handles the returns portal experience well, but Loop's analytics don't tie back to your Shopify UTM data or your CAC, so you still can't tell which ad creative is generating your high-return customers.

Manual Google Sheet return log

Free and flexible, but someone has to fill it in — and that someone is you, which means it's two weeks behind and missing the columns that matter when you actually need to make a reorder call.

On Starch RECOMMENDED

One platform — founder inbox, crm all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually connect to Shopify, or do I need to export data manually?

Shopify is available from Starch's integration catalog — you connect it once and the agent queries it live whenever your triage app or dashboard runs. No CSV exports, no manual sync.

Can Starch send refund approval emails from my actual Gmail account, not a generic address?

Yes. Starch connects directly to Gmail as a scheduled-sync provider with read and send access. Replies go out from your Gmail address. One thing to know: the Gmail OAuth consent screen currently shows the underlying connector's name rather than Starch — that's on the roadmap to fix, but it's worth knowing before you connect.

What if my returns portal is a third-party site with no API — like a branded Loop or AfterShip page?

Starch automates it through your browser — no API needed. Describe what you want: 'Log into my returns portal each morning, pull new requests, and add them to my triage queue.' Starch navigates the site the same way you would.

Will this work if I'm getting 5 refund requests a day, not 500?

Yes — and honestly, five a day is the best time to set this up, before it's twenty. The SKU-level return rate tracking is valuable at any volume. You'd rather know that one colorway has a 30% return rate when you've shipped 40 units than when you've shipped 400.

Is Starch SOC 2 certified? I'm nervous about connecting Gmail and Shopify to a new tool.

Starch is not SOC 2 Type II certified today — that's an honest answer. If your compliance requirements make that a hard requirement right now, that's worth knowing upfront. It's on the roadmap.

What about the Customer Support Agent that was mentioned — can I use that today?

Not yet. The Customer Support Agent — which would handle fully automated end-to-end refund resolution across chat, email, and social — is currently in development. You can request beta access. Today, the Email Triage app handles the inbox drafting and auto-approve logic, which covers most of the time savings.

Can the returns dashboard pull in my Meta ad spend to show cost-per-return by campaign?

Yes. Connect Facebook Ads from Starch's integration catalog; the agent queries it live. You can describe a dashboard that joins Shopify UTM data to Meta campaign spend, so you see not just return rate by channel but effective margin per acquisition source after refunds.