Imagine a hypothetical buyer messages a seller: "Is my refund happening or not?" The seller's own notes say only "looking into it." That vague update is the friction this article addresses. It does not describe an observed 365nails ticket, a real customer conversation or a measured outcome. It is a writing and diagnosis problem: how do you keep a quality issue under review plainly separate from a confirmed refund so the customer knows exactly which state they are in?
Answering the decision directly
A support status update should name the actual state: under review, quality issue confirmed with refund details pending, or refund details confirmed. Confirming a quality issue does not by itself establish the refund amount, timing or processing status. State what happens next and who is responsible, without promising unverified details. Describe payment as processed only when the record supports that separate status.
Why updates blur the two states
The likely causes sit in the writing process, not in the customer:
- One template for two states. A single "we are reviewing your issue" line gets reused after a refund has already been confirmed, so the customer may read it as "nothing has happened."
- Review language that sounds like a verdict. Phrases such as "we have verified the problem" used before any conclusion muddle the state in the other direction.
- Missing evidence checklist. When the seller has not defined which photos, order details or batch references are needed, the update may not explain what is still needed.
- Resolution terms folded into the review message. Refund mechanics get mentioned mid-review as a possibility, so the customer may treat a hypothetical as a promise.
Questions and evidence to settle before you reply
Before writing an update, a seller can work through this diagnostic set. These are proposed operator practice, not a 365nails workflow:
- Which state is this ticket actually in, on the evidence I hold right now?
- Do I have the customer's description of the defect, plus the visual or batch evidence my own policy requires?
- Has anyone already confirmed anything to this customer, in any channel? Check chat, email and marketplace messages together so one channel does not contradict another.
- If confirmed, what resolution terms have been verified internally, and who owns confirming the details?
- What single next step is supported by the current record, without an unverified date or amount?
What remains uncertain may be the internal handoff: who closes the review and who confirms resolution details. If that ownership is unresolved, say the issue remains under review, identify the next verified step, and clarify responsibility internally without implying that a refund has been confirmed.
A bounded resolution path
Write the update against a short, closed loop:
- Under review: state that the issue is being reviewed, restate the evidence received, name the one item still needed if any, and say the customer will get a follow-up once the review closes. Do not present an unapproved refund as confirmed; distinguish general policy information from the decision on this issue.
- Confirmed: distinguish a confirmed quality issue from confirmed refund details. State only the resolution details established in the record and identify anything still pending.
- Close: when the review resolves, send a new update rather than editing the old one, so the customer sees a clear change of state.
Where verified 365nails service facts fit
For a confirmed product quality issue, 365nails supports a refund without requiring return of the affected product. The team reviews the issue and confirms refund details. Note the boundary: the review stage and the confirmed stage are distinct in that verified fact, which is exactly the separation this article recommends for seller updates. Separately, 365nails supports salons, independent retailers, online sellers and founders building their own press-on nail brand — a service-scope fact, not a statement about how any individual ticket will be decided.

365 Take
An update should make clear whether review is ongoing, a quality issue has been confirmed, or refund details have been confirmed. Name the next responsible person or team and the next verified step. This is proposed communication practice, not a claim about how customers will respond.
From the 365 Workbench
A proposed drafting practice is to separate the customer-facing status from internal evidence notes. Draft the internal evidence summary first, determine the current state from it, and then write the customer-facing line. The verified 365nails fact above establishes the review and refund-detail boundary; it does not establish a particular internal ticket workflow.
Operator Move
Today, review your current support templates and label the status each one communicates: issue under review, quality issue confirmed with refund details pending, or refund details confirmed. Split any template that blurs those states. Include the verified next step and its responsible person or team. Request outstanding evidence only when it is actually needed, and do not add dates, amounts or payment-processing claims the record does not support.

