by ReturnCopy (LX AI)
ReturnCopy drafts clear return and refund policy copy that keeps customer trust — policy text and customer-facing replies for merchants who need language that is firm without sounding hostile.
Decision-support only — confirm before you publish or act.
I start by visiting the ReturnCopy sign‑up page and entering a work email. After submitting the form I receive a verification link. Clicking that link confirms the address and opens the onboarding wizard. I set a password that meets the strength requirements shown on the screen.
Next I choose the e‑commerce platform that powers my shop. ReturnCopy offers connectors for Shopify, WooCommerce, BigCommerce and Magento. I select the platform, then follow the prompts to install the small app or paste the API key. The connection test runs automatically and shows a green check when the token is valid.
In the settings panel I enter the store name, the default currency and the time zone used for order timestamps. I also choose the language for the generated copy — English is the default but I can switch to Spanish or French if my buyer base prefers those languages. I save the settings before moving to the drafting step.
ReturnCopy provides three starter templates: a short 30‑day window, a standard 60‑day window and an extended 90‑day window. I pick the one that matches the refund period I already advertise on my site. If I need a custom window I can edit the number of days directly in the template.
I then fill in the required legal clauses. The wizard highlights fields that are often required by consumer‑protection rules: eligibility condition, time frame for initiating a return, who pays return shipping, condition of items accepted, and how refunds are issued. I type plain language answers; the tool does not suggest legal advice, it only helps me structure the wording.
When I press “Generate draft” ReturnCopy returns a full policy text. I read it aloud to spot any awkward phrasing. I check that the refund timeline is explicit, that the tone stays neutral, and that there are no contradictory statements. If I spot a gap I edit the clause directly in the preview pane.
Because the draft is produced by a language model I review the OWASP Top 10 for Large Language Model Applications to see which risks are relevant. I look at the items about prompt injection and output validation. I make sure the policy does not contain any statements that could be interpreted as a guarantee of future behavior. I note any concerns and adjust the wording accordingly.
Once satisfied I click “Save draft”. The policy is stored in my ReturnCopy library and can be exported as plain text, HTML or Markdown. I copy the HTML version into the policy page of my store’s theme.
ReturnCopy groups common reasons into categories: damaged item, wrong item received, changed mind, late delivery, and missing parts. I select the reason that matches the customer’s ticket. If the reason is not listed I can type a free‑form description and the tool will try to map it to the closest category.
Below the reason selector I choose a tone slider that runs from formal to friendly. I usually set it slightly toward friendly because I want the reply to feel helpful while still being clear about the next steps. The slider adjusts word choice and sentence length.
Pressing “Create reply” returns a ready‑to‑send message. The output includes a greeting, a restatement of the issue, the applicable policy clause, the action the customer should take, and a closing line that invites further questions. I read the reply to verify that it does not sound robotic.
If the generated sentence feels off I edit it directly in the reply box. I can replace words, add a personal sign‑off, or insert a short apology if appropriate. The tool keeps track of the original version so I can revert if needed.
I save the final reply to my library under the reason label. Later, when a similar ticket arrives, I can insert the saved reply with one click and only adjust order‑specific details like the order number or the SKU.
ReturnCopy lets me paste a few paragraphs from my existing product descriptions, FAQ or blog posts. I copy about 200 words that show how I usually speak to customers. The tool analyses word frequency, sentence length and common phrases.
After the analysis I see three sliders: formality, enthusiasm and directness. I move each slider until the preview text sounds like something I would write myself. I can lock a slider if I do not want it to change during later generations.
I run a quick test by generating a policy and a reply for a “changed mind” scenario. I compare the output to my voice sample. If the enthusiasm is too high I lower the slider and regenerate. I repeat the test for a “damaged item” case to ensure the tone stays appropriate for a more serious issue.
When the preview matches my expectations I click “Save voice profile”. The profile is attached to my account and will be used automatically for all future drafts unless I select a different one.
I paste the generated policy into a readability tool and look at the Flesch‑Kincaid grade level. I aim for a score around 8th grade so that most shoppers can understand it without difficulty. If the score is higher I replace long words with simpler synonyms.
I add a short line at the bottom of the policy that states the copy is decision‑support only and that I should review it with a qualified adviser if I have specific legal concerns. This line is not generated by ReturnCopy; I type it manually.
I create a test order in my shop’s sandbox mode and initiate a return using the reason “wrong item received”. I then use the saved reply from ReturnCopy to respond to the test ticket. I verify that the reply includes the correct order number, links to the return label, and a clear deadline for shipping the item back.
If a real customer asks for clarification I note the missing information and update either the policy clause or the reply template. I then save the updated version and use it for the next similar ticket.
Before publishing the policy on the live site I ask a teammate to read it and confirm that it matches our brand voice and does not contain any absolute guarantees. Once both of us agree I replace the old policy page with the new version.
ReturnCopy does not promise that the generated text will satisfy every local regulation. I must still check the output against the rules that apply to my jurisdiction.
The tool is meant to help me draft language faster. It does not substitute a lawyer or a compliance expert when I need a formal legal review.
I cannot rely on the copy being perfect for every possible scenario. I review each draft and edit as needed.
ReturnCopy never pushes changes to my store automatically. I always copy the final text myself and upload it through my store’s admin panel.
Even with clear replies I still need a human to handle complex cases, exceptions or emotionally charged situations.
ReturnCopy drafts a return policy and the customer replies for common return reasons.
Both — a return-policy draft and reason-specific customer replies.
Yes — it drafts in your store voice so replies do not feel templated.
Free includes 5 drafts per month; Pro is $15/mo for more.
A clear policy and empathetic replies protect seller rating and repeat purchase; vague policy drives refunds and disputes.
ReturnCopy drafts a return policy and the empathetic replies that go with it. It matches your store tone, states a clear refund timeline, and writes reason-specific responses that keep the trust — and the sale.
Want to try the product? ReturnCopy
Generated 2026-09-17 · primary sources only · no fabricated traffic metrics