Safety and review guide

ReplyPolish creates customer reply drafts for review. The tool is designed to make replies clearer, but the user remains responsible for checking facts, policy, privacy, and the final decision before sending a message.

Review before sending

Read the full draft before copying it into a support inbox, marketplace message, SMS tool, or public review response. Confirm that the reply matches the actual case, the current policy, and the channel where it will be sent.

Keep promises specific

A draft should not invent refund approvals, delivery dates, compensation, legal positions, appointment times, or service guarantees. Put confirmed facts and deadlines in the facts field, then remove any wording that goes beyond those facts.

Protect private information

Do not paste passwords, full payment card numbers, security codes, government IDs, medical records, or private account credentials. For public review replies, avoid order numbers, addresses, emails, phone numbers, and billing details.

Use extra care for high-risk topics

Refunds, billing, account access, legal complaints, safety issues, health topics, and financial topics should be reviewed against the actual business policy and applicable rules. ReplyPolish is not a legal, medical, financial, or compliance advisor.

Check tone separately from facts

A warmer tone can make a reply easier to read, but it should not change the answer. A firm tone can keep a boundary clear, but it should not sound dismissive or punitive. The best draft is both accurate and respectful.

Use ReplyPolish as a drafting aid, not as an automatic decision system. The safest workflow is to lock the facts, generate a draft, check the risk notes, and make a final human review before sending.