Classify reason
Not all refunds are equal. Technical failure, duplicate charge, and unopened gift differ from 'I did not like the symbol'.
- Payment succeeded or duplicate?
- Result generated or failed?
- Product opened, emailed, downloaded?
refund without fire
Refund review workflow
How to review digital esoteric service refund requests honestly, quickly, and without fear-selling.
Goal: distinguish technical error from interpretation dissatisfaction and avoid arguing with a person about feelings.
what to ask first
Order/payment id or purchase email.
Product type and purchase date.
Reason: no access, technical error, accidental purchase, content dissatisfaction.
Whether the scroll was opened/downloaded.
Offer correction first
If the issue is access, email, or incomplete result, restore the path first. If the client still wants a refund, do not turn the conversation into court.
- New link sent.
- Result status verified.
- Clear expectation set.
Log decision
Every refund should leave a trail: reason, amount, product, whether opened, who decided, date.
- Refund reason logged.
- Stripe action matches internal status.
- Client receives a calm confirmation.
reply templates
Technical issue
Service did not deliver the paid result.
Checking your access or refund
Thank you for the message. If the paid scroll was not delivered because of a technical issue, we will restore access or issue a refund according to our policy. I will check payment and result status by your email.
Content dissatisfaction
Result was received, but the client dislikes the interpretation.
About your OmenHall scroll
I am sorry the scroll did not feel useful. OmenHall provides symbolic interpretation for reflection, not a guaranteed prediction. I will check whether there was a technical delivery or generation issue and reply under the Refund Policy.
red flags
- Client threatens chargeback before review.
- Duplicate charge or multiple checkout attempts.
- Many requests around one webhook failure.
closed when
- Refund, restore, credit, or no-refund decision recorded.
- Client receives a brief summary without internal notes.
- Repeated risk added to incident log.
related doors