Support triage, working example for Jewelry Candles

Every ticket below is invented. I asked for a real complaint to work from and didn't want to hold this up waiting, so I wrote four from scratch. The names, order numbers, dates and order contents are mine. The product names and prices are real, taken from your collection pages.

Anything in [square brackets] is a number or a decision I refused to invent. Some are ordinary setup gaps. Some are gaps on your side, there's a section at the bottom about those.

The queue this morning

Sorted by how close each one is to becoming a public complaint, not by arrival time, and not by how angry the customer sounds.

3Past your published 48-hour reply standard with nothing sent

3Customer has written more than once, unanswered

11Days since the oldest unanswered message arrived

1Safe for the system to answer on its own

Human send only Rule 1 fired Rule 2 fired Rule 3 fired Rule 4 fired, most restrictive, wins

What arrived

Customer

Third time asking, where is SAMPLE-4417

This is the third time I'm writing about SAMPLE-4417 and I still haven't heard from anyone. I ordered two Black Raspberry Vanilla Jewelry Candles and got a shipping confirmation two days later, so I assumed it was on the way. It's been over two weeks and the tracking has said "Label Created, USPS Awaiting Item" the entire time. It has never once moved.

I emailed nine days ago, emailed again five days ago, and called and left a voicemail two days ago. Nothing back on any of them. I'm not trying to be a pain, I just want somebody to tell me whether this order actually shipped or not. If it got lost on your end, fine, these things happen, just say so and send another one.

This was for my daughter's 12th birthday, which was Saturday. She got an empty card. I'd still like the candles but at this point I mostly just want someone to answer me.

What the system pulled out

Extracted

Order reference: SAMPLE-4417
Items: 2 × Black Raspberry Vanilla Jewelry Candle, $45.99 ea
Order total: $91.98 · free shipping applied (contiguous U.S., $75 min)
Carrier: USPS
Last tracking event: "Label Created, USPS Awaiting Item", no scan since
Days since order placed: 16
Days since label created: 14
Days since first unanswered contact: 9
Contact attempts, unanswered: 3, two emails, one voicemail
Deadline named by customer: Child's 12th birthday, already passed
What they are asking for: 1. Confirm whether it shipped. 2. Reship if lost. Refund not requested.
Escalation language: None yet

Drafted reply, waiting for a person to send

Operator voice

Hi [first name], You've written three times about SAMPLE-4417 and heard nothing back. That's our failure, not yours, and I'm sorry. Here is where your order actually stands. A USPS label was created for it on [label date], that label is what triggered the shipping confirmation you received. Since then, tracking has read "Label Created, USPS Awaiting Item" with no scan recorded against it at all. Our shipping information tells customers that tracking may take up to 48 hours to update once a label has been created. You are well past hours and into weeks, so I'm not going to ask you to keep waiting. What happens next, specifically. Your order is going to [fulfillment location] for a physical check, to establish whether the package is still sitting with us or was handed to USPS and never scanned in. It's assigned to [owner name], who will see it through. You'll hear from me by [follow-up date] either way, and if the answer isn't in by then, I'll write to tell you that rather than go quiet on you again. If it never left us, we'll [reship or refund, your call on which is default]. If USPS has it and never scanned it, that's still not yours to chase: [we'll open the trace from our end, or here is exactly how to file it with USPS yourself, your call, see the notes at the bottom of this page]. You won't have to ask a fourth time for either one. I can't do anything about the birthday, and I'm genuinely sorry about that part of it. [rep name] Jewelry Candles Customer Care

Why the system won't send this by itself. Nine days of silence puts it past Rule 4, which takes the ticket away from automation entirely. A fast, well-written machine reply to someone who has been ignored for nine days still reads as a machine. The drafting saves the time; the sending stays a person's job.

Drafted, held for approval Rule 1 fired Rule 2 fired Rule 5 fired, most restrictive, wins

What arrived

Customer

SAMPLE-4418 marked delivered but nothing here

Hello, my order SAMPLE-4418 shows as delivered on Tuesday afternoon and there is no package here. I've checked with both my neighbors, I've checked the front office of my building, and I've looked in every spot a driver might have tucked it. Nothing.

I called USPS and they told me the scan looks complete on their end and that I need to contact the shipper. So I emailed you on Wednesday and again on Friday and haven't gotten a response to either one.

I'm not accusing anybody of anything, I know packages get taken off porches. But $101.97 is not nothing to me and I genuinely don't know what to do next. Can someone help me file a claim with the carrier, or is there any chance of a replacement? Even just telling me which of those is realistic would help more than nothing.

What the system pulled out

Extracted

Order reference: SAMPLE-4418
Items: 1 × Fresh Baked Sugar Cookies Jewelry Candle, $45.99
2 × Caramel Apple Cash Money Candles, $27.99 ea
Order total: $101.97 · free shipping applied
Carrier: USPS
Tracking status: Delivery scan recorded, not received by customer
Address dispute: None raised
Days since delivery scan: 6
Days since first unanswered contact: 5
Contact attempts, unanswered: 2 emails
Published position: Shipping policy ends responsibility at the delivered scan and directs customers to the carrier. Separately, the refund policy states missing or stolen packages cannot be replaced at this time. (Two different pages.)
What they are asking for: Help filing a carrier claim, or a replacement, says either answer beats none
Decision required: Yes, published policy says no; whether to make an exception is a person's call

Drafted reply, waiting for a person to approve

Operator voice

Hi [first name], Thank you for checking with your neighbors and your building's front office before writing, that's the legwork most people skip. I'm sorry your first two emails went unanswered. Where SAMPLE-4418 stands: it shipped via USPS under tracking [tracking number], and the carrier recorded a delivery scan on [scan date and time]. The address on the order is [address on file]. If that isn't where you are, tell me straight away, because it changes everything below. I'd rather be straight with you than leave you hoping. Our published policy is that once tracking shows a package delivered our responsibility ends, and separately that we can't replace missing or stolen packages. So a replacement isn't the default outcome here, and I'm not going to imply otherwise while you wait. That isn't the same as handing you a phone number and calling it finished. On my side: 1. I've pulled the complete scan history and delivery-scan detail for your tracking number. It's below this message. That record is what the carrier will ask you for, and you shouldn't have to come back and request it from us. 2. I've asked [owner name] to decide whether to make an exception on this one. What the policy says and what we choose to do are two different questions, and the second belongs to a person. You'll have that decision by [follow-up date], a yes or a no, not a maybe. [If your team is willing to open carrier traces as the sender, add: "I've also opened a shipper-side trace with USPS, reference (number)." If not, delete this paragraph, see notes at the bottom of this page.] [rep name] Jewelry Candles Customer Care

Why this one is drafted but held. The honest answer under your published policy is largely no, and a "no" that lands four minutes after the email reads as a machine refusing someone. The system's job here is the gathering and the drafting. The deciding stays with whoever owns the goodwill budget.

Human send only Rule 1 fired Rule 2 fired Rule 5 fired Rule 4 fired, most restrictive, wins

What arrived

Customer

Is this a scam? SAMPLE-4419, eight candles, eight $2 bills

I need somebody to tell me straight whether this is a scam.

I ordered eight Iced Lemon Cookies Cash Money Candles on order SAMPLE-4419, $279.92. I burned every one of them down. Every single candle had a $2 bill in it and nothing else. Eight for eight, all at the exact minimum.

Your site talks about rewards up to $2,500. I understand it's random, I'm not stupid. But eight in a row at the exact floor doesn't feel random to me, and I don't know what to think.

I emailed about this eleven days ago and again seven days ago. Neither one got a reply. If nobody is going to explain it to me I'll file with the BBB and post about it, and honestly I'd rather not do that. Just talk to me.

What the system pulled out

Extracted

Order reference: SAMPLE-4419
Items: 8 × Iced Lemon Cookies Cash Money Candles, $34.99 ea
Order total: $279.92
Product line: Cash candles, guaranteed real $2 bill per candle; random larger rewards in select candles up to $2,500; odds not published
Outcome reported: $2 bill in all 8, no larger reward in any
Days since first unanswered contact: 11
Contact attempts, unanswered: 2 emails
Escalation language detected: "scam" · "file with the BBB" · "post about it"
What they are asking for: An explanation. No remedy requested, unusual this far in.
Decision required: Yes, no published claim path exists for a low-prize outcome, so this can't be answered from policy alone

Drafted reply, waiting for a person to send

Operator voice

Hi [first name], You asked a direct question, then asked it again four days later, and got silence both times. I'm sorry, that silence is worse than any answer I could have given you, and it's why you're asking the question you're asking now. Let me tell you exactly what I know and exactly what I don't. What I know: every cash candle includes a guaranteed real $2 bill, and the larger rewards, up to $2,500, sit in select candles and are randomly distributed. All eight of yours contained the guaranteed $2, which I understand is precisely your point rather than a comfort. What I don't know, and won't pretend to: we don't publish odds. That's stated on our promotional rules page. So I can't show you a probability that would tell you whether eight out of eight at the minimum is ordinary or unusual, and I'm not going to invent a number to make this email land more softly. What I'm not going to do is quote policy at you and close the ticket. Your order, eight Iced Lemon Cookies Cash Money Candles at $34.99 each, $279.92, placed [order date], is with [owner name] for a goodwill review. That means a person with authority to make a call is looking at it, which is a different thing from a policy answer. You'll have the outcome by [follow-up date], from a person with a name on it. [rep name] Jewelry Candles Customer Care

Why this one never touches automation. Once someone has typed "BBB" into an email, another fast status note reads as more of the same silence. Rule 4 pulls it out of the queue and hands it to a person the same day. Note what the draft doesn't do: it doesn't restate the guarantee and the return terms as an answer. That reply exists in your public record twice, and both customers rejected it, so sending it faster isn't the fix.

Safe to auto-send Rule 6 fired

What arrived

Customer

SAMPLE-4420, cracked candle + one item missing (photos attached)

Hi there, my order arrived this morning (SAMPLE-4420) and there are two issues.

First, the Baked Apple Pie Jewelry Candle has a crack running down the side of the glass and there was hardened wax across the bottom of the box. I've attached two photos, one straight on and one at an angle.

Second, I ordered five items and only four were in the box. The packing slip lists all five.

Honestly not upset, stuff happens in transit and I'm sure it's an easy fix. Just let me know what you need from me. Order number is SAMPLE-4420. Thanks!

What the system pulled out

Extracted

Order reference: SAMPLE-4420
Items ordered: 1 × Baked Apple Pie Jewelry Candle, $45.99
1 × Footprints In The Sand Jewelry Candle, $45.99
3 × Christmas Cookies Cash Money Candles, $29.99 ea
Items received: 4 of 5, customer has not identified which is missing
Damage reported: Baked Apple Pie Jewelry Candle, crack down the glass, wax leaked into box
Photos attached: 2, meets the two-photo count on the broken candle form. Image quality not assessed.
Delivered: Today
Reporting window: Inside the published 48-hour product-issue window, inbound timestamp locked to ticket
Time left in that window: 44h
Days since first unanswered contact: 0, first contact
Tone: Cooperative, no escalation language
Routing: Split, broken candle form for the candle; named fulfillment owner for the short shipment (I found no replacement form covering that)

Drafted reply, cleared to send automatically

Operator voice

Hi [first name], Thank you for sending photos with your first email, that's genuinely what lets us move fast on this. There are two problems in your message and they take two different routes. The cracked Baked Apple Pie Jewelry Candle. Broken candles go through our replacement form rather than the returns process: jewelrycandles.com/pages/broken-candle-replacement-form. It requires at least two clear photos showing the crack in the glass, you've attached two already, so you should be able to upload the same ones. The order number for the form is SAMPLE-4420. Once the form is in, we ship the replacement within 48 hours. The item that wasn't in the box. You ordered five things, four arrived, and your packing slip lists all five. That one is ours to check, and I'm not going to ask you to prove anything before we do. One thing that would speed it up: could you tell me which item is missing? Your order is flagged for a pick-and-pack check with [owner name], and I'll write back by [follow-up date] with either a shipping confirmation for it or [your resolution for a short shipment]. One note so no clock runs out on you. We ask customers to report a product issue within 48 hours of receiving their order. Your email arrived the same day the box did, so you're comfortably inside that, and I've locked that date to your ticket. However long our end takes from here, it doesn't count against you. [rep name] Jewelry Candles Customer Care

Why this is the one the system can send alone. Nothing in it decides anything, it routes, it confirms a deadline was met, and it asks one question. It's also the ticket most likely to be left until tomorrow, because the customer is nice. Three separate 48-hour clocks are live on your pages, and tomorrow is where they quietly break while nobody is angry yet. Tone is a bad proxy for urgency; that's most of the argument for aging rules.

The rules underneath

These are the part worth arguing with. When more than one fires on the same ticket, the most restrictive action wins, that's why SAMPLE-4419 is human-send-only even though Rule 1 would otherwise have it acknowledged inside 48 hours.

WhenNothing has gone out within 48 hours of a ticket arriving, or, for anything landing on a Friday, by end of the following Monday.

ThenSend an acknowledgment carrying the order's actual current status, not a "we received your message" note. Assign a named owner. Keep it flagged overdue until a person has touched it.

Your own FAQ tells customers you'll get back to them within 48 hours, and that Friday inquiries get a reply the following Monday. This doesn't invent a standard, it makes the one you already published the thing the system enforces. Missing a response time you set yourself is the easiest sentence in the world for an unhappy customer to write, because they can screenshot your page next to it.

WhenA second message arrives from the same customer about the same order, with no reply in between.

ThenUrgency moves up one level, the ticket jumps ahead of newer mail, and the queue label reads "2nd contact, unanswered" so nobody has to open it to know what it is.

In the public complaint record, repeat contact with no reply is attached to nearly every other issue rather than standing on its own, customers describing four emails, six emails with documentation, one describing roughly a hundred. By the time someone writes a formal complaint, the count of ignored attempts is usually the story, not the original problem. Counting repeat contact is enough to break that pattern.

WhenAn order has a shipping confirmation, but no carrier scan has been recorded for 7 calendar days since the label was created.

ThenMove to critical. Queue the order for a physical check at the fulfillment location. The reply states plainly that no scan has been recorded and that we're checking physically, it does not ask the customer to allow more time.

Your shipping information tells customers tracking may take up to 48 hours to update after a label is created. Past days rather than hours, "please allow a little more time" stops being true and the customer can see that on their own screen. Note what this rule deliberately does not say: a missing scan isn't proof the package never entered the network, USPS does accept parcels it fails to scan. Asserting otherwise in writing is a claim a later scan can embarrass you with.

WhenA ticket crosses 7 days since the first unanswered contact, or the message contains BBB, chargeback, dispute, attorney general, lawyer, "scam", a named review site, or a threat to post publicly.

ThenNo automated reply goes out at all. The system drafts and holds; a named person with authority to approve a reship, refund or goodwill gesture must send it the same day.

Public complaints about your business tend to surface somewhere around the two-to-three week mark. I can't prove silence is what causes that escalation, it's a pattern across review sites, not a mechanism I've tested, but it's the one variable sitting on your side of the line. And once someone has typed "BBB", another automated note reads as more of the same. That's why this rule takes the ticket away from the automation rather than speeding it up.

WhenThe reply would have to communicate a decision the published policy either refuses or doesn't cover: a package with a delivered scan, a final-sale item, or a prize-value complaint with no published claim path. (A ticket where the reply only routes and asks, like SAMPLE-4420, isn't deciding anything, so this doesn't catch it.)

ThenThe system does not send the decision. It assembles the evidence, full tracking history, scan detail, order contents, what the relevant policy actually says, drafts the reply, and holds it for a person to approve, edit or overrule.

These are the cases where speed alone makes things worse. A quoted policy landing in four minutes reads as a machine refusing you. The automation's job here is the gathering and the drafting, never the deciding, and there's a straightforward commercial argument that a goodwill call on a $280 order costs less than a permanent public complaint about one.

WhenAny product-issue ticket, damaged, broken, wrong or missing item, regardless of how calm the customer sounds.

ThenLock the inbound timestamp to the ticket and flag it time-critical. Route to the matching replacement form where one exists (broken candle; damaged or wrong-size jewelry) and to a named fulfillment owner where I found none (short shipment, wrong item). A ticket needing both gets split, not queued behind one path. Tell the customer in writing whether their report landed inside the 48-hour window, and where it didn't, flag for a person before any window is quoted.

Three separate 48-hour clocks are already live on your pages: product issues reported within 48 hours of receipt, replacement candles shipped within 48 hours of the broken-candle form, replacement jewelry within 48 hours of that form. A polite email with photos is the easiest one in the inbox to leave until tomorrow, and tomorrow is where all three quietly break.

WhenA follow-up date promised to a customer passes with nothing sent.

ThenThe ticket goes straight back to critical and to the owner who made the promise, ahead of everything else in their queue.

Every draft on this page commits to a date. A system that manufactures written, dated callback promises with nothing enforcing them doesn't fix a non-response problem, it generates fresh evidence of one, in your own words, with a timestamp. This rule exists because the rest of the page would be dangerous without it.

WhenMore than [your threshold] tickets in the queue are older than seven days at once.

ThenA daily aging digest goes to a named manager: every overdue ticket, its age, the customer's ask in one line, and whether anything has gone out. New tickets keep flowing normally, the digest is the escalation.

On the public review record, three separate grievances logged across roughly two and a half months were all answered on the same day, with near-identical text. From the outside that reads like a catch-up sweep, though you'd know what actually happened that week. Either way, a sweep always arrives too late for whoever waited longest. A short daily list is what stops the pile forming, and it costs a manager about ninety seconds a morning.

The thing I'd fix before buying any software

This came out of reading your policy pages closely enough to write replies that quote them. I'd rather hand it over than keep it as a sales point.

Your published policies currently contradict each other, and automation would multiply whichever version it's pointed at.

Two processing windows on the same page. /pages/refund-policy states "All orders are processed + shipped within 2-3 business days" and, further down, asks customers to "apply our 3-5 business day window for processing." No reconciling text.
Three return windows, live simultaneously. 60 days from purchase date (/policies/refund-policy), 30 days from receiving your order (/pages/refund-policy), and 60 days after receiving your order (/pages/faq).
A terms page that contradicts all of them. Section 3 of /pages/jewelry-candles-terms-and-conditions: "All sales are final once completed and any refunds, exchanges, or any related resolutions come at the sole discretion of Jewelry Candles LLC."
Two different toll-free numbers appear in otherwise near-identical policy text on different pages.
The page carrying your shipping timeframes isn't linked from your own navigation. I checked the raw HTML of the footer, homepage and both FAQ pages and found no link to it. It's still a live URL, I'm not claiming customers can't reach it, only that they're unlikely to land on it from your site.

This is why I kept returns out of all four samples. A rep can't answer consistently when the source doesn't. Reconciling that text is a prerequisite, not a nice-to-have, and it's your text to reconcile, not a vendor's. It's also free.

What this demo can't do

The parts a proposal would normally leave out.

The integration is the product; the wording is just what makes it worth opening. These replies say things a demo cannot know, that no scan has been recorded since the label, that a delivery scan happened at a specific time, that four of five items shipped. Every one of those is only true in production with live read access to your order data and to USPS and UPS tracking. Without that, all four collapse into a polite acknowledgment, which is something that can be sent with no integration at all.

I don't know what you already run. I didn't research your current helpdesk, autoresponders or order-status notifications, and I'm not claiming you have none. A vendor describing a gap he hasn't verified is a vendor guessing. If something's already in place, the useful question is whether these rules sit on top of it or replace it.

I can't tell which inbox this would watch. Three customer-facing email addresses and two different toll-free numbers appear across your own pages, and /pages/contact-us is a Wufoo form embed rather than a helpdesk. Triage pointed at the wrong queue is worthless, so the first real question isn't technical, it's which of those actually lands somewhere a person works.

The system reads text, not photographs. On SAMPLE-4420 it counted two attachments; it did not assess whether the crack is visible in them. Your broken-candle form is explicit that you won't replace a candle without a picture of the actual breakage, so a machine pre-approving photos would set customers up to be rejected later by your own reviewer. Counting is safe. Judging isn't.

Two drafts assume a business decision, not a software one. SAMPLE-4418's bracketed paragraph, and the bracketed clause near the end of SAMPLE-4417, both offer to open a carrier trace as the sender. Whether you're willing to do that is your call, and your published policy currently points customers to the carrier themselves. If the answer is no, those come out and both replies get noticeably weaker, worth deciding deliberately rather than discovering by default after it's built.

Every sample here is a bad week. All four score medium or higher, because I built them from public complaints, which are by definition the ones that went wrong. A real week has a long tail this doesn't show: tracking questions, ring-size changes, restock asks, appraisal follow-ups. That tail decides whether triage saves time or just adds a step, and I have no visibility into your ticket volume, staffing or current response times. Anyone quoting you a percentage improvement without those three numbers is making it up.

The complaint text is paraphrase, not quotation. Tone is modelled on publicly posted complaints and reviews, but everything I read passed through a summarizing step. If a line sounds like a specific customer you recognise, that's coincidence, not a record.

I'd build this to draft and hold rather than send unattended, particularly where the honest answer is no. A four-minute automated decline is worse than a slow human one. If you want fully unattended sending, that's a different design with different risk, and I'd want to argue about it with you before building it rather than after.