Move the decision to the first line
The original only revealed that the refund request had been received by paragraph three. It now opens with the status and what is still being confirmed.
Customers want one clear answer and one clear next step, not boilerplate. We rewrite replies so the decision leads, the reason is plain, and the action is specific. Policy terms, refund amounts, resolution times, and ticket numbers stay yours to fill — anything to confirm is left as a slot.
We lead with the decision, cut the boilerplate, turn empathy into a concrete action, and mark the policy, figures, and timings you must confirm.
SAMPLE OUTPUT
This is the complete output for the source text in the demo above: a reply quality score, itemised reasoning, the slots you complete from real policy, and the rewritten reply. It is a demonstration, not a customer case.
The original only revealed that the refund request had been received by paragraph three. It now opens with the status and what is still being confirmed.
“Deeply apologise” and “very sorry” appeared twice with no action attached. They become the current status and the next step.
“Please wait patiently” carries no information. It becomes what we do, what you can send, and how timing is established.
# Reply draft **Decision**: your refund request has been received and is being checked; [ELIGIBILITY TO CONFIRM]. **Where it stands**: the refund request for order [ORDER NUMBER] is in review and needs us to confirm [ITEM TO CONFIRM]. **Next** - We will: [SPECIFIC ACTION — yours to fill in] - You can: send us [DOCUMENT] if convenient - Timing: [TIMEFRAME, per actual policy] **Note**: no refund amount or payout date is stated here. Fill those in from real policy before sending.
WHAT IT DOES
Can it be done, how long, who does what next — answer those first and put the reasons after.
“We sincerely apologise for the inconvenience” does nothing a hundred times over. Say “I checked and found [RESULT]; next I will [ACTION]”.
Refund amounts, deadlines, and ticket numbers are never guessed here; they become [FILL IN] for you to complete from real policy.
WHY IT IS WORTH DOING
Bury the answer in paragraph three and the customer emails back asking the same question.
Repeating a standard phrase at someone already annoyed usually makes the situation harder to close.
One unauthorised “this will be sorted today” hurts more than the original fault when it does not hold.
Note: how a support exchange lands depends on your policy, authority, and the actual ticket; there is no general research result for an optimal reply template. This site works on wording and structure only, and gives no legal or consumer-rights advice.
REWRITE DEMO
Dear customer, thank you for contacting us. We deeply apologise for the issue you encountered and are very sorry for the inconvenience caused. Regarding your refund, we will process it as soon as possible. Please wait patiently and keep your phone available. If you have questions, feel free to contact us anytime.
# Reply draft **Decision**: your refund request has been received and is being checked; [ELIGIBILITY TO CONFIRM]. **Where it stands**: the refund request for order [ORDER NUMBER] is in review and needs us to confirm [ITEM TO CONFIRM]. **Next** - We will: [SPECIFIC ACTION — yours to fill in] - You can: send us [DOCUMENT] if convenient - Timing: [TIMEFRAME, per actual policy] **Note**: no refund amount or payout date is stated here. Fill those in from real policy before sending.
Demo sample: the decision moves to line one, boilerplate is cut, actions split into who does what, and amounts and timings stay as slots. Paste your reply to get your version (sign-in required; one credit per run).
WHY YOU CAN TRUST IT
Refund amounts, compensation, deadlines, ticket and order numbers become [FILL IN] slots rather than plausible-looking values.
“Sorted today” and “you will definitely get your refund” are removed unless your material explicitly authorises them.
Empathy is expressed through action. We neither admit unconfirmed fault nor push the cause back onto the customer.
Submitted text is used for this single AI request and is not intentionally persisted. See the Privacy Policy.
FAQ
No. Amounts, deadlines, and compensation rules are your real policy. This site leaves a [FILL IN] slot for you to complete within your authority.
We express understanding, but we do not admit responsibility you have not confirmed. Empathy lands in the action; the cause is yours to determine.
Read it first. The output is a draft, every [FILL IN] slot needs completing, and anything touching accounts or money should be checked before sending.
One credit per run, usually done in seconds, returning the draft, the reasoning, and items to confirm.
No. Credits never expire — whatever you do not use carries over to the next cycle instead of resetting.
Not yet. Each run processes one document and consumes one credit; there is no bulk upload or API today. Email us with your use case and we will assess it.
Not intentionally. Text is used for this single AI request only. See the Privacy Policy.
Ticket replies, email replies, returns and exchanges, complaint drafts — any support text that needs a clear decision and a decent tone.
SIMPLE PRICING
For an occasional publishing cadence, with a focused monthly credit allocation.
For frequent publishers who iterate on content continuously.
Our largest monthly credit allocation, for the heaviest continuous usage.
Credits never expire: unused credits carry over instead of resetting. Credits apply to this site only and are not shared with other sites.
Prices shown are USD baselines; final currency, taxes, and discounts are determined by Paddle for the checkout location.