Working example, built for 5Boys Apparel

The refund and status update that's supposed to happen, sent without a customer having to chase it

A BBB review from Amanda S. (07/07/2025) describes "terrible communication, terrible customer service" around missed delivery dates and no tracking updates. HaLee E. (02/03/2026) says "every single order has been severely late - not by weeks, but by months" with no response by email. Alex H. (07/23/2025) says after returning defective items, "been trying to get a refund for over a month now and they still have not responded." All three describe the same underlying gap: nothing tells a customer their order's status automatically, and an approved refund still depends on someone remembering to process it by hand.

What's real: the three review quotes above are pulled directly from your BBB customer review page, with reviewer names and dates as shown there. Your BBB profile and public reviews describe a pattern of orders going quiet for weeks or months and refund requests sitting unanswered, across multiple named customers.

What's illustrative: the orders, customers, and refund tickets below are fictional, not your real production queue or actual open cases. Nothing here sends a real text/email or moves real money, this shows exactly what a customer would receive at each step and how an approved refund would move without a manual handoff. A real build connects to whatever system your team uses today to track a print job (illustrative here as a generic "production board") and to whatever payment processor handles your refunds.

Production board: update an order

Sample orders, fictional

What the customer sees

Refund & support queue: SLA-tracked, separate from the general sales inbox

Sample tickets, fictional

Every ticket carries a countdown against a 48-hour SLA. Approving a refund here processes it immediately - no separate step, no waiting on someone to remember to log into the payment processor.

New order-status / refund request: replaces phone-and-email-only intake

What I'd flag before this gets built for real

Nothing here sends a real text or email, and no money actually moves. This demo shows exactly what a customer would receive at each production milestone, and exactly what happens the moment a refund is approved. A real version needs an actual SMS/email service connected to your production tracking, and a real integration with whatever processor issued the original charge (Stripe, Square, PayPal, or your InkSoft-linked processor).
The five stages shown (order received, artwork approved, on press, QC & packing, shipped) are a typical screen-printing production flow, not copied from your internal process. Worth a short conversation before this gets built for real - your team may track a job differently across five presses running that many hours a day.
The BBB reviews are real and quoted directly with names and dates as published; the fix is a reasonable response to that documented pattern, not a guarantee every order ships on time. A part of your backlog will still run behind sometimes. What this changes is whether a customer hears about it automatically, and whether an approved refund gets stuck behind a manual step in a shared sales inbox.
The intake form only captures a request, it doesn't verify order details against a real database. Keeping it to "what's wrong and how to reach you" is deliberate, this demo isn't connected to any real order records.